AzurePowerShellV5 task can no longer run bicep deployment #4495
-
|
Linking an issue I raised in the azure-pipeline-tasks, since it is a bicep deployment issue that started happening last week. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 2 replies
-
|
Hi @thesushil this is related to a recent regression with the Azure PowerShell Module via New-AzResourceGroupDeployment. The regression means that dynamic parameters are not being processed correctly. You can for now roll back to a known good version of the AZ PowerShell Module via the following. # azurePowerShellVersion: 'LatestVersion'
preferredAzurePowerShellVersion: 6.3.0
pwsh: trueThis was discussed in #4210 and I believe a fix is on the way, it may just take a while for it to reach the DevOps task. |
Beta Was this translation helpful? Give feedback.
-
|
related to: Azure/azure-powershell#15841 |
Beta Was this translation helpful? Give feedback.
-
|
Thank you @brwilkinson. I saw that discussion, but it sounded like specific to ResourceGroup deployment, mine is at the subscription level. Changing the version to 6.3.0 as per your suggestion did solve my issue. |
Beta Was this translation helpful? Give feedback.
Hi @thesushil this is related to a recent regression with the Azure PowerShell Module via New-AzResourceGroupDeployment.
The regression means that dynamic parameters are not being processed correctly.
You can for now roll back to a known good version of the AZ PowerShell Module via the following.
https://docs.microsoft.com/en-us/azure/devops/pipelines/tasks/deploy/azure-powershell?view=azure-devops
This was discussed in #4210 and I believe a fix is on the way, it may just take a while for it to reach the DevOps task.