{Core} Fix infinite wait for typespec generated SDK#32687
{Core} Fix infinite wait for typespec generated SDK#32687
Conversation
️✔️AzureCLI-FullTest
|
|
Hi @evelyn-ys, |
️✔️AzureCLI-BreakingChangeTest
|
|
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>
|
There was a problem hiding this comment.
Pull request overview
Updates Azure CLI wait logic to correctly extract provisioning state from TypeSpec-generated SDK models and prevent infinite waits (e.g., az xxx wait).
Changes:
- Switches wait provisioning-state extraction to use
azure.cli.core.util.todict(TypeSpec-aware) instead ofknack.util.todict.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
|
Hey guys, as the wait worked in the version 2.81.0, is it worth to consider a patch version with this fix? |
Related command
az xxx waitDescription
Fix #32656
After migrating to typespec generated SDKs, we should use new
todictfunction defined inazure.cli.core.utilinstead of oldknack.util. Here are some background PRs: #30339, #32419 (comment)This PR updates the
todictfunction we used for getting provisioning state info for allaz xxx waitcommands. With the oldtodict, we will get an empty{}for typespec generated SDK models so that no provisioning state returned which will cause infinite wait.Testing Guide
az keyvault wait -n $vaultName -g $rgName --createdHistory Notes
[Component Name 1] BREAKING CHANGE:
az command a: Make some customer-facing breaking change[Component Name 2]
az command b: Add some customer-facing featureThis 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.