What's Changed
Bug Fixes
- fix(examples): pass aliased azapi provider alongside azurerm by @arjenhuitema in #111
Other Changes
- feat(metadata): add approved module metadata by @jaredfholgate in #121
- chore: update AMBA library to 2026.10.0 by @arjenhuitema in #146
- fix: retire ModTM and update managed workflows by @jaredfholgate in #143
New Contributors
- @jaredfholgate made their first contribution in #121
Full Changelog: v0.4.0...v0.5.0
Breaking changes
- Upgrade Terraform to 1.11.0 or later, below 2.0, for the root and default example. The three ALZ examples require Terraform 1.12.0 or later. Refresh provider locks for AzAPI
~> 2.12and the managed identity dependency's AzureRM>= 4.60.0, < 5.0.0requirement. - ModTM is replaced with optional empty subscription-scope AzAPI deployments. The executing identity needs permission to manage
Microsoft.Resources/deploymentsat the telemetry subscription scope. Setenable_telemetry = falseto opt out. Remove obsoletemodtmprovider mappings from module calls, but retain any provider configuration still needed by old state until Terraform processes theremovedblocks withdestroy = false. - Resource Group advances from 0.4.0 to 0.5.0 and Managed Identity from 0.5.0 to 0.6.0. Resource Group moves
azapi_resource.thistoazapi_resource.this[0]; older AzureRM state can require provider migration or import. For older AzureRM-based role assignments, supply each existing assignment GUID in lowercase asrole_assignments[*].nameto preserve its identity. That input is now effective rather than ignored: remove an unintended previously supplied value, since a different GUID can force replacement or conflict. Existing 0.4.0-generated role-assignment UUID state is normally retained. Resource Group lock bodies now sendnotes = null; the effect on existing notes is unverified. - ALZ examples advance the module from 0.21.0 to 0.23.0, the ALZ provider from 0.21.x to 0.22.x, and the AMBA library from 2026.06.2 to 2026.10.0. Custom architecture examples change their management-group identifiers from the
contosoconvention toalz,platform,management, and related identifiers. Preserve your deployed architecture IDs when adapting these examples. - The default example switches to
Azure/avm-utl-naming/azure0.3.0 and itsnamesoutput. Its new random resources do not preserve the old naming seed: reusing an existing example state can replace the resource group and identity, potentially deleting the resource group. Preserve deployed names and follow the naming migration guidance; legacy mode retains the old named-output references rather than the newnamesmap. Multi-subscription module calls must map bothazurermandazapito the intended subscription.
AMBA's four scalar outputs are unchanged. Random remains a legitimate transitive dependency for role-assignment names; do not remove its provider configuration while state or dependencies still require it.
Back up state and inspect a representative upgrade plan for unexpected replacements or destruction before applying. Historical live-state upgrades were not tested.
The exact released tree passed two byte-unchanged Microsoft-signed Authoring preparations and hosted PR-check including policy. All five root/example provider closures exclude ModTM and validate at their declared Terraform floors. Managed unit and integration suites are absent; their hosted wrappers reported zero tests, not coverage. The legacy example-plan harness was not run. E2E was explicitly deferred.