Description of the new feature / enhancement
Maybe applies to other commands as well that require automation friendly output. Right now, if the user settings JSON file has not been created in the host machine, wingetcreate will output the telemetry notice in the stdout of the commands, making it noisy to deal with in automation scenarios.
Current output (no settings JSON initialized)
~ wingetcreate show Microsoft.PowerShell
Telemetry Settings
------------------
The Windows Package Manager Manifest Creator collects usage data in order to improve your experience.
The data is anonymous and collected only by Microsoft.
By default, telemetry is enabled but can be disabled by running `wingetcreate settings` and editing your settings file.
Installer Manifest:
{
...
}
Default Locale (en-US) Manifest:
{
...
}
Version Manifest:
{
...
}
To get around it in automation scenarios, one has to first run wingetcreate settings command, so that the settings file in initialized, and then run subsequent commands for a parse-able output
Proposed technical implementation details
No response
Description of the new feature / enhancement
Maybe applies to other commands as well that require automation friendly output. Right now, if the user settings JSON file has not been created in the host machine, wingetcreate will output the telemetry notice in the stdout of the commands, making it noisy to deal with in automation scenarios.
Current output (no settings JSON initialized)
To get around it in automation scenarios, one has to first run
wingetcreate settingscommand, so that the settings file in initialized, and then run subsequent commands for a parse-able outputProposed technical implementation details
No response