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-10-24
stories 43

© 2026 RepoJournal Home Showcase How it works Privacy

$ the-wire · showcase

Terraform policy for Stacks goes GA, GKE clusters go 0-node

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

terraform-provider-tfe completes Terraform policy (tfpolicy) support and ships Stack scoping resources, while terraform-provider-google-beta accepts 0-node GKE clusters and deprecates remove_default_node_pool.

feat: r/tfe_policy_set Terraform policy (tfpolicy) GA support and go-tfe v2.13.0 upgrade hashicorp/terraform-provider-tfe

by shrishyamb

tfpolicy policy sets are now GA: tfe_policy_set rejects agent_enabled and overridable at plan time when kind = "tfpolicy", even when set to false, deferring the check to apply if the value is unknown. go-tfe/v2 moves to v2.13.0 and team member helpers are adjusted for a renamed included envelope type.

feat: New r/tfe_stack_policy_set and r/tfe_stack_policy_set_exclusion for Terraform Policy (tfpolicy) on Stacks hashicorp/terraform-provider-tfe

by shrishyamb

Two new resources scope policy sets to Stacks: tfe_stack_policy_set for inclusion and tfe_stack_policy_set_exclusion for exclusion. Resource IDs take the form <STACK_ID>/<POLICY_SET_ID>, import uses the same format, and every attribute forces replacement, so changing one recreates the association.

container: support 0-node google_container_cluster creation and deprecate remove_default_node_pool hashicorp/terraform-provider-google-beta

by modular-magician

google_container_cluster now accepts native 0-node creation by omitting initial_node_count and node_config, or setting initial_node_count = 0, without remove_default_node_pool, on GKE 1.36.4-gke.1469000 and later. The provider also ignores HTTP 404 when remove_default_node_pool = true is set at creation and default-pool was never created.

sql: redact sensitive fields in BGD switchover validation hashicorp/terraform-provider-google-beta

by modular-magician

The SQL Blue-Green Deployment switchover check compared configured fields against the green replica while root_password held its prior value, because the Cloud SQL Admin API never returns it, and reported a mismatch containing plaintext password values. The change redacts sensitive fields in that validation path.

compute: remove DEPRECATED_LegacyApiaryClient (#19590) (#13534) hashicorp/terraform-provider-google-beta

by The Magician

Also in google-beta: the compute package drops DEPRECATED_LegacyApiaryClient, and vagrant-registry-export gains a release workflow plus a CLI command that reports the running tool's version.

Quick answers

What shipped in HashiCorp on October 24, 2026?
terraform-provider-tfe completes Terraform policy (tfpolicy) support and ships Stack scoping resources, while terraform-provider-google-beta accepts 0-node GKE clusters and deprecates remove_default_node_pool. In total, 19 commits, 20 pull requests, and 4 releases landed.
Who contributed to HashiCorp on October 24, 2026?
3 developers shipped this update, including taru-garg-2000, shrishyamb, and The Magician.
What were the notable HashiCorp updates?
feat: r/tfe_policy_set Terraform policy (tfpolicy) GA support and go-tfe v2.13.0 upgrade, feat: New r/tfe_stack_policy_set and r/tfe_stack_policy_set_exclusion for Terraform Policy (tfpolicy) on Stacks, and container: support 0-node google_container_cluster creation and deprecate remove_default_node_pool.