Fix and update azure dependency version ranges#31513
Fix and update azure dependency version ranges#31513janjagusch wants to merge 15 commits intoAzure:devfrom
Conversation
❌AzureCLI-FullTest
|
|
Hi @janjagusch, |
️✔️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>
|
| 'azure-cli-core=={}'.format(VERSION), | ||
| 'azure-cosmos~=3.0,>=3.0.2', | ||
| 'azure-data-tables==12.4.0', | ||
| 'azure-data-tables~=12.4.0', |
There was a problem hiding this comment.
| 'azure-mgmt-apimanagement==4.0.0', | ||
| 'azure-mgmt-appconfiguration==3.1.0', | ||
| 'azure-mgmt-appcontainers==2.0.0', | ||
| 'azure-keyvault-administration~=4.4.0b2', |
There was a problem hiding this comment.
There is now a stable 4.4.0 (and even a 4.5.0) release.
| 'azure-mgmt-appconfiguration==3.1.0', | ||
| 'azure-mgmt-appcontainers==2.0.0', | ||
| 'azure-keyvault-administration~=4.4.0b2', | ||
| 'azure-keyvault-certificates~=4.7.0', |
There was a problem hiding this comment.
| 'azure-keyvault-administration~=4.4.0b2', | ||
| 'azure-keyvault-certificates~=4.7.0', | ||
| 'azure-keyvault-keys~=4.11.0b1', | ||
| 'azure-keyvault-secrets~=4.7.0', |
There was a problem hiding this comment.
| 'azure-keyvault-keys~=4.11.0b1', | ||
| 'azure-keyvault-secrets~=4.7.0', | ||
| 'azure-mgmt-advisor~=9.0.0', | ||
| 'azure-mgmt-apimanagement~=4.0.0', |
There was a problem hiding this comment.
| 'azure-mgmt-applicationinsights~=1.0.0', | ||
| 'azure-mgmt-authorization~=4.0.0', | ||
| 'azure-mgmt-batchai==7.0.0b1', | ||
| 'azure-mgmt-batchai~=7.0.0b1', |
There was a problem hiding this comment.
| 'azure-mgmt-containerregistry~=14.0.0', | ||
| 'azure-mgmt-containerservice~=36.0.0', | ||
| 'azure-mgmt-cosmosdb==9.7.0', | ||
| 'azure-mgmt-cosmosdb~=9.7.0', |
There was a problem hiding this comment.
| 'azure-mgmt-datamigration~=10.0.0', | ||
| 'azure-mgmt-dns~=8.0.0', | ||
| 'azure-mgmt-eventgrid==10.2.0b2', | ||
| 'azure-mgmt-eventgrid~=10.2.0b2', |
There was a problem hiding this comment.
| 'azure-mgmt-eventhub~=10.1.0', | ||
| 'azure-mgmt-extendedlocation==1.0.0b2', | ||
| 'azure-mgmt-hdinsight==9.0.0b3', | ||
| 'azure-mgmt-extendedlocation~=1.0.0', |
There was a problem hiding this comment.
| 'azure-mgmt-extendedlocation==1.0.0b2', | ||
| 'azure-mgmt-hdinsight==9.0.0b3', | ||
| 'azure-mgmt-extendedlocation~=1.0.0', | ||
| 'azure-mgmt-hdinsight~=9.0.0', |
There was a problem hiding this comment.
| 'azure-mgmt-iothub~=3.0.0', | ||
| 'azure-mgmt-iothubprovisioningservices~=1.1.0', | ||
| 'azure-mgmt-keyvault~=11.0.0', | ||
| 'azure-mgmt-loganalytics~=13.0.0b4', |
There was a problem hiding this comment.
| 'azure-mgmt-policyinsights==1.1.0b4', | ||
| 'azure-mgmt-postgresqlflexibleservers==1.1.0b2', | ||
| 'azure-mgmt-policyinsights~=1.1.0b4', | ||
| 'azure-mgmt-postgresqlflexibleservers~=1.1.0', |
There was a problem hiding this comment.
| 'azure-mgmt-privatedns~=1.0.0', | ||
| 'azure-mgmt-rdbms==10.2.0b17', | ||
| 'azure-mgmt-mysqlflexibleservers==1.0.0b3', | ||
| 'azure-mgmt-rdbms~=10.2.0b17', |
There was a problem hiding this comment.
| 'azure-mgmt-servicebus~=8.2.0', | ||
| 'azure-mgmt-servicefabricmanagedclusters==2.1.0b1', | ||
| 'azure-mgmt-servicelinker==1.2.0b3', | ||
| 'azure-mgmt-servicefabricmanagedclusters~=2.1.0b1', |
There was a problem hiding this comment.
| 'azure-mgmt-storage==22.1.0', | ||
| 'azure-mgmt-synapse==2.1.0b5', | ||
| 'azure-mgmt-signalr~=2.0.0b2', | ||
| 'azure-mgmt-sqlvirtualmachine~=1.0.0b5', |
There was a problem hiding this comment.
| 'azure-mgmt-signalr~=2.0.0b2', | ||
| 'azure-mgmt-sqlvirtualmachine~=1.0.0b5', | ||
| 'azure-mgmt-sql~=4.0.0b21', | ||
| 'azure-mgmt-storage~=22.1.0', |
There was a problem hiding this comment.
| 'azure-mgmt-sqlvirtualmachine~=1.0.0b5', | ||
| 'azure-mgmt-sql~=4.0.0b21', | ||
| 'azure-mgmt-storage~=22.1.0', | ||
| 'azure-mgmt-synapse~=2.1.0b5', |
There was a problem hiding this comment.
| 'azure-monitor-query==1.2.0', | ||
| 'azure-multiapi-storage==1.4.0', | ||
| 'azure-mgmt-web~=7.3.1', | ||
| 'azure-monitor-query~=1.2.0', |
There was a problem hiding this comment.
evelyn-ys
left a comment
There was a problem hiding this comment.
Use ~= for keyvault data plane sdks are by design because beta versions allow breaking changes and it will cause Azure CLI break. That's why we pinned these beta versions
|
/azp run |
|
Azure Pipelines successfully started running 3 pipeline(s). |
|
We deliberately use Bumping Azure SDK versions needs to be done SDK by SDK with careful code inspection and testing. If you need a version bump for specific SDK, please create an issue and we'll review it (such as #31520, #31521). |
Thanks for the explanation. I'll open issues for the packages that I believe should be bumped, then. 👍 |
Related command
Description
The version pinnings in azure-cli's Python setup file are too tight. They often pin to an exact patch version, or, even worse, to an exact pre-release version. This prevents newer compatible package versions that fix bugs or vulnerabilities from getting installed automatically.
In this PR, I'm replacing all exact pinnings (
==) onazure-*packages with 'compatible release' pinnings (~=). The assumption is that allazure-*packages follow semantic versioning. I also updated the pinnings to use a compatible stable version, where available.For example:
azure-keyvault-administration==4.4.0b2->azure-keyvault-administration==4.4.0If also left PR comments showing the latest compatible version for each dependency.
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.