We had been printing these messages to stdout. This is fine for some operations, but others are more likely to be used in a scripted environment where just the value (e.g., token=$(doppler configure get token --plain)) is expected. By not printing to stderr, the message would end up in the value of the assignment. This just switches all uses of valueFromEnvironmentNotice to use utils.Log rather than utils.Print.
We had been printing these messages to
stdout
. This is fine for some operations, but others are more likely to be used in a scripted environment where just the value (e.g.,token=$(doppler configure get token --plain)
) is expected. By not printing tostderr
, the message would end up in the value of the assignment. This just switches all uses ofvalueFromEnvironmentNotice
to useutils.Log
rather thanutils.Print
.