Introduce markdown output for documentation purposes

[waldekmastykarz]

What do you think if we introduced in the CLI markdown output? It could be useful for generating documentation for the current configuration.

This idea is based on this thread on twitter: https://twitter.com/wictor/status/1463879429889867783?s=21 started by @wictorwilen

[garrytrinder]

I'm not sure I understand the use case, could you offer an example?

[wictorwilen]

@garrytrinder - I can give you a great example. Assume that a person is building an app, perhaps for a conference demo. Then you do want to document the settings you have for the AAD app (scopes, app id uri's) or something else and put in your readme file in a human readable format.

[garrytrinder]

@garrytrinder - I can give you a great example. Assume that a person is building an app, perhaps for a conference demo. Then you do want to document the settings you have for the AAD app (scopes, app id uri's) or something else and put in your readme file in a human readable format.

Thanks @Wictor that makes perfect sense.

So in that scenario, is the idea that the user would execute add app get --output md which provides a pre-formatted output in markdown?