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-02
stories 36
GitHub RSS Archive Reviews

© 2026 RepoJournal Home Showcase How it works Privacy

$ the-wire · showcase

TERRAFORM GOOGLE PROVIDERS SHIP MAJOR REFACTOR ACROSS DUAL TRACKS

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

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.

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

$ 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 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.
♥

$ 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.