Elastic-Agent: Do not output to STDERR under powershell, unless you want PS to fail execution as an error about elastic-agent HOT 7 OPEN

Pinging @elastic/ingest-management (Team:Ingest Management)

from elastic-agent.

@michalpristas or @blakerouse you know more windows than me. Can you take a look?

from elastic-agent.

Please note if you don't have $ErrorActionPreference = "Stop" (PS equiv of Bash's set -e), then PS will treat the STDERR output as an error and display it, but it wont immediately kill elastic-agent.exe. Tested under PowerShell ISE.
Why not under PowerShell interactive? I am no PS expert, but reading up on this it seems, ISE, PS Remote, and I assume task scheduled instances wrap STDERR with System.Management.Automation.ErrorRecord.

from elastic-agent.

Pinging @elastic/elastic-agent-control-plane (Team:Elastic-Agent-Control-Plane)

from elastic-agent.

closing, even with the options set i was not able to repro
Win 11 64bit

from elastic-agent.

As I document you will not trip this issue in a normal powershell console. This error handling is only on by default in PS Remote, PS ISE and certain ways of scheduling PS scripts. Search for System.Management.Automation.ErrorRecord - If this error handling is enabled any line sent to STDERR becomes an ErrorRecord that needs to be handled. If not you get the NativeCommandError, and with $ErrorActionPreference = "Stop" the exe is stopped/killed.

 [System.Environment]::OSVersion.Version

Major  Minor  Build  Revision
-----  -----  -----  --------
10     0      19042  0       

from elastic-agent.

@michalpristas could you please take a look again.

from elastic-agent.