Janne Kujanpää

Role assignments with bicep documentation has a good explanation how and why use deterministic naming with guid-typed name property: https://learn.microsoft.com/en-us/azure/azure-resource-manager/bicep/scenarios-rbac#name

Similar discussion within scope of Bicep templating here: https://github.com/Azure/bicep-registry-modules/issues/949 Retaining configuration values is possible but required extra templating and/or extra tools.

Is suggest subscribing also https://github.com/Azure/bicep-registry-modules/issues/949 for a reference. Sadly looks like the issue is being stalled on AVM too.

From [monthly call](https://youtu.be/UuwhLi-Xe2U?t=1912): (I would have posted this earlier but missed capturing screenshot from live presentation) The demo on monthly was really good: 5/5 probably will check again soon. -----...

> If process scope environment variables are intended to be unsupported What do you mean by `process scope environment`? > What are your tips about defining default values locally to...

Weird. How do you invoke Bicep? Result on my machine: ``` bicep --version Bicep CLI version 0.18.4 (1620479ac6) ``` --- other cosmetic issue: related with my earlier comment about tooling...

> @jikuja latest release is 0.19.x so try update bicep cli Same results. Works for me, no regression.

Start of discussion: How Hedge should support multiple clouds with one build.boot file? One solution: ```clojure (set-env! :source-paths #{"src"} :resource-paths #{"resources"} :dependencies ' [siili/boot-hedge "0.0.4-SNAPSHOT" :scope "test"] [siili/hedge "0.0.4-SNAPSHOT"] ])...

I suggest also adding support for role assignments(for environment security) to circumvent some problems(1) Azure devops has: *`https://dev.azure.com/{organization}/_apis/securityroles/scopes/distributedtask.globalenvironmentreferencerole/roleassignments/resources/{something}` * https://learn.microsoft.com/en-us/rest/api/azure/devops/securityroles/roleassignments/set-role-assignment?view=azure-devops-rest-7.1 (1) https://developercommunity.visualstudio.com/t/Environments-Permissions-changing-not-po/872257

> Only block public access to UI is not a feasible solution since people still can access ADF service through API. So the better solution is to disable all ARM...