Refactor text output

[waldekmastykarz]

I'd like to propose that in v4 we refactor the text output mode:

1. We rename it to table so that it's clearer what it does. Since in the terminal everything is text, text isn't pretty descriptive. Using table instead would be clearer and we'd align with the Azure CLI
2. We change it so that you always get to see a table. Right now, if you get just one result, we transpose the output so that you get a key-value pair output where each pair is printed in a new line. Originally we introduced it for readability but I'm not sure if it's worth the effort and if consistency wouldn't be preferable.

[garrytrinder]

I agree with you that introducing table would be a good idea, however we should still have a text output.

In many Azure CLI examples, the tsv format is used when returning strings as it removes extra formatting, see the below statement from the Azure CLI docs.

Be sure to use the tsv output type. Other output types may contain unwanted symbols such as quotation marks.

Output formats for the Azure CLI, TSV output format - https://docs.microsoft.com/en-us/cli/azure/format-output-azure-cli#tsv-output-format
Use Azure CLI effectively, Pass Values to another command - https://docs.microsoft.com/en-us/cli/azure/use-cli-effectively#pass-values-to-another-command

[appieschot]

Nothing to add 😂. Agree with default to table, makes sense for quickly reading output. Personally use json a lot in scrips but always use the text output when checking results of single commands.

[waldekmastykarz]

@appieschot so the idea was to actually replace the default output with JSON, like you have in the Azure CLI and then rename text to table and make it explicit 🙂

[appieschot]

Even better!

[Adam-it]

aaa so that's what --output text actually is 😅.

[waldekmastykarz]

We had big plans for it, but it turned out that it's not as simple as we thought @Adam-it. Check out #2544 for more info