Skip to content

EES-6021 Search infrastructure Bicep deployments are failing caused by bug in Azure CLI #5770

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

Merged
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -22,13 +22,8 @@ jobs:
- checkout: self
- download: none

- task: AzureCLI@2
displayName: Install Bicep
inputs:
azureSubscription: ${{ parameters.serviceConnection }}
scriptType: bash
scriptLocation: inlineScript
inlineScript: az bicep install
- script: az upgrade --yes
displayName: Upgrade Azure CLI and extensions

- template: ../tasks/deploy-bicep.yml
parameters:
Expand Down
4 changes: 4 additions & 0 deletions infrastructure/templates/search/ci/tasks/deploy-bicep.yml
Original file line number Diff line number Diff line change
Expand Up @@ -32,6 +32,10 @@ steps:
inlineScript: |
set -e

# Workaround for AZ CLI 2.71.x breaks bicep deployments when using Azure Devops Agent
# See https://github.com/Azure/azure-cli/issues/31189
az config set bicep.use_binary_from_path=false

az deployment group ${{ parameters.action }} \
--name $(infraDeployName) \
--resource-group $(resourceGroupName) \
Expand Down