Logging is initialized before the configuration file is processed. #6085
Assignees
Labels
Comments
3 tasks
9 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
On Unix systems (Linux and MacOS), PowerShell logging can be customized using the -settingsFile command-line option and it is assumed the file is processed before any logging occurs.
On recent builds, this is no longer the case and logging is being initialized before the logging overrides are read from the configuration file resulting in logging using the default values.
Note that logging initialization is currently through static constructors and any reference to the associated classes can cause initialization to occur. As a result, logging initialization is non-deterministic and can occur before logging overrides are processed.
Steps to reproduce
Create a powershell.config.json with a single configuration setting "LogIdentity": "CustomPWSH"
Launch PowerShell with -settingsFile powershell.config.json
Expected behavior
On Linux, PowerShell logs all events using the identity 'CustomPWSH'
Actual behavior
PowerShell logs all events using the default identity 'powershell'
Environment data
The text was updated successfully, but these errors were encountered: