● Covered by 1 source · 1 reportMedium impact1 neutral
HashiCorp Releases Terraform Google Cloud Provider 8.0 with Load Balancer Default Changes
Key points
- Default load balancing for Compute Engine resources changed to EXTERNAL_MANAGED.
- Resources linked to retired Google Cloud services have been removed.
- Order-insensitive attributes converted from lists to sets to prevent diffs.
- Users must update configurations and clear deprecation warnings before upgrading.
Default Load Balancing Scheme Update
Version 8.0 of the Terraform Google Cloud provider introduces a significant change to the default load balancing scheme for `google_compute_backend_service` and `google_compute_global_forwarding_rule`. The `load_balancing_scheme` now defaults to `EXTERNAL_MANAGED` instead of `EXTERNAL`. This means new configurations will use the external Application Load Balancer by default. Existing configurations that rely on the Classic Load Balancer must explicitly set `load_balancing_scheme = "EXTERNAL"` to avoid unintended changes.
Removal of Deprecated Resources
The release removes several resources and data sources that correspond to Google Cloud services that have been shut down or replaced. These include `google_iap_brand` and `google_iap_client` due to the IAP OAuth Admin APIs shutdown, `google_notebooks_*` resources (replaced by `google_workbench_instance`), `google_ml_engine_model`, and BeyondCorp app connection resources (replaced by Security Gateway resources). `google_vertex_ai_schedule` is replaced by `google_colab_schedule`. Users must update their Terraform configurations to remove references to these deprecated resources before upgrading to version 8.0.
Schema Behavior Changes
To prevent perpetual plan differences, attributes where the order of elements does not matter have been converted from lists to sets. This change affects fields in Compute Service Attachments, GKE logging and monitoring configurations, and Cloud Security Compliance Frameworks. This ensures that Terraform plans do not propose changes solely due to API responses returning values in a different order than configured. Additionally, validation has become stricter for some Google Cloud APIs, requiring fields like `source_contents` for `google_workflows_workflow` and `claim_mapping` for Workforce Identity Pool Provider SCIM tenants.
Upgrade Recommendations
As a breaking release, HashiCorp advises users to first upgrade to the latest 7.x release and resolve any deprecation warnings before attempting to upgrade to version 8.0. Some state changes, such as integer-to-string conversions, will migrate automatically, while others will require manual configuration edits. The provider also now supports Terraform list resources, which integrate with the `terraform query` workflow.
✨ This summary was generated by AI from the outlets' reporting listed below. It is not independently verified and may contain errors — check the original sources. How BrevFeed works →
The daily brief
One email each morning: the day's tech stories, clustered across outlets and summarized. No account needed.
One email a day. Unsubscribe in one click, any time.
Today's brief
Spend a few minutes, get the whole day. Every topic's top stories in one hands-free rundown — listen, watch, or read the transcript.
▶ Play today's brief
New every morning, and the back catalogue is archived by date.
Primary sources
GitHub opentofu/opentofuReporting from
HashiCorp has released version 8.0 of the Terraform Google Cloud provider, which updates default load balancing for Compute Engine resources and removes resources tied to retired Google Cloud services. This major release requires users to update configurations due to breaking changes, including a shift from EXTERNAL to EXTERNAL_MANAGED for default load balancing schemes.