Consider a machine-readable form of output that would allow command redirection at least at the shell level.
Note that click itself does not really support the idea of redirection in the interactive mode (output of one command available as input to the next command) but we could use the click context as a way to pass results to input in the interactive mode (Which would make the command mode different than the interactive mode).
Some examples of usage might be: Run a command to get the namespaces and then run another command on all of those namespaces. The easiest idea for this is the processing of things like connection names, instancenames, classnames, and namespace names. or lists of the same.
Consider a machine-readable form of output that would allow command redirection at least at the shell level.
Note that click itself does not really support the idea of redirection in the interactive mode (output of one command available as input to the next command) but we could use the click context as a way to pass results to input in the interactive mode (Which would make the command mode different than the interactive mode).
Some examples of usage might be: Run a command to get the namespaces and then run another command on all of those namespaces. The easiest idea for this is the processing of things like connection names, instancenames, classnames, and namespace names. or lists of the same.