modules▌

Certification requirements and best practices for Azure Terraform modules seeking AVM compliance. \n \n Enforces provider version constraints (azurerm >= 4.0, < 5.0; azapi >= 2.0, < 3.0) and prohibits git-based module references in favor of pinned Terraform registry sources \n Mandates lower snake_casing for all identifiers, precise variable types, discrete output attributes via anti-corruption layer pattern, and alphabetically ordered locals \n Requires feature toggle variables for ne

Framework extensions through published npm packages, local modules, and runtime/server integrations. \n \n Covers three module types: published npm packages (@nuxtjs/, nuxt-), local project modules in the modules/ directory, and inline hooks in nuxt.config.ts \n Provides defineNuxtModule patterns, Kit utilities, and hook system for extending components, composables, plugins, API routes, and middleware \n Includes E2E testing strategies, npm publishing workflows, and copy-paste CI/CD templates fo

Automated Azure Verified Module version updates for Bicep files with breaking change detection. \n \n Scans Bicep files to extract AVM module references, queries MCR for latest versions, and applies updates automatically \n Pauses for manual approval when breaking changes, security modifications, or parameter incompatibilities are detected \n Validates all changes with bicep lint and bicep build to ensure compliance before finalizing \n Outputs results in a structured table showing module names,