avm-res-network-virtualnetwork breaking changes
An Azure Verified Module for Terraform, published as Azure/avm-res-network-virtualnetwork/azurerm in the Terraform Registry: the resource module for Virtual Network.
Azure
Latest v0.23.0, released · 3 releases that list breaking changes in the last 12 months
Pick your version
Every release from v0.11.0 up to v0.23.0: 6 releases with breaking changes, 15 changes
Breaking changes
v0.23.0
- Standalone modules/subnet and modules/peering now enable telemetry by default and require a non-null location when telemetry is enabled. Existing direct callers must supply location or explicitly set enable_telemetry = false. The root module passes its existing location to these children.
- Enabled telemetry now creates Azure subscription-scope deployments through AzAPI, including for the root module and enabled children. Identities must have the necessary subscription-scope deployment permissions; alternatively disable telemetry. Terraform state forgets legacy ModTM telemetry and telemetry UUID objects without destroying them and tracks the new telemetry deployment resources.
v0.20.0
- Breaking change: subnet service endpoints. service_endpoints_with_location is removed and now raises a validation error instead of being silently discarded. Configure subnet service endpoints with names only.
v0.19.0
- Interfaces converted from azurerm to azapi (#52), the resource lock, role assignment, and diagnostic settings interfaces are now implemented with azapi_resource via the Azure/avm-utl-interfaces utility module. The azurerm provider dependency has been removed from the module entirely. (#108) Source for this change in v0.19.0
- Input/output compatibility: the lock, role_assignments, and diagnostic_settings variable schemas are unchanged, no inputs or outputs were added, removed, or renamed. Existing configurations do not need to change.
- Locks & diagnostic settings migrate in place via moved blocks, no recreation.
- Role assignments are recreated once. Their underlying resource name changes from the azurerm-generated GUID to the utility module's generated name, so Terraform will destroy and re-create each role assignment on the first apply after upgrading. This is a metadata-only churn, the effective access (principal, role, scope) is identical before and after. Plan carefully if you have policies that react to role-assignment lifecycle events.
v0.15.0
- The deprecated service_endpoints input for subnets has been removed.
- We have had to separate the implementation of subnets using IPAM. If you have deployed a subnet with IPAM since that change went out, you'll need to add a moved block to your code into order to migrate the state. E.g.
- If you are not using IPAM your state will automatically be migrated.
v0.12.0
- This PR removes some of the retry options, but very unlikely they are being used so not expecting much impact.
v0.11.0
- This release includes a significant breaking change to the module interface.
- We have removed the resource_group_name and subscription_id inputs. The resource group ID must now be explicitly provided via the parent_id input.
- This change was necessary to align to forthcoming AVM v1 specs as well as fix an underlying idempotency issue with the existing implementation.
- We try very hard not to make breaking changes to module interfaces like this and understand the impact it has to consumers of our modules. We do not anticipate any further breaking changes to the interface of this module prior to v1.
Related items
The timeline items about releases of avm-res-network-virtualnetwork, by release date.