{
  "slug": "azure-avm-network-bastionhost-0-10-0-breaking-change",
  "title": "avm-res-network-bastionhost 0.10.0: breaking changes",
  "summary": "Release date of version 0.10.0 of the Azure Verified Module avm-res-network-bastionhost: 17 Nov 2026. Breaking changes listed in the release notes: 4.",
  "cloud": "azure",
  "service": "Azure Verified Modules",
  "service_slug": "avm",
  "category": "iac_module",
  "type": "breaking_change",
  "announced_date": "2026-11-17",
  "effective_date": "2026-11-17",
  "effective_precision": "day",
  "impact": "Breaking changes listed in the release notes:\n\n- AzAPI now requires ~> 2.12 (previously ~> 2.4). The root Terraform constraint remains >= 1.9, < 2.0; qualification used Terraform 1.17.2.\n- Enabled telemetry now creates empty subscription-scoped ARM deployments. The executing identity needs the corresponding deployment read/write/delete permissions at subscription scope. enable_telemetry = false continues to disable telemetry.\n- The Public IP child dependency moves from 0.2.0 in the previous release to 0.3.0 and migrates its AzureRM resources to AzAPI using upstream moved blocks. Review an existing-state upgrade with a normal refreshing plan; do not use -refresh=false. The root public inputs/outputs and primary Bastion resource addresses are unchanged; those Bastion resources were already AzAPI in v0.9.0.\n- Examples now use Naming 0.3.0 and VNet 0.23.0; Developer uses Regions 0.13.2. Developer's new location input controls only Regions-helper telemetry placement, not the randomly selected resource-group region.",
  "migration_path": "1. Breaking changes listed in the [release notes](https://github.com/Azure/terraform-azurerm-avm-res-network-bastionhost/releases/tag/v0.10.0) for 0.10.0: 4. HashiCorp recommends explicitly constraining the acceptable version numbers to avoid unexpected or unwanted changes.\n2. Check the `version` argument of the module block that installs avm-res-network-bastionhost from the [Terraform Registry](https://registry.terraform.io/modules/Azure/avm-res-network-bastionhost). 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.10.0 can bring in this release. A module block with no `version` argument defaults to the latest version available from the source.\n3. 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.\n4. 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.\n5. To adopt 0.10.0, set the `version` argument to it, then run `terraform init` so that Terraform can update the local code.",
  "replacement": null,
  "affected_versions": [
    "0.10.0"
  ],
  "source_url": "https://github.com/Azure/terraform-azurerm-avm-res-network-bastionhost/releases/tag/v0.10.0",
  "extra_source_urls": [
    "https://registry.terraform.io/modules/Azure/avm-res-network-bastionhost"
  ],
  "vendor_ref": "v0.10.0",
  "last_checked_at": "2026-11-20T03:24:26.335Z",
  "created_at": "2026-11-19T05:00:11.922Z",
  "updated_at": "2026-11-19T05:00:11.922Z",
  "url": "https://eolwatch.dev/items/azure-avm-network-bastionhost-0-10-0-breaking-change",
  "short_url": "https://eolwatch.dev/i/lj",
  "markdown_url": "https://eolwatch.dev/items/azure-avm-network-bastionhost-0-10-0-breaking-change.md",
  "json_url": "https://eolwatch.dev/items/azure-avm-network-bastionhost-0-10-0-breaking-change.json",
  "estate_check": null,
  "source_note": null
}
