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
{{ message }}
Repository navigation
auth0 users show --json emits non-JSON text (tenancy info) #1270
An approach could be to have some cli flags which can omit all the content that is sent to stderr. As it stands, many work-arounds are required to avoid causing errors in CICD when the auth0 cli tooling continually writes messages into stderr.
stderr should indeed be reserved for errors; not used as regular output. Full stop - standard behaviour should not be conditional on any flag or option.
All said, we’ll definitely give this more thought for a future major release and see if we can make the experience more robust. Instead of closing this issue, we are going to park this in under Discussions and hear more from the community.
Activity
ramya18101 commentedon Jul 11, 2025
Hello @ad8-bdl ,
Yes, We noticed about the tenancy information which leads to stderr, I'm creating a task internally and shall pick this up shortly.
michaelbiriley-auror commentedon Jul 21, 2025
An approach could be to have some cli flags which can omit all the content that is sent to stderr. As it stands, many work-arounds are required to avoid causing errors in CICD when the
auth0cli tooling continually writes messages into stderr.ad8-bdl commentedon Jul 22, 2025
stderrshould indeed be reserved for errors; not used as regular output. Full stop - standard behaviour should not be conditional on any flag or option.ramya18101 commentedon Aug 7, 2025
Hello @ad8-bdl, @michaelbiriley-auror
Thank you for your thoughtful feedback. We completely agree with the points you raised. but changing the existing behavior would affect current users.
With the new
--json-compactflag, all header messages are fully suppressed, preserving clean, parsable output for automation use.ramya18101 commentedon Aug 18, 2025
All said, we’ll definitely give this more thought for a future major release and see if we can make the experience more robust. Instead of closing this issue, we are going to park this in under Discussions and hear more from the community.