Columnise find to reduce output width #12409
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The output find is rather large, now that we have more and more
populated fields, we're potentially showing to much information. Instead
of just removing the fields that look unimportant, we should tailor it
depending on the users needs.
This PR introduces columns for the tabular field. Using --columns flag
with the column alias seems like a decent approach. Other canonical
tools also do this, so it isn't something new (LXD).
With decent defaults it actually looks rather good as well.
QA steps
Default column output
$ juju bootstrap lxd test $ juju find kubernetes
Tailoured
$ juju bootstrap lxd test $ juju find --columns=nbvaS