You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using the --json flag (such as in the example above) Heroku shows update messages.
What is the expected behavior?
It should not output update messages. Why? I would think that the vast majority of the time when someone uses --json they are intending to pipe the output into something like jq. However, when the update message is present, the output string is not valid json
The text was updated successfully, but these errors were encountered:
The Heroku CLI outputs should be outputting this warning on STDERR, not STDOUT. This allows us to display the error, while keeping something like heroku apps --all --json | jq . working. While it is a bit confusing, I think this is intended behaviour.
Have you noticed this breaking any scripts for you? It may be possible we're emitting a warning over stdout when we should be emitting over stderr
Yes - we run that shell command in what I believe is a non-login process and it still outputs the warning... I can't reproduce anymore as I updated the CLI...
Bug

What is the current behavior?
When using the
--json
flag (such as in the example above) Heroku shows update messages.What is the expected behavior?
It should not output update messages. Why? I would think that the vast majority of the time when someone uses
--json
they are intending to pipe the output into something likejq
. However, when the update message is present, the output string is not valid jsonThe text was updated successfully, but these errors were encountered: