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
This should be addressed by an enhancement we're aiming to ship with 0.32. Bicep infers a deployment's dependency graph based and emits this as dependsOn properties in the compiled JSON template, and this logic was never updated to account for a backend change made some time ago to reduce the behavioral differences between "classic" ARM JSON template and language version 2.0 that would be observable to Bicep users.
FYSA, the line param eventTypes string[] is what's causing your template to compile with existing resources in the JSON template -- user-defined types require language version 2.0, which also makes existing resources first-class citizens in the JSON template.
Bicep version
v0.31.92
Describe the bug
Newly compiled ARM templates now require additional permissions for deployment.
To Reproduce
Steps to reproduce the behavior:
We have bicep module, which is deployed by principal with
EventGrid EventSubscription Contributor
RBAC role:bicep v0.30.23 generated next ARM template:
and bicep v0.31.92 generates
Microsoft.EventGrid/topics
existing resource requiresMicrosoft.EventGrid/topics/read
permission during deployment, butThe text was updated successfully, but these errors were encountered: