HashiCorp Released Terraform Google Cloud Provider 8.0
The update introduces mandatory schema changes and removes support for retired cloud services.
Updated on Oct. 9, 2026 in Data Centers
Live Poll
Do you prefer software updates that maintain backward compatibility over those that remove legacy features?
HashiCorp has released version 8.0 of the Terraform Google Cloud provider, a major update that is now in general availability. This release includes significant breaking changes, such as the removal of resources linked to discontinued Google Cloud services and modifications to schema types.
Why it matters
The transition to version 8.0 addresses long-standing infrastructure discrepancies by shifting order-insensitive attributes from lists to sets. It requires manual configuration adjustments to accommodate these schema updates and the removal of deprecated resource hooks.
The 8.0 provider updates require OpenTofu 1.11 or later to support new write-only attributes. The shift from lists to sets for order-insensitive attributes aims to eliminate perpetual plan differences, a change documented under OpenTofu issue 3787.
The players
HashiCorp
The developer of infrastructure-as-code software including Terraform, a tool for defining and provisioning cloud resources via configuration files.
Google Cloud
A suite of cloud computing services that hosts the resources managed by the updated provider.
OpenTofu
An open-source infrastructure-as-code tool that provides an alternative to the Terraform CLI.
The details
The update changes default load balancing settings for two specific Compute Engine resources to align with current cloud service standards. To migrate, teams must first upgrade to the latest 7.x provider version before adopting 8.0. The migration process necessitates manual intervention to refactor configuration files where resources were removed or data types were strictly converted from lists to sets.
Timeline
HashiCorp announced the general availability of the provider on October 9, 2026.
The Tech Race
This release updates the foundational tooling for managing Google Cloud resources within the broader Terraform and OpenTofu ecosystem. It continues the industry trend of tightening provider schemas to ensure parity between infrastructure configuration and live cloud states.
Engineering teams must pin their provider versions and execute a two-step upgrade process by first moving to the latest 7.x release. Failure to manually update configurations for the removed resources and type changes will result in plan errors when running infrastructure updates.
The takeaway
The move to 8.0 signals a permanent shift in how resource attributes are validated within Google Cloud deployments. Teams should monitor the OpenTofu issue 3787 tracker to stay informed on the evolving support for write-only attributes and schema requirements.
Further reading
For more on managing cloud infrastructure at scale, see our Data Centers section.
Source note: This article includes information reported by InfoQ.
Live Poll
Do you prefer software updates that maintain backward compatibility over those that remove legacy features?
