The Wire · Showcase
TERRAFORM PROVIDERS EXPAND GOOGLE CLOUD COVERAGE AND IN-PLACE UPDATES
By RepoJournal · Filed · About HashiCorp
HashiCorp shipped in-place VCS connection updates for registry modules while Google provider gains traffic config for Vertex AI and promotes NCC gateway resources to GA.
The terraform-provider-tfe landed a critical usability fix: `tfe_registry_module` can now update its VCS connection in place instead of forcing resource destruction and recreation [1]. The change routes `vcs_repo` updates through the go-tfe v2 Patch API, keeping the resource stable while swapping repository identifiers, OAuth tokens, or GitHub app installations. This eliminates painful state churn for teams rotating credentials or migrating repositories. On the Google side, the terraform-provider-google is rapidly expanding its Vertex AI coverage. The provider now supports traffic distribution configuration for Reasoning Engine deployments [2], enabling manual traffic splits and live-latest routing modes with custom diff suppression to reduce noise in plans. Separately, NCC gateway resources and spoke gateway blocks graduated from Beta to GA [3], signaling production-ready support for advanced network connectivity patterns. The provider also relaxed certificate creation constraints, making the organization field optional in `subjectConfig` [4], and added ACL enforcement controls to BigQuery data policies and Discovery Engine data stores [5] [6]. These are infrastructure-layer wins: fewer resource replacements, broader GCP service coverage, and more flexible security configurations.
One email a day. Unsubscribe in one click.
Keep up with HashiCorp in about 3 minutes a day: what actually shipped — the commits, pull requests, releases, and security advisories that matter.
One email a day. Unsubscribe in one click. Read a past issue →
Action items
- → Review tfe_registry_module configurations to identify resources that can drop ForceNew and stabilize drift [ref:1] hashicorp/terraform-provider-tfe [plan]
- → Test NCC gateway and spoke resources in staging if you use network connectivity services [ref:7] hashicorp/terraform-provider-google [plan]
- → Evaluate Vertex AI Reasoning Engine traffic config for canary and blue-green deployments [ref:6] hashicorp/terraform-provider-google [monitor]
References
- [1] [TF-37922] Support updating tfe_registry_module VCS connection in place ↗ hashicorp/terraform-provider-tfe
- [2] Add traffic config support and diff suppress to Vertex AI ReasoningEngine ↗ hashicorp/terraform-provider-google
- [3] Promote NCC Gateway Spokes and Gateway Advertised Routes to General A… ↗ hashicorp/terraform-provider-google
- [4] Make Organization field in subjectConfig optional when creating certs ↗ hashicorp/terraform-provider-google
- [5] Add data_governance_tag to google_bigquery_datapolicyv2_data_policy s… ↗ hashicorp/terraform-provider-google
- [6] discoveryengine: add acl_enabled to google_discovery_engine_data_store ↗ hashicorp/terraform-provider-google