--noconsolelogging prevents errors being logged

[michaelnoonan]

If an error occurs when running an Tentacle.exe command with the --noconsolelogging switch, the error isn't written anywhere except the log file.

For example: Tentacle.exe show-configuration --noconsolelogging can fail if you don't specify the --instance argument, and you get no configuration via stdout, but also no error message saying what went wrong.

This behaviour makes it really hard to debug scripts which are automating Tentacle setup.

Proposed solution

We should interpret --noconsolelogging as switching off Info and Warn logs (or lower) which would have corrupted stdout, but still write any Error or Fatal level logs to stderr.

Breaking change?

This change will result in:

• Verbose, Info, Warning log messages being written to stdout (like before)
• Error, Fatal log messages being written to stderr (this is a change but works within our ecosystem of tooling and automation)

[octoreleasebot]

Release Note: All error messages are now written to stderr even if the --noconsolelogging switch is used with Tentacle.exe