What is the vision for deployment of infrastructure as code using Bicep?

[rpothin]

Hello everyone,

Since I started to test Bicep few days ago, I am wondering how you see it used in deployments of infrastructure as code.

You will find below how I see it today, but perhaps I am totally wrong 😅:

• In your repository you will push your Bicep code and your parameters files (JSON)
• A build pipeline / GitHub actions (or other) will
  • generate the ARM template from the Bicep code
  • eventually execute a "deployment validate" to check for errors
  • eventually run some "tests", using for examples Azure Resource Manager Template Toolkit
• A deployment pipeline that will execute the "deployment create"

Thank you in advance for your point of views regarding this subject.
I am really looking forward your vision and your ideas.

Have a nice weekend all!

[alex-frankel]

I think you've got it exactly right. Once #858 is done, you won't need to transpile the code yourself unless you need it for something like TTK, which does not yet support evaluating a .bicep file.

[rpothin]

Hey @alex-frankel,

Thank you very much for your answer.

I assume that the goal of what you are doing in the issue #858 is to manage the hard work for us behind the scene: generate the ARM template and create the deployment from it. Am I right? 😊

Regarding the parameters' file,

• will it be possible to pass it to the command like presented below?

az deployment group create -f ./main.bicep -g my-rg -p ./main.parameters.json

• will it be possible to directly generate the parameters' file from Bicep code using the VS Code extension?

Last question, having the ability to create a deployment from a Bicep file using Azure CLI or PowerShell is already awesome, but is it in the roadmap to add this feature it in the ARM template deployment task in Azure DevOps? Or to create a new one, Bicep deployment perhaps 🤔?

Thank you in advance for your answers and have a nice day.