Session

Govern your bicep modules with a CI/CD approach

One of the main benefits of using bicep as your language for Infrastructure as Code on Azure is how easy it is to reuse your code via bicep modules.

However, sharing them with your colleagues may become challenging if you're working in a team: you need to be sure that everyone is using a working release, and possibly the latest one.

You can improve your process for authoring, testing, and sharing your modules by leveraging a CI/CD pipeline and a bicep registry.

Let's see together an example of how you can implement a pipeline that validates your bicep files, executes a test deployment, and push your bicep to the registry applying a version tag to them.

Marco Obinu

former Azure MVP, Azure Technical Trainer @ Microsoft, Geek to the bone

Arenzano, Italy

Actions

Please note that Sessionize is not responsible for the accuracy or validity of the data provided by speakers. If you suspect this profile to be fake or spam, please let us know.

Jump to top