Skip to content
EOL Watch
Search itemsOpen menu

AzureBreaking change

avm-res-storage-storageaccount 0.11.0: breaking changes

Release date of version 0.11.0 of the Azure Verified Module avm-res-storage-storageaccount: 4 Nov 2026. Breaking changes listed in the release notes: 5.

Breaking since , 4 Nov 2026

What breaks

Breaking changes listed in the release notes:

  • The tracing_tags_header input was removed from the blob_service, container, data_lake_filesystem, diagnostic_setting, file_service, local_user, management_policy, private_endpoint, queue, queue_service, role_assignments, share, table, and table_service child modules. The static_website child retains this input.
  • Direct callers must now supply location to container, diagnostic_setting, local_user, queue, role_assignments, share, and table. Direct callers of blob_service, data_lake_filesystem, file_service, management_policy, queue_service, static_website, and table_service must supply location when telemetry is enabled (the default).
  • The minimum Azure AzAPI provider version increases to 2.12 for the root and all child modules.
  • Enabled telemetry now creates subscription-scope ARM deployments. The caller needs subscription-scope deployment read, write, and delete permissions. The root and instrumented children honor enable_telemetry = false; root input and output contracts are unchanged.
  • The root and its updated Interfaces dependencies retire legacy ModTM and random telemetry state with destroy = false. Upgrading existing state may still require the legacy providers during initialization. Review the plan before applying.

Who is affected

Affected versions

  • 0.11.0

What to do

  1. Breaking changes listed in the release notes for 0.11.0: 5. HashiCorp recommends explicitly constraining the acceptable version numbers to avoid unexpected or unwanted changes.
  2. Check the version argument of the module block that installs avm-res-storage-storageaccount from the Terraform Registry. Terraform uses the newest installed version that meets the constraint. When no acceptable version is installed, it downloads the newest version that meets the constraint, so a constraint that allows 0.11.0 can bring in this release. A module block with no version argument defaults to the latest version available from the source.
  3. The AVM versioning specification requires that, until a module's first major version 1.0.0 is released, the minor version is bumped for breaking changes and the major version is not bumped.
  4. To stay on an earlier version for now, require a specific version. HashiCorp recommends this for third-party modules so that updates only happen when convenient to you.
  5. To adopt 0.11.0, set the version argument to it, then run terraform init so that Terraform can update the local code.

Replacement

Not stated by vendor.

Sources

Last checked against the first source in this list on .

avm-res-storage-storageaccountbreaking changes by version

Found an error? Report it

The text on this page is drafted with AI assistance from the vendor's text, checked against the official source and approved by a person before it is published. How items are written

Last checked · Added · Changelog for this item