Skip to content
EOL Watch
Search itemsOpen menu

avm-res-network-routetable breaking changes

An Azure Verified Module for Terraform, published as Azure/avm-res-network-routetable/azurerm in the Terraform Registry: the resource module for Route Table.

Azure

Latest v0.6.0, released · 2 releases that list breaking changes in the last 12 months

Pick your version

For example 0.1.0 or ~> 0.1. A typed value wins over the list.

Every release from v0.1.0 up to v0.6.0: 3 releases with breaking changes, 9 changes

Breaking changes

v0.6.0

Release notes for v0.6.0

  • Direct users of modules/route must now supply a non-null real Azure location even when enable_telemetry=false. Root callers already supply location; the root forwards it and enable_telemetry to each route child. No new required root input is added.
  • Default-enabled telemetry now creates empty Incremental subscription deployments for the root and every instantiated non-legacy route child. Subscription deployment-management permissions are required; resource-group-only routing permissions may be insufficient. Owner is not specifically required. Configure the intended AzAPI subscription or explicitly disable telemetry. Expect additional deployment-history records per child and plan-timestamp updates. Existing routes_legacy_mode selection is unchanged.
  • AzAPI now requires~>2.12 instead of~>2.4 in root and direct route child. Terraform>=1.9,<2.0 and AzureRM~>4.0 remain unchanged. Refresh provider locks as appropriate.
  • ModTM and telemetry-only root Random requirements are removed. Non-destructive removed blocks request forgetting old root telemetry resources. Workload addresses and map keys are preserved, but an actual historical-state upgrade has not been exercised; back up state and inspect the plan.
  • Route-table/route request bodies, route outputs, subnet associations, locks and role assignments retain their existing contract. Examples use exact certified Naming0.2.0 and legacy Regions0.8.2.

v0.5.0

Release notes for v0.5.0

  • A submodule has been introduced for routes.
  • The Terraform moved block lacks the capability to perform this move dynamically. As such we have retained the legacy mode for the next couple of releases. This can be enabled by setting the routes_legacy_mode variable to true.
  • In order to migrate to the submodule, you'll need to construct moved blocks for each of your routes like this.

v0.4.0

Release notes for v0.4.0

  • Breaking changes in underlying provider versions supported.

Related items

The timeline items about releases of avm-res-network-routetable, by release date.