-
Notifications
You must be signed in to change notification settings - Fork 3.3k
[Core] BREAKING CHANGE: Remove azure stack profiles 2020-09-01-hybrid, 2019-03-01-hybrid, 2018-03-01-hybrid and 2017-03-09-profile
#31307
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
Conversation
️✔️AzureCLI-FullTest
|
|
| rule | cmd_name | rule_message | suggest_message |
|---|---|---|---|
| cloud register | cmd cloud register update parameter profile: updated property choices from ['2017-03-09-profile', '2018-03-01-hybrid', '2019-03-01-hybrid', '2020-09-01-hybrid', 'latest'] to ['latest'] |
||
| cloud set | cmd cloud set update parameter profile: updated property choices from ['2017-03-09-profile', '2018-03-01-hybrid', '2019-03-01-hybrid', '2020-09-01-hybrid', 'latest'] to ['latest'] |
||
| cloud update | cmd cloud update update parameter profile: updated property choices from ['2017-03-09-profile', '2018-03-01-hybrid', '2019-03-01-hybrid', '2020-09-01-hybrid', 'latest'] to ['latest'] |
|
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>
|
| logger.error( | ||
| "The azure stack profile '{}' has been deprecated and removed, using the 'latest' profile instead.\n" | ||
| "To continue using Azure Stack please install the CLI `2.66.*` (LTS) version.".format(c.profile) | ||
| ) | ||
| c.profile = 'latest' |
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.
For azure stack users who already set the cloud config to azure stack profiles using old CLI versions, this error messages will be displayed. Here we replace the azure stack profiles by the latest profile instead of raising the CLIError, because if we raise error all the commands will be blocked, including the az cloud set --name xxx --profile latest command which is used to set the cloud config back to the latest profile.
There's no extensions in azure-cli-extensions repo support azure-stack profiles |
|
Could you add: more detail refers to http: XXX @mike will provide this link. |
Added the link https://learn.microsoft.com/en-us/cli/azure/whats-new-overview#important-notice-for-azure-stack-hub-customers |
zhoxing-ms
left a comment
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.
LGTM
|
cc @mtrilbybassett , the related monikers in current doc version picker might need to be updated on Learn site |
Related command
Description
The azure stack profiles are not supported since v2.73.0, because the support of multiple api-versions in the new python SDKs will be dropped.
The Azure CLI LTS version v2.66.x will keep azure stack profiles support.
Testing Guide
For the currently users who already configured the azure stack profiles in old cli versions they will get the following error messages and the latest profile will be used. They should use the

az cloud set --name xxxxx --profile latestcommand to change back thelatestprofile in the cloud config instead.For the new users, the azure stack profiles are removed from the choices of

--profileargument. We add the following information in the argument help.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.