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
The outputs of the list/show subcommands are quite different in format and arguments, and some of their outputs are not currently very useful. We should make them more consistent for a better user experience.
To clarify, I think there's two big reasons to have the cli tools in addition to the python api, which we should emphasize in the design:
Convenience: not needing to fire up a python environment when working in a shell. Most housekeeping/setup tasks are done from shell rather than python in our current docs & usage.
Ability to easily use these tools together with the rest of the cli/bash/excel/etc software ecosystem. Many of the current output formats are currently not very convenient for piping to other tools. Ability to parse/extract values from the output is a plus. The dataset commands have a --format specifier for getting the output in parse-able formats like csv, which traditionally Ops used quite heavily.
The outputs of the
list
/show
subcommands are quite different in format and arguments, and some of their outputs are not currently very useful. We should make them more consistent for a better user experience.The text was updated successfully, but these errors were encountered: