-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
{Keyvault} Vendor azure-keyvault
track1 SDK to make customization for supporting Python 3.11
#27148
Conversation
️✔️AzureCLI-FullTest
|
️✔️AzureCLI-BreakingChangeTest
|
Keyvault |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Did you test how many extensions will be affected?
Should we use a separate PR to fix the usage of Line 62 in df516d7
|
This is a good point and reminds me that once we start bundling Python 3.11, extensions that don't support Python 3.11 will be broken. |
Yes I have triggered extension regression pipeline and manually check the failure extension tests. The failures are not caused by keyvault |
|
Description
Keyvault module now depends on
azure-keyvault
(api version2016-10-01
and7.0
)az keyvault security-domain
command group (api version7.2
)azure-keyvault-keys
/azure-keyvault-secrets
/azure-keyvault-certificates
/azure-keyvault-administration
But track1 sdk can't work with Python 3.11 because sdk uses
inspect.getargspec
which has been dropped in Python 3.11.This PR removes public track1 sdk dependency and migrate all related commands to use vendored track1 sdk so that we can customize sdk code to unblock Python 3.11 support as a tmp workaround. Considering track1 sdk is not maintained and won't release new version anymore, our goal is to fully migrate all track1 sdk dependency to track2 which needs to be planned ASAP.
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.