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
Describe the bug
Using series of Modules that have dependencies on each other via outputs. (i.e. App service plan pass plan ID to app service).
When running -c at the end of a az deployment sub create command it doesn't recognize the dependencies in the what if scenario. Confirm after running my deployment everything was created; however, does not match the plan. This deployment is at the subscription scope.
Not sure if this is a bug with the azure cli as I haven't tested this with other ARM templates but figured start here.
To Reproduce
Steps to reproduce the behavior:
Try running a what if against a bicep file with dependencies between modules.
The text was updated successfully, but these errors were encountered:
Bicep version
3.1
Describe the bug
Using series of Modules that have dependencies on each other via outputs. (i.e. App service plan pass plan ID to app service).
When running
-c
at the end of aaz deployment sub create
command it doesn't recognize the dependencies in the what if scenario. Confirm after running my deployment everything was created; however, does not match the plan. This deployment is at the subscription scope.Not sure if this is a bug with the azure cli as I haven't tested this with other ARM templates but figured start here.
To Reproduce
Steps to reproduce the behavior:
Try running a what if against a bicep file with dependencies between modules.
The text was updated successfully, but these errors were encountered: