update-avm-modules-in-bicep

To update Azure Verified Modules in Bicep, this Skill scans your files, checks current module versions against the Microsoft Container Registry, and applies available updates automatically.

Breaking change detection for Bicep AVM module updates works by fetching module documentation for significant version changes, flagging potential breaking changes for manual review instead of applying them automatically.

Yes, you can automatically update AVM modules in a large Bicep project by scanning specified files to identify all modules, fetching latest versions from MCR, and applying non-breaking changes.

Updating Bicep modules includes syntax validation by running bicep lint and bicep build commands after applying changes, ensuring your updated infrastructure code remains valid and compliant.

When a Bicep AVM module update has a major version change, the process fetches documentation to review potential breaking changes and flags them for manual review rather than updating automatically.

The best way to handle non-breaking changes in Bicep AVM modules is to automate the version update process, which applies changes directly to your Bicep files and validates the syntax.