Open ChristopherGLewis opened 4 months ago
@ChristopherGLewis This is another instance of the short-circuiting issue that What-If faces. In MainSub.bicep, you have location: rg.location
, which is a runtime value that causes What-If to stop evaluating. We are currently working on a fix for What-If and will keep you updated on that process.
Any updates on status for fixing this short-circuting issue @sydkar? Any other issue where progress is tracked?
A status update on the fix process and links to any issues where progress is tracked would be helpful.
Particularly if any such progress tracking issues provide interim workaround steps.
An update was shared here:
Describe the bug I'm deploying a bicep module scoped at MG, Sub and RG and when deployed to either MG or Sub, it shows no pending changes.
When deployed at the RG scope, it works fine.
To Reproduce Steps to reproduce the behavior:
Code I'm deploying a very simple IP group module
IPGroup Module
MainRG.bicep
MainSub.bicep
MainRG.bicep
deploy-RG.ps1
deploy-Sub.ps1
deploy-MG.ps1
Resource Group Output
Subscription Output
Expected behavior What-if actually works the way it's supposed to.
I expect the Sub based deployment to show the same results. I've simplified this so that I'm not hitting any of the What-If limits
what-if-limits
Client [e.g. PowerShell, CLI, API)
This happens with the latest CLI and Powershell up to 7.3.9. Bicep version is 0.25.53