HashiCorp Releases Google Cloud Provider 8.0 with Native Resource Discovery
HashiCorp has officially released version 8.0 of the Terraform provider for Google Cloud. Developed in continued partnership with Google Cloud engineering, this major release expands native support for Terraform list resources, cleans up technical debt by eliminating deprecated service interfaces, modernizes default provider settings, and tightens parity between HCL configurations and upstream Google Cloud APIs.
The headline capability in provider 8.0 is the maturation of list resources paired with the `terraform query` workflow. Instead of requiring engineers to rely on custom discovery scripts or tedious manual `terraform import` operations, the provider now natively inspects unmanaged cloud infrastructure across key services—including Google Compute Engine, IAM, BigQuery, Pub/Sub, Secret Manager, and Network Services. Teams can directly query live environments to generate corresponding Terraform resource blocks and import declarations, drastically simplifying Day-2 adoption for teams retrofitting IaC across existing environments.
This release fits into a broader macro shift across the Infrastructure as Code domain: bridging the gap between static declarative definitions and live cloud realities. As multi-cloud estates expand and automated agentic tooling generates ad-hoc resources, configuration drift and unmanaged assets represent growing security and operational vulnerabilities. Upgrading IaC providers from purely unidirectional provisioning engines to bidirectional discovery systems reflects the industry's drive toward continuous state convergence and unified cloud governance.
In practice, migrating to provider 8.0 requires disciplined preparation due to breaking changes, schema realignments, and removed legacy data sources. Platform teams should first upgrade their workspaces to the latest 7.x release to clear deprecation warnings before bumping to 8.0. Once updated, practitioners should actively incorporate list resource queries into platform auditing pipelines and migration runs to automate the discovery and codification of orphaned cloud components.
Read original source