Write-Error should be used if you want to inform the user of a non-critical error. By default all it does is print an error message in red text on the console. It does not stop a pipeline or a loop from continuing. Throw on the other hand produces what is called a terminating error. If … Read more
Next time you make one, export-csv in powershell 7 has a new option you may like: export-csv -UseQuotes AsNeeded
A word of warning about some of the existing answers – they will run very slow for very big files. For a 1.6 GB log file I gave up after a couple of hours, realising it would not finish before I returned to work the next day. Two issues: the call to Add-Content opens, seeks and … Read more
No, there is no special syntax, but there is a simple workaround, using iex, the built-in alias[1] for the Invoke-Expression cmdlet: $propertyPath=”a.b” # Note the ` (backtick) before $json, to prevent premature expansion. iex “`$json.$propertyPath” # Same as: $json.a.b # You can use the same approach for *setting* a property value: $newValue=”foo” iex “`$json.$propertyPath = … Read more
For detailed and very useful background, see the answer by mklement0 After much frustration, I have decided to list all variants of quote escaping that I’ve tried, and came up with one more, which suddenly worked! So, sharing it here: kubectl patch deployment wapi-backend-d1 –patch ‘{\”spec\”: {\”template\”: {\”metadata\”: {\”labels\”: {\”date\”: \”test123\”}}}}}’ This is how to … Read more
Import-Csv $path | Foreach-Object { foreach ($property in $_.PSObject.Properties) { doSomething $property.Name, $property.Value } }
tl;dr -Filter uses .NET’s implementation of FsRtllsNameInExpression, which is documented on MSDN along with basic pattern matching info. The algorithm is unintuitive for compatibility reasons, and you should probably avoid using this feature. Additionally, .NET has numerous bugs in its implementation. -Filter does not use the filtering system provided by PowerShell–that is, it does not … Read more
Current as of PowerShell [Core] 7.2.1 PowerShell-internal use of exit codes: PowerShell-internally, where native PowerShell commands generally run in-process, exit codes from child processes that run external programs play a very limited role: Native PowerShell commands generally don’t set exit codes and don’t act on them. PowerShell has an abstract counterpart to exit codes: $?, … Read more
While @Keith Hill’s answer explains the difference between Replace method and the -replace operator, to explain why you might not see the same result, it is because you are using the String.Replace method which does string replace and -replace operator uses regex replace. You can use the Regex.Replace method for this purpose and you should … Read more
First step is to load your xml string into an XmlDocument, using powershell’s unique ability to cast strings to [xml] $doc = [xml]@’ <xml> <Section name=”BackendStatus”> <BEName BE=”crust” Status=”1″ /> <BEName BE=”pizza” Status=”1″ /> <BEName BE=”pie” Status=”1″ /> <BEName BE=”bread” Status=”1″ /> <BEName BE=”Kulcha” Status=”1″ /> <BEName BE=”kulfi” Status=”1″ /> <BEName BE=”cheese” Status=”1″ /> </Section> … Read more