github Azure/terraform-azurerm-avm-res-web-site v0.25.0

one hour ago

Full Changelog: v0.24.1...v0.25.0

Breaking changes and upgrade guidance

Recommended version: v0.25.0 (breaking minor), not v0.24.2. This review covers the complete six-commit, 142-file delta from published v0.24.1 (56c704e9f44002a46a71226d3c19f3915e1865c0) to qualified main 6365a9585a39fd12a6c3b0b02f09b010fe033300, tree 823e8188c3b3552c542a7646c4da662de28c785d. All six commits have maintenance-style titles; those titles and the generated notes alone do not describe the consumer impact.

Direct child-module callers: location inputs change

All 14 deployable child modules now expose non-nullable enable_telemetry, defaulting to true. The pure site_config_helpers module is unchanged.

Direct child modules Upgrade requirement
config_azurestorageaccounts, extensions_zipdeploy New required, non-null location, even when enable_telemetry = false.
config_appsettings, config_authsettings, config_authsettingsv2, config_backup, config_connectionstrings, config_logs, config_metadata, config_slotconfignames, hostname_binding, publishing_credential_policy New location defaults to null, but validation requires a non-null value while telemetry is enabled. Supply a location, or explicitly disable telemetry for that direct child call.
certificate, slot Location was already required. These gain the new default-on telemetry input/resources, not a new location requirement.

The root and slot forward their location and telemetry settings to their local children. Root telemetry opt-out now also reaches slots and their interfaces. The root input/output schema is unchanged; ordinary root-module callers do not gain a new location argument.

Default-on subscription telemetry: permissions and plan/state effects

  • ModTM is replaced by an empty, subscription-scoped Microsoft.Resources/deployments@2025-04-01 AzAPI resource and a provider-free terraform_data instance identifier. This applies to the root, instantiated deployable children, and the upgraded interfaces dependency.
  • With telemetry enabled, the deployment identity needs Microsoft.Resources/deployments/read, Microsoft.Resources/deployments/write, and Microsoft.Resources/deployments/delete at subscription scope. Resource-group-only permissions may no longer suffice. A telemetry deployment failure can fail the apply. This preparation does not grant permissions or perform Azure operations.
  • Root enable_telemetry remains true by default; the new child input also defaults to true. A root opt-out propagates through its children; independently called child modules have their own setting. Opt-out does not remove the two unconditional location requirements above.
  • Deployment names use module metadata, version/source-kind tokens, and a stable instance hash instead of the former ModTM payload. The deployment template is empty, but plantimestamp() intentionally changes its output on each normal plan/apply, so otherwise unchanged deployments can still show telemetry updates.
  • Existing root and interfaces ModTM telemetry and telemetry-only Random UUID addresses are covered by removed blocks with destroy = false. They are forgotten without destroying managed Azure workload resources. Existing state can still require the old provider during final initialization/state processing. Retain the normal state backup and provider availability; no manual state deletion or provider replacement is prescribed.
  • New telemetry adds ARM deployment records and Terraform state entries. Primary site/slot addresses, root outputs, and the existing connection-string state-move contract are not migrated by this delta. An Azure-backed upgrade/no-replacement plan has not been executed.

Provider and published dependency changes

  • Root requirements remove direct azure/modtm ~> 0.3 and direct hashicorp/random >= 3.5.0, < 4.0.0. Root Terraform >= 1.9, < 2.0, AzAPI ~> 2.12, and Time >= 0.9.0, < 1.0.0 constraints are unchanged.
  • Random is not universally removed: Azure/avm-utl-interfaces/azure still requires it for non-telemetry identifiers, and examples also use Random. No ModTM dependency remains in any of the 38 initialized module/example graphs.
  • Root and slot upgrade Azure/avm-utl-interfaces/azure 0.7.0 to 0.9.0, passing the newly required location and, for slots, the telemetry setting. The upstream runtime delta replaces telemetry, adds location, and raises its AzAPI constraint from ~> 2.4 to ~> 2.12; its interface computation/output implementations are unchanged. The root already required AzAPI ~> 2.12.
  • examples/interfaces upgrades Azure/avm-utl-regions/azurerm 0.12.0 to 0.13.0, passing its newly required location. That dependency replaces telemetry, removes ModTM and telemetry-only Random requirements, and raises AzAPI ~> 2.4 to ~> 2.12. Region filtering/output logic and cached regional data are unchanged across those tags.
  • All dependency versions above and below are already published; no unreleased Tools/ALZ or other runtime dependency is needed for this candidate.

Existing example deployments: naming replacement risk

All 22 examples switch from Azure/naming/azurerm (0.4.3, or 0.4.4 for zip_deploy_file) to Azure/avm-utl-naming/azure 0.2.0. This changes the naming utility, not the root Web Site implementation from AzureRM to AzAPI.

The replacement naming utility requires Terraform >= 1.9, < 2.0 and Random >= 3.3.2, < 4.0, compatible with the existing example graphs.

The new utility defaults to its modern renderer (legacy_mode = false). Its modern Random resource addresses differ from the old naming module's addresses. The compatibility moved blocks target legacy instances, which have zero count in modern mode; they do not guarantee preservation of the old example naming seed under the examples' new default configuration. Reusing an existing example state can regenerate unique names and propose replacement of resource groups and workloads, potentially with destructive consequences. Modern catalog/rendering rules can also differ.

The utility offers legacy_mode = true, but these examples do not select it. Review names and state explicitly before adapting an existing deployment; do not treat these examples as an automatic state-safe migration. This example-only dependency change does not rename resources for ordinary root-module callers that retain their existing name inputs.

examples/interfaces and examples/submodules additionally expose non-null location inputs defaulting to eastus and forward them for utility/direct-child telemetry. Their existing primary resource-group region selection remains separate and can differ from this telemetry location. The sensitive-values example's variable-file change is formatting only.

Other intervening changes and preserved behavior

  • Generated root, child, and example READMEs describe the changed requirements, resources, dependencies, and inputs.
  • Twenty-nine changed unit-test files and seven fixture/provider-source files adapt mocks, explicit provider bindings, and location inputs. Existing authored behavioral/state assertions remain; the qualified unit suite still executes 30 files. No telemetry-only test suite was added.
  • Managed-files baseline advances 1.1.4 to 1.2.1. Obsolete failing avm/avm.bat launcher stubs are removed; contributor tooling uses installed PowerShell Avm.Authoring.
  • PR checks remove the local fork-warning job and fork-only exclusion on the reusable managed workflow. Fork PRs can now enter that workflow, subject to its own controls. Existing contents: read, id-token: write, and inherited-secrets configuration are otherwise unchanged.
  • Root variables.tf, outputs.tf, main.tf, locals.tf, and moved.tf are unchanged. Parent/slot workload changes outside telemetry/interfaces are parameter forwarding only. Existing private-endpoint, connection-string, and isolated-.NET fixes already present in v0.24.1 are not newly introduced here.

Qualification and release boundary

The exact tree above retains two official preparation passes (7/7 each, second unchanged), native init/validate/providers for 38/38 roots, 155/155 unit runs across 30 files, documentation checks for 38 roots, and a clean official full gate (10/10, including 2,730 policy evaluations, zero issues). Authoring 1.1.1 and Terraform 1.17.2 were used. Managed-files 1.4.0 was available but not adopted; its drift warning did not fail qualification.

These are preserved local receipts, not a claim of a hosted managed qualification or Azure-backed upgrade. Integration reports skipped because no integration fixtures exist. E2E and deployed-state migration checks remain deferred; no workflow/environment approval, deployment, grant, release, or tag is performed by this preparation. Gates were not rerun because the qualified tree is unchanged. Publication remains the coordinator's decision after exact-head/version review.

Don't miss a new terraform-azurerm-avm-res-web-site release

NewReleases is sending notifications on new releases.