Open dbradish-microsoft opened 8 months ago
Hi @dbradish-microsoft Find similar issue https://github.com/Azure/azure-cli-extensions/issues/8060. | ||
---|---|---|
Issue title | az aks app up | Provide list of azCLI reference commands being executed in in-line help |
Create time | 2024-03-14 | |
Comment number | 0 |
Please confirm if this resolves your issue.
Thank you for opening this issue, we will look into it.
Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @dkkapur.
@dkkapur, Can we resolve this issue by putting a sentence in the short or long summary that states something like "Run this command with the --debug
parameter to see the API calls and parameters values being used."?
This avoids a lengthy long-summary property, but tells the customer how to find the answer for themselves.
Describe the bug
Customers are asking what Azure CLI reference commands are being executed by our az ... up commands. Doc writers are also requesting this information when they must replicate Azure CLI docs with Azure PowerShell commands. Although the reference list might change based on the parameters being passed, we need clarity in our in-line help and resulting autogenerated reference content.
Reference command link: https://learn.microsoft.com/en-us/cli/azure/container/app#az-container-app-up Related reference command link: https://learn.microsoft.com/en-us/cli/azure/containerapp#az-containerapp-up
Current description of "az container app up":
Deploy to Azure Container Instances using GitHub Actions.
Current description of "az containerapp up":Create or update a container app as well as any associated resources (ACR, resource group, container apps environment, GitHub Actions, etc.).
REQUEST: Please modify these descriptions to list each Azure CLI reference command that "up" can/is executing.
Possible impacted source code files (where this descriptions are found): az container app up
az containerapp up
Related command
az container app up
andaz containerapp up
QUESTION: Is this spelling on purpose, or is this something we are fixing?
Errors
n/a
Issue script & Debug output
n/a
Expected behavior
n/a
Environment Summary
Azure CLI 2.58.0
Additional context
No response