RepoJournal
HashiCorp

@hashicorp

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

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

One email a day. Unsubscribe in one click.

Pick a date

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

The Wire · Showcase

TERRAFORM GOOGLE PROVIDERS SHIP MAJOR REFACTOR ACROSS DUAL TRACKS

By RepoJournal · Filed · About HashiCorp

modular-magician dependabot[bot]
2 people shipped this
modular-magician @modular-magician 10 cited dependabot[bot] @dependabot[bot] 2 cited

Both the stable and beta Terraform Google providers are mid-migration away from legacy client patterns, replacing BasePath usage and moving to direct HTTP transport across compute, SQL, and resource management services.

The Google provider team is executing a coordinated refactor across terraform-provider-google and terraform-provider-google-beta [ref:7,12], replacing hardcoded BasePath usage in universe tests, ACM, AD, AlloyDB, and Apigee with a more maintainable pattern. This foundational work is paired with client migrations that decouple SQL, BackupDR, Dataflow, and ResourceManager services from legacy abstractions [ref:9,14], with a notable subpackaging of ResourceManager to resolve circular dependencies with compute. The framework provider is being moved to use the registry directly [ref:8,13], reducing technical debt in the dual-provider model. On the feature side, both providers now support `gce_hd` in workstations_workstation_config [ref:10,15], and compute's ProjectMetadataItem resource has been migrated to direct HTTP transport rather than client libraries [ref:11,16]—a pattern that signals the team's broader push toward simpler, more direct API interactions. Meanwhile, Nomad's ecosystem is live with nightly snapshots of podman-driver, autoscaler, and pack [ref:1,5,6], with go-jose crypto library fixes landing in podman-driver [ref:2,3] to address JWE decryption panics.

One email a day. Unsubscribe in one click.

Action items

References

  1. [1] Replaced BasePath usage in universe tests, acm, ad, alloydb, and apigee ↗ hashicorp/terraform-provider-google-beta
  2. [2] Replaced BasePath usage in universe tests, acm, ad, alloydb, and apigee ↗ hashicorp/terraform-provider-google
  3. [3] Moved framework provider to using registry ↗ hashicorp/terraform-provider-google-beta
  4. [4] Moved framework provider to using registry ↗ hashicorp/terraform-provider-google
  5. [5] Moved clients for sql, backupdr, dataflow, resourcemanager, and resourcemanagerv3 ↗ hashicorp/terraform-provider-google-beta
  6. [6] Moved clients for sql, backupdr, dataflow, resourcemanager, and resourcemanagerv3 ↗ hashicorp/terraform-provider-google
  7. [7] Add support for gce_hd in workstations_workstation_config. ↗ hashicorp/terraform-provider-google-beta
  8. [8] Add support for gce_hd in workstations_workstation_config. ↗ hashicorp/terraform-provider-google
  9. [9] Migrate resource_compute_project_metadata_item to use transport_tpg.SendRequest ↗ hashicorp/terraform-provider-google-beta
  10. [10] Migrate resource_compute_project_metadata_item to use transport_tpg.SendRequest ↗ hashicorp/terraform-provider-google
  11. [11] nightly ↗ hashicorp/nomad-driver-podman
  12. [12] nightly ↗ hashicorp/nomad-autoscaler
  13. [13] nightly ↗ hashicorp/nomad-pack
  14. [14] build(deps): bump github.com/go-jose/go-jose/v4 from 4.1.3 to 4.1.4 ↗ hashicorp/nomad-driver-podman
  15. [15] build(deps): bump github.com/go-jose/go-jose/v3 from 3.0.4 to 3.0.5 ↗ hashicorp/nomad-driver-podman

Quick answers

What shipped in HashiCorp on May 2, 2026?
Both the stable and beta Terraform Google providers are mid-migration away from legacy client patterns, replacing BasePath usage and moving to direct HTTP transport across compute, SQL, and resource management services. In total, 15 commits, 18 pull requests, and 3 releases landed.
Who contributed to HashiCorp on May 2, 2026?
2 developers shipped this update, including modular-magician and dependabot[bot].
What were the notable HashiCorp updates?
Replaced BasePath usage in universe tests, acm, ad, alloydb, and apigee, Replaced BasePath usage in universe tests, acm, ad, alloydb, and apigee, and Moved framework provider to using registry.

More from @hashicorp

HashiCorp @hashicorp

TERRAFORM PROVIDERS EXPAND GOOGLE CLOUD COVERAGE AND IN-PLACE UPDATES

HashiCorp shipped in-place VCS connection updates for registry modules while Google provider gains traffic config for Vertex AI and promotes NCC gateway resources to GA.

hashimoon modular-magician
go 19 shipped 1-min read
HashiCorp @hashicorp

VAULT LDAP GETS ON-DEMAND PASSWORD ROTATION, PACKER CUTS v1.16.0

Terraform provider for Vault now supports rotate-on-read for LDAP secrets, letting teams rotate credentials at read time instead of waiting for scheduled intervals.

pajay-rao vivekpandeyHashi dependabot tanmay-hc
go 8 shipped 1-min read
HashiCorp @hashicorp

CONSUL FIXES FLOODED MEMBER REJOIN BUG AS VSO PATCHES GRPC FRAME FLOOD

Consul patches a critical WAN flood regression that was incorrectly treating failed members as alive during rejoin sequences.

sanikachavan5 dependabot
go 8 shipped 1-min read
HashiCorp @hashicorp

TERRAFORM AWS PROVIDER GAINS S3 TABLES AND OPENSEARCH FEDERATION SUPPORT

The AWS provider shipped three enhancement PRs overnight that expand infrastructure-as-code coverage for S3 Tables metadata properties and OpenSearch security configurations, while the docs team cleaned up deprecated tutorial collections and fixed formatting bugs across Vault and PKI documentation.

williamdalessandro pajay-rao JoshAtHC Robert Main +5
go 60 shipped 1-min read

Daily updates, in your inbox

Follow HashiCorp

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

or

One email a day. Unsubscribe in one click. Read a past issue →

Elsewhere on the wire

AI Agents AI Agents

CLAUDE OPUS 5 LANDS ACROSS THE STACK

The newest Anthropic model is now live in langchain, Cline, and llama-index, with native support for extended reasoning and 1M context windows.

github-actions[bot] hntrl dependabot ak684 +6
ai-agents 28 shipped 1-min read
Local LLMs Local LLMs

OLLAMA LANDS LAGUNA SUPPORT AND CRUSHES MEMORY LEAKS WHILE SGLANG HITS V0.5.16 WITH CONFIDENCE-DRIVEN SPECULATIVE DECODING

Ollama shipped three critical performance and reliability fixes for Metal residency and concurrent access patterns, while SGL-Lang released 0.5.16 with a new speculative algorithm hitting 383.7 tok/s on DeepSeek-V4.

dhiltgen ParthSareen Xuan-Son Nguyen Johannes Gäßler +11
llms 210 shipped 2-min read
CachyOS @CachyOS

HYPRLAND V0.56 FIXES LAND, PACKAGE ECOSYSTEM ROLLS FORWARD

Hyprland configuration updated for v0.56 compatibility across multiple desks, while the AUR-derived ecosystem locked in four automated package bumps.

cantosun99 Jinra Aarrayy Valeri +7
infra 85 shipped 1-min read
Elixir & Phoenix Elixir & Phoenix

LIVEVIEW ASYNC CLEANUP FIX SHIPS ALONGSIDE RANGE OPTIMIZATIONS

Phoenix LiveView closes a critical async task test failure while Elixir cuts unnecessary abs calls from Range operations.

Barna Kovacs Alexander Gubarev SteffenDE José Valim +1
elixir 19 shipped 1-min read
Want every project, not just this one?