RepoJournal
HashiCorp

@hashicorp

Terraform, Vault, Consul — infra-as-code for ops teams

Pick a date

  1. Sun 3 may
  2. Tue 5 may
  3. Wed 6 may
  4. Thu 7 may
  5. Fri 8 may
  6. Sat 9 may
  7. Sun 10 may
  8. Mon 11 may
  9. Tue 12 may
  10. Wed 13 may
  11. Thu 14 may
  12. Fri 15 may
  13. Sat 16 may
  14. Sun 17 may
  15. Tue 19 may
  16. Wed 20 may
  17. Thu 21 may
  18. Sat 23 may
  19. Sun 24 may
  20. Mon 25 may
  21. Tue 26 may
  22. Wed 27 may
  23. Thu 28 may
  24. Fri 29 may
  25. Sat 30 may
  26. Sun 31 may
  27. Mon 1 jun
  28. Mon 8 jun
  29. Tue 9 jun
  30. Today 10 jun

The Wire · Showcase

TERRAFORM AZURERM 5.0 BREAKS ADDRESS_SPACE - PLAN YOUR MIGRATION NOW

By RepoJournal · Filed · About HashiCorp

Terraform's Azure provider is shipping a breaking change in 5.0 that converts address_space from a List to a Set, forcing configuration rewrites for anyone managing local network gateways.

The terraform-provider-azurerm team merged a structural change [1] [2] that reshapes how address_space attributes are handled in azurerm_local_network_gateway resources. This isn't a bug fix or feature add. It's a deliberate breaking change that will require you to rewrite Terraform configs before upgrading to 5.0. The shift from List to Set changes ordering semantics and will trigger plan diffs on otherwise identical configurations. Across the Nomad ecosystem, nightly builds are rolling for the Podman driver [3], Nomad Autoscaler [4], and Nomad Pack [5], giving early testers a window to catch issues before stable releases. If you're running Azure infrastructure through Terraform, this is the upgrade you need to plan for now, not discover in production.

Action items

References

  1. [1] `azurerm_local_network_gateway` - change type of `address_space` to Set in 5.0 ↗ hashicorp/terraform-provider-azurerm
  2. [2] `azurerm_local_network_gateway` - change type of `address_space` to Set in 5.0 (#32460) hashicorp/terraform-provider-azurerm
  3. [3] nightly ↗ hashicorp/nomad-driver-podman
  4. [4] nightly ↗ hashicorp/nomad-autoscaler
  5. [5] nightly ↗ hashicorp/nomad-pack

FAQ

What changed in HashiCorp on May 28, 2026?
Terraform's Azure provider is shipping a breaking change in 5.0 that converts address_space from a List to a Set, forcing configuration rewrites for anyone managing local network gateways.
What should HashiCorp teams do about it?
Audit terraform-provider-azurerm configs for azurerm_local_network_gateway resources with address_space blocks • Test Nomad Podman driver, Autoscaler, and Pack against nightly builds in non-production before stable release • Schedule Azure provider 5.0 upgrade for next major Terraform deployment cycle
Which HashiCorp repositories shipped on May 28, 2026?
hashicorp/terraform-provider-azurerm, hashicorp/nomad-driver-podman, hashicorp/nomad-autoscaler, hashicorp/nomad-pack

Related across the cluster

For your repos

The showcase is a teaser.
Your wire is the product.

Same engine. Different stack. Below: what changes when the wire is yours.

Showcase wire

  • •14 famous open source orgs
  • •One wire per day
  • •Public, generic
  • •Read on the web, when you remember

Your wire

  • →Up to 1,500 of your repos - orgs, deps, vendors
  • →Morning and evening briefs
  • →Action items routed to your team
  • →Slack delivery, email, breaking-news CVE alerts

Want a hands-on demo first? Ask a current user for an invite link.