update-avm-modules-in-bicep

Overview

Update AVM Modules in Bicep is a skill that automatically scans Bicep infrastructure-as-code files for Azure Verified Module (AVM) references and updates them to their latest versions. It checks the Microsoft Container Registry for the newest tags, applies non-breaking updates, validates the changes with bicep lint and bicep build, and produces a summary table of all changes.

Key Features

• Automated Version Discovery - Scans Bicep files for avm/res/{service}/{resource} module references and fetches latest versions from the Microsoft Container Registry (MCR) tag list API
• Semantic Version Comparison - Parses and compares semantic versions to identify which AVM modules need updating, distinguishing between patch, minor, and major version changes
• Breaking Change Protection - Pauses for user approval when updates involve incompatible parameter changes, security/compliance modifications, or behavioral changes before applying
• Validation Pipeline - Runs bicep lint and bicep build after applying updates to ensure compliance and catch any issues introduced by version changes
• Structured Output - Produces a clear table with module name, current version, latest version, status icons, actions taken, and documentation links

Who is this for?

This skill is for Azure infrastructure engineers and DevOps teams who manage Bicep deployments using Azure Verified Modules. It is particularly useful for teams that need to keep their infrastructure-as-code up to date with the latest AVM releases while maintaining confidence that updates will not break existing deployments.