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
Currently, commands output status messages giving the user an idea of the progress and what's happening behind the scenes. While useful, this will be problematic, when the CLI gets support in non-interactive mode and users would like to pass the output of one command into another.
To prevent commands from having to parse string output of command messages when receiving input from another commands, commands should by default work in silent mode, where only the result of the command is displayed (eg. list of apps, tenant settings, etc). Status messages can be displayed by running the command in verbose mode. Current verbose mode, should be renamed to debug as it outputs very detailed information which is required only when debugging the CLI.
rename verbose to debug
add new global option --verbose
wrap current status messages with verbose
ensure commands output nothing but their direct output
The text was updated successfully, but these errors were encountered:
Currently, commands output status messages giving the user an idea of the progress and what's happening behind the scenes. While useful, this will be problematic, when the CLI gets support in non-interactive mode and users would like to pass the output of one command into another.
To prevent commands from having to parse string output of command messages when receiving input from another commands, commands should by default work in silent mode, where only the result of the command is displayed (eg. list of apps, tenant settings, etc). Status messages can be displayed by running the command in verbose mode. Current verbose mode, should be renamed to debug as it outputs very detailed information which is required only when debugging the CLI.
--verbose
The text was updated successfully, but these errors were encountered: