You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 latest command to change back the latest profile in the cloud config instead.
For the new users, the azure stack profiles are removed from the choices of --profile argument. 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 feature
This checklist is used to make sure that common guidelines for a pull request are followed.
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).
After that please run the following commands to enable git hooks:
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.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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.