HashiCorp Released Terraform Google Cloud Provider 8.0
The update introduces major breaking changes, including resource removals and new schema requirements.
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, marking a major update for infrastructure automation. The release is now in general availability but requires significant manual configuration adjustments for users.
Why it matters
The update is necessary to remove support for retired Google Cloud services and improve reliability by preventing ongoing plan differences through schema changes. These breaking changes ensure that current infrastructure configurations remain stable and compatible with modern platform services.
The provider version 8.0 update converts several order-insensitive attributes from lists to sets. Additionally, full support for new write-only attributes requires OpenTofu 1.11 or later.
The players
HashiCorp
HashiCorp is a prominent software company known for creating tools that automate the deployment and management of cloud infrastructure.
Google Cloud
Google Cloud is a suite of cloud computing services offered by Google that runs on the same infrastructure that Google uses internally.
OpenTofu
OpenTofu is an open-source infrastructure-as-code tool that emerged as a community-driven alternative for managing cloud resources.
The details
Users must first upgrade their systems to the latest 7.x release before migrating to 8.0 to ensure a smooth transition. The update includes default load balancing changes for specific Compute Engine resources and requires manual updates to account for removed services.
Timeline
HashiCorp announced the general availability of the provider on October 9, 2026.
The Tech Race
This release continues the shift toward more rigorous infrastructure management standards within the cloud ecosystem. By forcing schema updates, HashiCorp aligns its provider with modern cloud service architectures and replaces legacy configuration patterns.
Developers and systems engineers must manually update their infrastructure configurations and pin their provider versions to avoid service disruptions. Teams relying on OpenTofu will need to ensure their software is updated to at least version 1.11 to maintain full attribute compatibility.
The takeaway
Maintaining infrastructure-as-code requires proactive monitoring of provider updates to prevent breaking changes from impacting operations. Engineers should prioritize testing in non-production environments before deploying version 8.0 to existing live stacks.
Further reading
For more information on infrastructure management, see the latest updates on Data Centers.
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?
