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-11-07
stories 46

© 2026 RepoJournal Home Showcase How it works Privacy

$ the-wire · showcase

Application Design Center lands, workload identity pools grow two fields

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

Both Google Terraform providers mirrored the same six changes today, shipping the first `google_design_center_space` resource alongside new workload identity pool provider fields and a revert that walks back `identity_type`.

designcenter: add google_design_center_space resource hashicorp/terraform-provider-google

by modular-magician

The first Application Design Center resource, `google_design_center_space`, arrives with shared child-resource bootstrap helpers in place for nine companion split PRs, so the follow-on resources should merge without conflicts. The same change lands in `-beta`.

iambeta: add discovery_uri and actor_providers fields hashicorp/terraform-provider-google

by modular-magician

`google_iam_workload_identity_pool_provider` gains `actor_providers` and `oidc.discovery_uri`, exposed on the data source as well. The samples now reference `.id` rather than `.name` so `{project}` matches the parent resource path IAM validation requires, which matters if you copy those samples into your own configs.

agenticapplications: add mcp_data_sources.request_headers hashicorp/terraform-provider-google

by modular-magician

`google_agentic_applications_analyst_agent_persona` adds `mcp_data_sources.request_headers` with `header_name`, `value`, and `dynamic_value`. The reworked sample drops the `api_key_name` and `api_key_header` configuration that was set without `api_key`; anyone carrying that pattern has an invalid config to clean up.

identityplatform: add response_type to google_identity_platform_tenant_oauth_idp_config hashicorp/terraform-provider-google

by modular-magician

`google_identity_platform_tenant_oauth_idp_config` gains `response_type`, mirroring the field already on `google_identity_platform_oauth_idp_config`. It is marked `default_from_api` because the API returns `responseType: {idToken: true}` on create when the field is unset, so omitting it will not show drift.

Revert "compute: add identity_type to workload_identity_config" hashicorp/terraform-provider-google-beta

by modular-magician

The `identity_type` addition to `workload_identity_config` is reverted before it shipped in any release, while the `google.golang.org/api` dependency bump from the original change stays in `mmv1/third_party/terraform/go.mod`. The rest of the day is smaller: an `ENABLED_FOR_USERS_GROUPS` value for `scim_usage` on `google_iam_workforce_pool_provider`.

Quick answers

What shipped in HashiCorp on November 7, 2026?
Both Google Terraform providers mirrored the same six changes today, shipping the first `google_design_center_space` resource alongside new workload identity pool provider fields and a revert that walks back `identity_type`. In total, 22 commits, 22 pull requests, and 2 releases landed.
Who contributed to HashiCorp on November 7, 2026?
1 developer shipped this update, including modular-magician.
What were the notable HashiCorp updates?
designcenter: add google_design_center_space resource, iambeta: add discovery_uri and actor_providers fields, and agenticapplications: add mcp_data_sources.request_headers.