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

AZURE PROVIDER SHIPS v4.72.0 WITH NEW SUBNET LIST RESOURCE

By RepoJournal · Filed · About HashiCorp

Terraform azurerm reaches v4.72.0 with a new list resource for subnets and Go 1.25.10 bump, while vault-provider hardens its AWS/GCP integration layer across the stack.

The terraform-provider-azurerm v4.72.0 release [1] introduces a new `azurerm_subnet` list resource and upgrades Go to 1.25.10 [2], shipping alongside enhancements to LogAnalytics API versioning and improved HTTP error logging [3]. Over on the vault-provider side, the team is pushing write-only parameter support to `vault_raft_snapshot_agent_config` [4], starting with AWS S3 and staging GCP/Azure for follow-ups. The underlying dependency story matters here: vault-provider bumped AWS SDK v2, Google Cloud IAM, and STS libraries [5], keeping pace with the Azure upgrades. Consul-k8s meanwhile shipped a critical spdystream security patch (GHSA-pc3f-x583-g7j2) [6] and is hardening AKS cluster testing with EDR agent instrumentation [7]. Boundary's E2E test scenarios are getting refreshed with RDP variable handling [8] to support enterprise testing workflows.

Action items

References

  1. [1] v4.72.0 ↗ hashicorp/terraform-provider-azurerm
  2. [2] dependencies: update `go` to `1.25.10` ↗ hashicorp/terraform-provider-azurerm
  3. [3] `common` - Add additional logs when HTTP response was failed to be dumped ↗ hashicorp/terraform-provider-azurerm
  4. [4] Add write-only parameters to `vault_raft_snapshot_agent_config` ↗ hashicorp/terraform-provider-vault
  5. [5] build(deps): bump the gomod-backward-compatible group across 1 directory with 10 updates ↗ hashicorp/terraform-provider-vault
  6. [6] Post release (#5289) hashicorp/consul-k8s
  7. [7] adding EDR for aks tests ↗ hashicorp/consul-k8s
  8. [8] chore(e2e): update rdp scenario ↗ hashicorp/boundary

FAQ

What changed in HashiCorp on May 8, 2026?
Terraform azurerm reaches v4.72.0 with a new list resource for subnets and Go 1.25.10 bump, while vault-provider hardens its AWS/GCP integration layer across the stack.
What should HashiCorp teams do about it?
Update terraform-provider-azurerm to v4.72.0 and verify subnet list resource in your infrastructure modules • Patch consul-k8s to pick up spdystream CVE fix (GHSA-pc3f-x583-g7j2) in AKS deployments • Stage vault-provider write-only parameter support for S3 snapshots in non-production before wider rollout
Which HashiCorp repositories shipped on May 8, 2026?
hashicorp/terraform-provider-azurerm, hashicorp/terraform-provider-vault, hashicorp/consul-k8s, hashicorp/boundary

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.