Bicep Community Call - December '24

[stephaniezyen]

We are hosting our last Bicep Community Call of the year on Thursday, December 5th at 9AM PST!

Use this issue to address topics you would like to discuss, questions you have for our team, further demos you would like to see, and any high or low points you would like to share. This is an open space for our users to discuss any topics they would like to talk about with our team.

You can list topics of discussion in this thread OR you can ask questions during the Q&A portion of the call.

Please sign up here to get an invite to our Community Call series. See you there!

[stephaniezyen]

Copying over comments from: #15147

"@stephaniezyen I do not see thread for the next community call so posting the issues I would like to get some information on the next one:
#15441
#14063
#14064"

"Would it be posssible that ARM/Bicep team gives some kind of comment for existing keyword abuse: Azure/bicep-types-az#2320 (comment)

team mate of mine fell on this trap and used time to solve issue via support just to find that sources they trusted were wrong
I've seen this as solution on multiple tickets
Should documentation has more warnings than current "If you attempt to reference a resource that doesn't exist, you get the NotFound error and your deployment fails. Check the name and scope of the resource you're trying to reference." that does not happen always

Also what is the status of the related ticket: #4023?"

[GABRIELNGBTUC]

Would it be possible to get some feedback about the feasibility of creating a stop gap solution at compile time for #1876?

It looks like an issue related to this is created every month and looking at #15517, it looks like that even the AVM registry is unknowingly publishing templates with conditional scopes which are compiled to deploy to the current scope and not any of the scopes in the conditional.

Someone proposed adding a linter rule when using a ternary on the scope property #15651 (comment) and it would be interesting to know if it was possible to add such rule in the short term as well as maybe updating the documentation to show how to currently conditionally choose a scope with the current limitations.

[ttq-ak]

Has there been any thought into dependabot support for bicep modules used from a registry? (As suggested here: Azure/bicep-registry-modules#452)
We have lots of different projects using our internal modules and it would be great to know they're being updated in dependent repositories when I push fixes/features