github Azure/terraform-azurerm-avm-res-web-serverfarm v2.1.0

29 minutes ago

Breaking changes and upgrade guidance

  • Azure/azapi now requires >=2.12.0,<3.0.0. Terraform remains >=1.9,<2.0. Random remains a transitive dependency; fresh installations no longer need ModTM.
  • Default-enabled telemetry creates two empty subscription-scoped Azure deployments, at the root and in Interfaces. The deployment identity needs Microsoft.Resources/deployments read/write/delete permissions in the active AzAPI provider subscription; resource-group-only permissions may be insufficient. Rejected enabled telemetry fails apply. Set enable_telemetry=false to disable both deployments. Telemetry deliberately writes on each normal apply, even when infrastructure is otherwise unchanged.
  • For P* Premium plans with automatic scaling enabled, maximum_elastic_worker_count now controls maximum burst when supplied, rather than being ignored. It must not be below worker_count when both are non-null. Omission retains worker_count-based Premium behavior. The input default changes from 3 to null; EP/WS plans still default effectively to 3, and an explicit null now also resolves to 3 rather than omitting the API property.
  • All six examples switch to Azure/avm-utl-naming/azure 0.3.0 in modern naming mode. Existing example state can receive new random uniqueness values and different name prefixes, potentially replacing resource groups, plans, identities and other named resources. This does not change ordinary root callers' explicitly supplied name or parent_id.
  • The managed_instance example now requires AzureRM 4.x and registers five resource-provider namespaces; registration needs subscription register/action rights if they are not already registered. windows_container now locates its resource group in the selected region and is excluded from automatic E2E discovery because of test-subscription quota.

State and compatibility

The primary service-plan, lock, role-assignment and diagnostic-setting addresses remain unchanged. The AzureRM-to-AzAPI moved blocks already present in v2.0.8 remain in place; this release does not introduce another primary-resource migration.

Root and Interfaces removed blocks forget legacy telemetry state with destroy=false. Old state may need one final initialization with the legacy providers available before applying those blocks; this is not a permanent ModTM requirement. No imperative state move is newly required for the inspected v2.0.8 root upgrade. Do not blindly remove state: review a normal refreshing plan, including example naming, lock-note and scaling changes, before applying.

Qualification and limitations

Official Avm.Authoring 1.1.1 and Terraform 1.17.2: two unchanged preparation passes, all seven native root/example provider closures ModTM-free, all 11 existing unit runs passed, and the complete local PR gate passed including policy.

The integration suite is absent: skipped, zero runs, not passed coverage. No full exact-tree hosted PR/unit/integration evidence exists for the automated merge; a same-tree CLA check is not substituted for validation. E2E, minimum-version execution and existing-state upgrade execution were not performed. Live upgrade and example replacement behavior remain unverified.

What's Changed

Other Changes

New Contributors

Full Changelog: v2.0.8...v2.1.0

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

NewReleases is sending notifications on new releases.