Richard "Rick" Roché

Software Engineer, Solutions Architect, Hiking Enthusiast

Bicep Modules: Refactor, Compose, Reuse

In my previous post I touched on the things I learnt while migrating ARM templates to Bicep. Bicep also introduces the concept of modules to enable template reuse. I took some time to refactor a composite application that had already been converted from using ARM to Bicep templates, to use Bicep modules. This post will cover the things that I learnt by working through that process. Why modules? From the Bicep documentation:

Migrating Azure ARM templates to Bicep

You may have heard of Bicep, and you may be wondering how much effort it is going to take to move all your ARM templates to this new way of deploying Azure resources. I gave migrating from ARM to Bicep a go. This post will cover going from JSON ARM templates to shiny new Bicep templates that have no errors and don’t contain any warnings or linting issues! Why should you migrate?

Azure Pipelines and Dependabot

Keeping your dependencies up to date in a project is a really easy way to try and keep the software secure. New releases of a dependency often include

  • Patches for security vulnerabilities!
  • Performance improvements!
  • Awesome new features!
  • Bug fixes!

It can also be quite a boring activity and can be time-consuming for a team maintaining the project to run updates regularly into production. Fortunately tools like Dependabot exist!