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
Note the absence of the scope property in the role assignment resource.
To Reproduce
Download the file RoleAssignment.bicep.json
Rename the file RoleAssignment.bicep.json to RoleAssignment.bicep
Run the command: az bicep build -f RoleAssignment.bicep
Additional context
I would expect the bicep to generate the following ARM template which is a valid ARM template and allows us to create a central template for role assignment: Expected_RoleAssignment.json
The text was updated successfully, but these errors were encountered:
@stephaniezyen, @shenglol, I understand that the proposal described in #2246 is to allow the passing of the resource as a parameter.
While this would solve my initial problem, the current work-around should also work. However, it seems like the current bicep file is not correctly compiled as an ARM file. So it feels a bit wrong to just close this as the passing of the resource will not actually fix the compilation of the current bicep file. (It will however make the current work-around obsolete)
Bicep version
0.24.24
Describe the bug
As described in GitHub issue - Scope can not be passed as a parameter to a module #3626 , a scope cannot be passed as a parameter. So in order to be able to extract our role assignments into one template, we started with the following implementation:
RoleAssignment.bicep.json
When compiling this bicep file into ARM, it generates the following ARM: Generated_RoleAssignment.json
Note the absence of the scope property in the role assignment resource.
To Reproduce
Additional context
I would expect the bicep to generate the following ARM template which is a valid ARM template and allows us to create a central template for role assignment: Expected_RoleAssignment.json
The text was updated successfully, but these errors were encountered: