{Keyvault} Upgrade data plane sdk to stable version#31898
{Keyvault} Upgrade data plane sdk to stable version#31898
Conversation
️✔️AzureCLI-FullTest
|
️✔️AzureCLI-BreakingChangeTest
|
|
Thank you for your contribution! We will review the pull request and get back to you soon. |
There was a problem hiding this comment.
Pull Request Overview
This PR upgrades Azure Key Vault data plane SDK dependencies from beta versions to stable versions to improve security, quality, and stability. The changes replace beta SDK versions (4.4.0b2 and 4.11.0b1) with their stable counterparts (4.4.0 and 4.11.0).
- Updates azure-keyvault-administration from version 4.4.0b2 (beta) to 4.4.0 (stable)
- Updates azure-keyvault-keys from version 4.11.0b1 (beta) to 4.11.0 (stable)
Reviewed Changes
Copilot reviewed 4 out of 4 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| src/azure-cli/setup.py | Updates Key Vault SDK versions in the main setup dependencies |
| src/azure-cli/requirements.py3.windows.txt | Updates Key Vault SDK versions for Windows platform requirements |
| src/azure-cli/requirements.py3.Linux.txt | Updates Key Vault SDK versions for Linux platform requirements |
| src/azure-cli/requirements.py3.Darwin.txt | Updates Key Vault SDK versions for macOS platform requirements |
|
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>
|
| azure-keyvault-keys==4.11.0b1 | ||
| azure-keyvault-keys==4.11.0 | ||
| azure-keyvault-secrets==4.7.0 | ||
| azure-keyvault-securitydomain==1.0.0b1 |
There was a problem hiding this comment.
azure-keyvault-securitydomain doesn't have any stable version so we can't upgrade at the moment
Related command
Description
To ensure security, quality and stability, we should use stable version SDKs instead of beta versions
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.