Re: changing cf CLI trace stream from stdout to stderr


Mike Youngstrom <youngm@...>
 

This change wouldn't effect any of my users.

Mike

On Mon, Oct 24, 2016 at 9:44 PM, Koper, Dies <diesk(a)fast.au.fujitsu.com>
wrote:

Hi friends,



Currently, the cf CLI trace when enabled (“CF_TRACE=true”, `cf config
–trace true` or with the `-v` option) is directed to stdout.

Looking at other commands, e.g. `curl -v`, it’s common to send such
information to stderr.

This recently came up in the following issue.

https://github.com/cloudfoundry/cli/issues/962



I’d like to know whether anyone would be massively inconvenienced if we
fixed this to make cf CLI trace output go to stderr (e.g. because you have
many scripts expecting trace to be streamed to stdout, or not expecting
anything but errors and warnings to be streamed to stderr)?

Note that trace configured to output to a file would not be affected.



Cheers,

Dies Koper
Cloud Foundry Product Manager - CLI




Join cf-dev@lists.cloudfoundry.org to automatically receive all group messages.