Who contributed to HashiCorp on July 18, 2026?

3 developers shipped this update, including github-actions[bot], hc-github-team-nomad-ecosystem, and modular-magician.

What were the notable HashiCorp updates?

cloudrunv2: promote start_execution_token and run_execution_token to GA, Promoting QuotaAdjusterSettings resource to GA, and `container`: set default timeout for `google_container_node_pool` to 2 hours.

Jul 18, 2026

$ the-wire · showcase

TERRAFORM GOOGLE PROVIDER SHIPS GA PROMOTIONS FOR CLOUD RUN AND QUOTA MANAGEMENT

By RepoJournal · Filed 06:57 UTC on July 18, 2026 · About HashiCorp · Composed from the cited sources · methodology

3 people shipped this

modular-magician @modular-magician 3 cited

github-actions[bot] @github-actions[bot] 2 cited

hc-github-team-nomad-ecosystem @hc-github-team-nomad-ecosystem 1 cited

HashiCorp's Terraform Google provider graduated two major Cloud Run features and the QuotaAdjusterSettings resource to GA, signaling stability for production workloads.

In brief

Terraform Google provider: start_execution_token and run_execution_token for Cloud Run are now GA. you can authenticate workload invocations directly from your infra code instead of bolting it on later.
QuotaAdjusterSettings resource hit GA in the Google provider. rate limiting quotas just got a first-class citizen in Terraform. no more manual GCP console tweaks for quota adjustments.
google_container_node_pool now defaults to a 2 hour timeout instead of the old 4. if your GKE node pools have been mysteriously timing out, this might be the reset you needed.

The terraform-provider-google-beta landed three significant promotions overnight. Cloud Run's start_execution_token and run_execution_token fields move to GA [1] after extended beta testing, giving you native token handling for job execution without workarounds. QuotaAdjusterSettings joins GA [2], letting teams manage quota adjustments at production scale. On the infrastructure side, the provider now sets a 2-hour default timeout for google_container_node_pool operations [3], eliminating the silent failures teams have been debugging when cluster provisioning exceeded the old defaults. This is the stability push you've been waiting for if you're running multi-region GCP infrastructure through Terraform. Across the Nomad ecosystem, nightly snapshots hit for Autoscaler [4], Pack [5], and the Podman driver [6], tracking the latest development work if you need to test against unreleased features.

Action items

→ Plan terraform-provider-google-beta upgrade to capture GA promotions in your next release cycle hashicorp/terraform-provider-google-beta [plan]
→ Update any Cloud Run job configurations to use the new GA token fields instead of beta equivalents hashicorp/terraform-provider-google-beta [plan]
→ Verify container_node_pool timeout behavior in dev after upgrade to ensure 2-hour default fits your provisioning patterns hashicorp/terraform-provider-google-beta [monitor]

References

[1] cloudrunv2: promote start_execution_token and run_execution_token to GA ↗ hashicorp/terraform-provider-google-beta
[2] Promoting QuotaAdjusterSettings resource to GA ↗ hashicorp/terraform-provider-google-beta
[3] `container`: set default timeout for `google_container_node_pool` to 2 hours ↗ hashicorp/terraform-provider-google-beta
[4] nightly ↗ hashicorp/nomad-autoscaler
[5] nightly ↗ hashicorp/nomad-pack
[6] nightly ↗ hashicorp/nomad-driver-podman