Customer feedback (both Core & extension) | all commands | output code blocks are needed in our reference content

[dbradish-microsoft]

Describe the bug

This GitHub issue is being moved from Azure DevOps UUF 343593, but I'm not assigning a specific Azure resource group as this is a recurring customer request and pertains to all of our reference content.

Engineering request

Until we have an output property for our autogenerated reference content, consider using the long-summary property to return possible command output. Please see @dcaro for additional feedback / ideas.

Per @calvinhzy, This will be a long term effort to add output examples as currently only some tutorials have sample output. Looking into using swagger to get a sample output.

Related issues

I'll continue to add to this list as more customer feedback is received.

• az storage queue | Customer feedback | az storage queue | No output example in documentation #29462
• az cosmosdb | https://dev.azure.com/msft-skilling/Content/_workitems/edit/343593

Customer feedback

Repo:

azure-docs-cli

Title:
az cosmosdb copy | Microsoft Learn

Verbatim:
Would appreciate some reference to what the output format of these commands looks like, specifically the show command. Since I am using these commands in scripts I need to know how to parse the output.

Verbatim Id:
2084b18a-7b9b-ef11-8a6a-6045bd02282e

Triaged By:
[email protected]

Triaged Comment:
This is actionable as we need to start collecting customer requests for output examples in autogenerated content.

Live URL:
https://learn.microsoft.com/en-us/cli/azure/cosmosdb/copy

GitHub URL:
https://github.com/MicrosoftDocs/azure-docs-cli/blob/live/2018-03-01-hybrid/docs-ref-autogen/cosmosdb/copy.yml

UUF Triage App Feedback URL:
https://aka.ms/UUFTriageApp?pageviewid=8aa50965-e49c-3904-bdba-08400b14ce92

Related command

All reference commands

Errors

.

Issue script & Debug output

.

Expected behavior

.

Environment Summary

Azure CLI 2.66.0

Additional context

No response

[yonzhan]

Thank you for opening this issue, we will look into it.

[microsoft-github-policy-service]

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @pjohari-ms, @kushagraThapar, @simplynaveen20.

[microsoft-github-policy-service]

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @xgithubtriage.