Bicep Community Call - April '23

[stephaniezyen]

We are hosting our April Bicep Community Call next Thursday, April 27th at 2PM PST!

(We will 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 the call. See you there!

[josh-bennett-cubesys]

My current process is deploying automation accounts into a resource group using bicep through Azure DevOps. I have the runbook code hosted on DevOps as well, but there doesn't seem to be an easy way to get this code through to a bicep uploaded runbook without adding it to a public url or storage account with an key. Is there any different way to get local DevOps code pushed to a runbook deployed with bicep? Or is there a best practice around doing this in a nice workflow?

[WhitWaldo]

Always eager to hear regular updates about the current state of custom types, cross-module imports, resources as outputs and any potential ETAs for delivery of each! Thanks!

[Kaloszer]

#645 - wanted to ask if there's any plans to include that sometime in the near future

[alex-frankel]

My current process is deploying automation accounts into a resource group using bicep through Azure DevOps. I have the runbook code hosted on DevOps as well, but there doesn't seem to be an easy way to get this code through to a bicep uploaded runbook without adding it to a public url or storage account with an key. Is there any different way to get local DevOps code pushed to a runbook deployed with bicep? Or is there a best practice around doing this in a nice workflow?

@josh-bennett-cubesys -- I would open a separate "Discussion" topic for this one. I don't think there is anything we can do on the Bicep side to make this easier. The Automation Resource Provider team would need to support pulling from DevOps/GitHub/etc. as a feature of their service.

[WhitWaldo]

We didn't talk about these today for lack of a QA, but I'm leaving them here as a note to bring up next month to seek updates on then:

• Feature: Augment map function to also include index of item #9462
• Add index parameter to all list processing lambda reduce functions #9244
• Ability to use resources in outputs instead of passing around lookup identifiers all over the place
• Will we be able to create/update AAD apps via the AAD extensibility provider?

Thanks for the time today!