RepoJournal
HashiCorp @hashicorp
176 wires and counting

$ follow HashiCorp

Keep up with HashiCorp in about 3 minutes: what actually shipped — the commits, pull requests, releases, and security advisories that matter.

or

fair warning: these emails are deeply technical. diffs, version numbers, CVEs, benchmark deltas. if that's not your idea of a good read, this isn't your newsletter.

Folds into your digest — weekly by default, monthly if you prefer. Unsubscribe in one click.

$ status

wire 2026-05-28
stories 5
GitHub RSS Archive Reviews

© 2026 RepoJournal Home Showcase How it works Privacy

$ the-wire · showcase

TERRAFORM AZURERM 5.0 BREAKS ADDRESS_SPACE - PLAN YOUR MIGRATION NOW

By RepoJournal · Filed · About HashiCorp · Composed from the cited sources · methodology

sreallymatt
1 person shipped this
sreallymatt @sreallymatt 1 cited

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

$ ls hashicorp/reviews/ # the step-back reads

the week in review Consul provider patches two Go CVEs, adds 2.23.0 upgrade gate the month in review Consul patches four CVEs as Go bumps sweep repos
Full archive → Weekly reviews →

Quick answers

What shipped 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. In total, 1 commits, 1 pull requests, and 3 releases landed.
Who contributed to HashiCorp on May 28, 2026?
1 developer shipped this update, including sreallymatt.
What were the notable HashiCorp updates?
`azurerm_local_network_gateway` - change type of `address_space` to Set in 5.0, `azurerm_local_network_gateway` - change type of `address_space` to Set in 5.0 (#32460), and nightly.
♥

$ log @hashicorp --recent

A copyright sweep is the whole day 2 shipped HashiCorp: no material update 2 shipped Application Design Center lands, workload identity pools grow two fields 46 shipped Consul CI breaks on jq 1.8 as Ubuntu 26.04 runners arrive 31 shipped

$ log --all # elsewhere on the wire

Agent Security Quiet day in agent security as guard coverage reaches four clients Alignment & Post-training verl defaults Ascend RL mode, open-instruct unblocks SFT packing

$ ls showcases/

Safety Evals AI Red Teaming Agent Security Interpretability Alignment & Post-training

$ init your-desk

RepoJournal can write one of these for any repo you care about. Sign in with GitHub, pick your repos and sources, and your desk gets a wire like this one every morning.