Describe the bug
When using an existing reference to compute properties for the resources to create in bicep, module is not idempotent.
Indeed, successive re-execution of the whatif will show modifications even though it would resolve to the same values.
For instance, i see this in the whatif:
Creation is working fine.
My issue is the non-idempotence when re-executing the same bicep a second time with whatif, to check infra is in proper/expected state.
Bicep version 0.26.54 (5e20b29b58)
Describe the bug When using an existing reference to compute properties for the resources to create in bicep, module is not idempotent. Indeed, successive re-execution of the whatif will show modifications even though it would resolve to the same values. For instance, i see this in the whatif:
if i apply the deployment, no change appear as the computed name is (as expected) : "toAzure10.55"
To Reproduce
dnsServers also tried to replace computed value with
despite resolving to the same values....
Creation is working fine. My issue is the non-idempotence when re-executing the same bicep a second time with whatif, to check infra is in proper/expected state.