New-AzResourceGroupDeployment - Update Bicep Version?

[hwwilliams]

Description

How do I update the Bicep version used by New-AzResourceGroupDeployment?

There is currently a bug in 34.1 that is affecting my companies work and no matter what we do to update the version using az bicep upgrade the PowerShell command continues to use the bugged version as shown below in the image.

Azure/bicep#16676

This Bicep is being ran on the GitHub runner ubuntu-latest.

Script or Debug output

az bicep upgrade

$AzResourceGroupDeploymentParameters = @{
    Force                      = $true
    Mode                       = "Incremental"
    Name                       = $Name
    ResourceGroupName          = $ResourceGroupName
    TemplateFile               = "./bicep/main.bicep"
    Verbose                    = $true
}
New-AzResourceGroupDeployment @AzResourceGroupDeploymentParameters

Environment data

Module versions

Error output

[hwwilliams]

This started working temporarily on Tuesday earlier this week without us changing anything and PowerShell was using 34.44 version of Bicep but today when I try to use it again it is back to using 34.1 of Bicep without me changing anything.

[microsoft-github-policy-service]

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @Azure/deployments-owners.

[anthony-c-martin]

See Install Bicep Tools. Azure PowerShell doesn't do anything special to manage a Bicep installation - Azure PowerShell just uses whatever is on the $PATH

If you're not installing the Bicep CLI yourself, then presumably the image you are using in your Github runner is bundling a particular version. If so, then I'm assuming this must have been upgraded, hence why things started working again.

[hwwilliams]

See Install Bicep Tools. Azure PowerShell doesn't do anything special to manage a Bicep installation - Azure PowerShell just uses whatever is on the $PATH

If you're not installing the Bicep CLI yourself, then presumably the image you are using in your Github runner is bundling a particular version. If so, then I'm assuming this must have been upgraded, hence why things started working again.

Apparently you didn't read the issue at all as you can see in the image that I am upgrading Bicep using the CLI but then PowerShell doesn't respect it.

[microsoft-github-policy-service]

🔔 Routing this issue to @act-identity-squad.

[anthony-c-martin]

See Install Bicep Tools. Azure PowerShell doesn't do anything special to manage a Bicep installation - Azure PowerShell just uses whatever is on the $PATH
If you're not installing the Bicep CLI yourself, then presumably the image you are using in your Github runner is bundling a particular version. If so, then I'm assuming this must have been upgraded, hence why things started working again.

Apparently you didn't read the issue at all as you can see in the image that I am upgrading Bicep using the CLI but then PowerShell doesn't respect it.

Apologies for the massive delay in responding (almost exactly a year). I did want to clarify that I did read + understand what you'd written, but I didn't explain the reasoning clearly enough in my response.

To clarify for anyone else coming across this issue:

1. Azure PowerShell uses an existing version of Bicep CLI that's resolved from the the system $PATH env variable.
2. Azure CLI manages its own installation of Bicep CLI under ~/.azure/bin/bicep. This is typically NOT included in the system $PATH unless someone has explicitly added configured it to be.
3. As a result, when you run az bicep upgrade, only the version of Bicep CLI installed to ~/.azure/bin/bicep is being upgraded. This has no effect on the version of Bicep CLI that Azure PowerShell uses.