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
When using az deployment group what-if with Azure Bicep templates that are called via modules, only modules without any dependencies actually produce/show their output (ie. what will be created). All other resources are not listed, giving the incorrect assumption that they will not be created.
Command Name az deployment group what-if --resource-group GHES-aermie --template-file main.bicep
To Reproduce:
Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.
Describe the bug
When using
az deployment group what-if
with Azure Bicep templates that are called via modules, only modules without any dependencies actually produce/show their output (ie. what will be created). All other resources are not listed, giving the incorrect assumption that they will not be created.Command Name
az deployment group what-if --resource-group GHES-aermie --template-file main.bicep
To Reproduce:
Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.
Sample Bicep code
Expected Behavior
From the above-listed Bicep example, output for both the NSG and VNET is expected, but only output for the NSG is produced.
Environment Summary
Additional Context
It may be related to Issue #19308
The text was updated successfully, but these errors were encountered: