The first time Export-Configuration is used, it generates a warning message:
WARNING: The Enterprise path C:\Users\<username>\AppData\Roaming\powershell cannot be found
...and it cannot be suppressed with any of the usual methods:
$callerWarningPreference = $WarningPreference
$WarningPreference = 'SilentlyContinue'
$new | Export-Configuration -WarningAction Ignore
$WarningPreference = $callerWarningPreference
I'm trying to present a clean experience to users and this error message is a bit cryptic and not at all helpful: Export-Configuration creates the path and writes the file without issue. Surely this message is better suited to the Verbose stream? Searching the source, it appears to be coming from Get-ConfigurationPath and the flags to suppress warning aren't being pushed down into its scope.
I suppose I could call Get-ConfigurationPath myself first--suppressing the warning there--but I think the issue still deserves attention in either the code or the documentation.
The first time Export-Configuration is used, it generates a warning message:
WARNING: The Enterprise path C:\Users\<username>\AppData\Roaming\powershell cannot be found...and it cannot be suppressed with any of the usual methods:
I'm trying to present a clean experience to users and this error message is a bit cryptic and not at all helpful: Export-Configuration creates the path and writes the file without issue. Surely this message is better suited to the Verbose stream? Searching the source, it appears to be coming from Get-ConfigurationPath and the flags to suppress warning aren't being pushed down into its scope.
I suppose I could call Get-ConfigurationPath myself first--suppressing the warning there--but I think the issue still deserves attention in either the code or the documentation.