Authoring and deploying Azure resources with Bicep | Azure Friday

[@paninger]

Scott is a real showmaster 👏 Very cool and authentic examples 👍 Entertaining and educational.

[@MicrosoftAzure]

We're happy to hear that you enjoyed the video! 😀

[@MrPinceldigital]

WOWWW Scott is the BESSSST in Microsoft - I see Azure Fridays just to see Scott questions and interaction! the Best EVER

Quote for today: With great power comes great complexity and a lot of JSON 💪

[@adamlindstrom4542]

2:02

[@NM-tr1ii]

Excellent intro about Bicep and you guys are so real!

[@tjpld]

Love Bicep. Only ran into a bit of a chicken and egg problem deploying a key vault with secrets. Ended up initializing them with dummy values which I then update via API calls later. They are not a lot so it works and I can make sure they aren't permanently visible in clear text anywhere, not even shell history or a script that injects them.

[@mfsbo]

Love how scott says with great power comes great amount of json

[@lalitjisoria]

This is the best azure Friday video so far. I just started learning Bicep and it is awesome. Can we convert Bicep file to terraform ? Just to make it cloud agnostic.

[@afhb21]

There is no ability to convert between Bicep and TF. While similar, there is not a guaranteed 1:1 translation between a bicep type and its TF equivalent.

[@SwatantraYadav]

Great introduction to bicep.

[@ruoxuan666]

Wow, bicep is so powerful. Could you share the demo repo?

[@sivaramagupta]

Hi there, I am using gitactions to create the CICD and try to deploy the azure components, I have tried many ways by using yaml or json. Is there any way we can only use bicep from gitaction and not use other formats. Is so please let me know the documentation kindly

[@MicrosoftAzure]

Hello there! The only way to describe GitHub actions workflows is via a YAML file that complies with their GitHub actions schema. It is not possible to use bicep in this case.

[@PrimephotoStudio]

Nice job on the video, very helpful.

[@MicrosoftAzure]

🙌 🤩

[@sivaramagupta]

For each and all resources end we are mentioning the version with the date name, instead, we can use it as the latest and backend Microsoft can map the updated to the 'Latest' keyword. the reason because I do need to change every time when the new version comes up.

[@MicrosoftAzure]

Thanks for the details! This seems like a better situation to post on the Azure Bicep GitHub discussions tab for some additional assistance. msft.it/6050efK7r

[@lalitjisoria]

There may be some breaking change with new version that might break your pipeline. I guess that's the reason its not there. Ex: addition of require parameter

[@sivaramagupta]

Finally, I have created a few resources using bicep. But I would like to give one parameter.json file and if i update the JSON parameter file with all parameter then it should deploy my resources. Can you guide me the process if possible

[@MicrosoftAzure]

Hi there! While we're unsure of how you are updating the parameters file, it is possible to wire up a CI/CD pipeline that will automatically redeploy the project if the bicep file or the parameters file is updated. Here’s some documentation on using bicep and GitHub Actions: msft.it/6058eQdQE

[@nnemakhavhani-up1986]

what a cool 'language' this is!

[@romanferguson4032]

awesome video thank you

[@adriangriffith7372]

Could someone please tell the host to BE QUIET. The part on using the 'existing' keyword is periously close to the end because he talks so much (bicep to arm is like typescript to javascript). I learned how to provide my storage account object to my application template thanks to the presenter. I can only imagine what I missed because of the host.

[@tarasbuha7726]

Don’t you think Pulumi is more powerful