[ARM] az resource list: Include provisioningState property in table output#32156
Conversation
️✔️AzureCLI-FullTest
|
|
Hi @bennerv, |
️✔️AzureCLI-BreakingChangeTest
|
There was a problem hiding this comment.
Pull Request Overview
This PR fixes the Status field in table output for the az resource list command to properly display the provisioning state of Azure resources.
- Updates the resource list transformer to use the correct field path for provisioning state
- Changes from accessing nested
properties.provisioningStatusto top-levelprovisioningState
Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.
|
Thank you for your contribution! We will review the pull request and get back to you soon. |
|
The git hooks are available for azure-cli and azure-cli-extensions repos. They could help you run required checks before creating the PR. Please sync the latest code with latest dev branch (for azure-cli) or main branch (for azure-cli-extensions). pip install azdev --upgrade
azdev setup -c <your azure-cli repo path> -r <your azure-cli-extensions repo path>
|
az resource commandaz resource list: Include provisioningState in table output
az resource list: Include provisioningState in table outputaz resource list: Include provisioningState property in table output
Related command
az resource listDescription
The
az resource list -o tableoutput previously wouldn't populate theStatusfield which corresponds to provisioningState. With this change, the table output now contains the provisioning state of the resource.Note: the resources API is not returning the correct provisioning state for resources, this change does not fix this. I will open an ICM to the ARM team to address this.
Testing Guide
Before the change
after the change
History Notes
[resource] Populate the provisioningState as Status on table output for resource list
This checklist is used to make sure that common guidelines for a pull request are followed.
The PR title and description has followed the guideline in Submitting Pull Requests.
I adhere to the Command Guidelines.
I adhere to the Error Handling Guidelines.