{Keyvault} Bump azure-keyvault-keys to 4.11.0b1 - #31288
Conversation
️✔️AzureCLI-FullTest
|
|
Hi Yishi Wang (@evelyn-ys), |
❌AzureCLI-BreakingChangeTest
Please submit your Breaking Change Pre-announcement ASAP if you haven't already. Please note:
|
|
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>
|
The KeyVaultPreparer was pinned to --enable-rbac-authorization false (Access-Policy mode) by commit cd9a1ae (Azure#31288), but the CMK encryption identities are granted via RBAC role assignments (Key Vault Crypto Service Encryption User). AP-mode vaults ignore RBAC assignments, so 'backup vault encryption update' failed live with 403 UserErrorCMKKeyVaultAuthFailure. Flip the preparer to --enable-rbac-authorization true so the (live-only) RBAC grants take effect. Grants stay commented because role assignments use non-deterministic GUIDs that cannot be recorded/replayed; re-recorded the cassette. Verified: playback passes, live passes. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Related command
Description
This PR bumps API version for keyvault key from 7.5-preview.1 to 7.6-preview.2
Will add new feature support for key attestation in separate PR
Testing Guide
History 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.