Azure
Bicep Community Call - September '24
We are hosting our September Bicep Community Call on Thursday, October 3rd at 9AM PST!
(We usually switch off from 9AM to 2PM PST every other month to accommodate for different time zones)
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!
I would like some status on this: https://github.com/Azure/bicep/issues/13674 and all issues related to it. It is quite big issue with language version 2 that deserves to be solved soon.
Folks - we (the Microsoft Graph team) hope to present our Microsoft Graph Bicep types GA plan at the community call on Oct 3rd. We'll have a few questions for you to make sure that this proposed GA release has the features you need, to be comfortable using it in production environments.
I won't be able to attend, but Jason and Eric will cover.
Any update on the issues relating to publishing to OCI registries and not only supporting ACR?
Azure/bicep#4884 Azure/bicep#4947
Has any progress been made using ORAS .NET client? If so would it be possible to get an update?
It would be great to use GitHub for our Bicep modules/vars. Currently we are publishing to ACR, then using ORAS cli to copy from ACR to GitHub, then use ACR cache on multiple instances to cache the Bicep artifacts. It would be nice if we could skip the ORAS cli copy step in this process and publish direct to GitHub.
To follow up from last time - a concern that was not addressed from the questions in last community call regarding what-if and permissions: https://github.com/Azure/arm-template-whatif/issues/135
Any updates to share on when to expect shared bicepparam files coming out of experimental for ga?
I would like to raise general issues with API versions. It seems there are API versions published to Bicep but not available in Azure. Something has to be done. Examples: https://github.com/Azure/bicep-types-az/issues/2185 https://github.com/Azure/bicep-types-az/issues/2319
Most likely these are not the only examples.
On top of that I think rule use-recent-api-versions should be refactored and should allow more options around preview versions and not only maxAgeInDays. I find this rule more and more useless due to different resource providers as it gives more false positives over time. My take:
- Preview versions should be included and not excluded. I think the majority of resource providers use preview versions in a way that many GA features are available in preview versions and not available in non-preview versions. Many of these resource providers even have only preview versions.
- Days should not be counted by default. Let's say I have a service for which the latest version is preview and 2022-06-01-preview and there is not newer version. That should not produce warning just because the resource provider hasn't issued newer version and I am using the latest available.
Unfortunately did not receive the invite to the call for this one. Was there any important updates that came out in the Community Call?
Thank you
Unfortunately did not receive the invite to the call for this one. Was there any important updates that came out in the Community Call?
Thank you
The calls are uploaded to YouTube within a few days after the call: https://www.youtube.com/@azuredeploymentsgovernance3067
But here's a high level :)
- MS Graph Bicep updates & Roadmap for GA and beyond
- Nameof() Function discussion
- Azure Verified Modules team updates
- Requested community updates from this thread
@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: https://github.com/Azure/bicep/issues/15441 https://github.com/Azure/bicep/issues/14063 https://github.com/Azure/bicep/issues/14064
@stephaniezyen because no thread available:
Would it be posssible that ARM/Bicep team gives some kind of comment for existing keyword abuse: https://github.com/Azure/bicep-types-az/issues/2320#issuecomment-2444537694
- 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: https://github.com/Azure/bicep/issues/4023?
@slavizh @jikuja added your comments to our next community call post here: #15655