Azure Verified Modules (AVM) is an initiative to consolidate and set the standards for what a good Infrastructure-as-Code module looks like. Modules will then align to these standards, across languages (Bicep, Terraform etc.) and will then be classified as AVMs and available from their respective language specific registries.
[Documentation Update]: New Spec - All Bicep resource modules MUST leverage the common type utility module for shared interfaces (document exceptions) #1560
[x] I have checked for previous/existing GitHub issues
Description
Add Bicep Spec for resource modules: All Bicep resource modules MUST leverage the common type utility module for shared interfaces
Document exceptions if any.
This has to be a MUST for new modules, a SHOULD for existing modules until this gets integrated into the library.
The spec should include details on the lifecycle, e.g., modules should always use the latest version of the common type utility module 2 weeks after its release (lifecycle details still to be discussed)
Check for previous/existing GitHub issues
Description
Add Bicep Spec for resource modules: All Bicep resource modules MUST leverage the common type utility module for shared interfaces
Document exceptions if any.
This has to be a MUST for new modules, a SHOULD for existing modules until this gets integrated into the library.
The spec should include details on the lifecycle, e.g., modules should always use the latest version of the common type utility module 2 weeks after its release (lifecycle details still to be discussed)