Skip to content
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

CLI confirm-what-if doesn't recognize dependent resources #1715

Closed
JFolberth opened this issue Mar 4, 2021 · 3 comments
Closed

CLI confirm-what-if doesn't recognize dependent resources #1715

JFolberth opened this issue Mar 4, 2021 · 3 comments

Comments

@JFolberth
Copy link
Contributor

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 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.

@ghost ghost added the Needs: Triage 🔍 label Mar 4, 2021
@alex-frankel
Copy link
Collaborator

I think it is this issue: Azure/arm-template-whatif#157. Can you take a look?

@JFolberth
Copy link
Contributor Author

Agreed, provided feedback on what happens for redeployment.

@alex-frankel
Copy link
Collaborator

Closing and tracking with the what-if issue

@ghost ghost locked as resolved and limited conversation to collaborators May 28, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants