RepoJournal
HashiCorp

@hashicorp

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

Pick a date

The Wire · Showcase

TERRAFORM GOOGLE PROVIDERS SHIP MAJOR REFACTOR ACROSS DUAL TRACKS

By RepoJournal · Filed · About HashiCorp

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

FAQ

What changed 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.
What should HashiCorp teams do about it?
Review terraform-provider-google PRs for BasePath migration impact on custom configurations • Test workstations_workstation_config with gce_hd before deploying to prod • Pull latest nomad-driver-podman nightly to pick up go-jose security fixes
Which HashiCorp repositories shipped on May 2, 2026?
hashicorp/terraform-provider-google-beta, hashicorp/terraform-provider-google, 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.