-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
[ARM] Fix various issues with az bicep
#31041
base: dev
Are you sure you want to change the base?
Conversation
️✔️AzureCLI-FullTest
|
️✔️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>
|
Please fix CI issues |
Related command
az deployment
az stack
az bicep
Description
This PR resolves two issues affecting the az deployment, az stack, and az bicep commands:
use_binary_from_path
is set totrue
andcheck_version
isfalse
.bicep install/upgrade
command downloads the x64 binary instead of the ARM binary.Closes #29809.
Closes #29435.
Testing Guide
az deployment tenant/mg/sub/group create
with a.bicepparam
file.bicep install/upgrade
on an aarch64 machine.History Notes
[ARM]
az deployment
/az stack
/az bicep
: Fix an issue where the commands mistakenly check for the latest Bicep version, even whenuse_binary_from_path
istrue
andcheck_version
isfalse
[ARM]
az bicep install / upgrade
: Fix an issue where the command downloads the x64 binary instead of the ARM binary on aarch64 machinesThis 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.