terraform-gcp-provider

Guide Google Cloud Platform Terraform provider v6.x usage with troubleshooting and best practices.

1|Updated Mar 16, 2026
One-click install
npx skills add https://github.com/iceflower/opencode-agents-and-skills --skill terraform-gcp-provider
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: terraform-gcp-provider
Source: https://github.com/iceflower/opencode-agents-and-skills/tree/main/skills/terraform-gcp-provider
Command: npx skills add https://github.com/iceflower/opencode-agents-and-skills --skill terraform-gcp-provider

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses common issues, breaking changes, and best practices when working with the Google Cloud Platform Terraform provider, specifically version 6.x.

Core Features & Use Cases

  • Breaking Changes: Understand and mitigate changes in default behaviors like label attribution and deletion protection.
  • Troubleshooting: Resolve common errors related to project handling, service account impersonation, and API enablement timing.
  • Best Practices: Implement recommended patterns for multi-project deployments, regional resource management, and secure authentication.
  • Use Case: You're upgrading your Terraform configuration to GCP provider v6.x and encountering unexpected diffs or errors. This Skill provides immediate solutions and configuration adjustments.

Quick Start

Use the terraform-gcp-provider skill to understand the default label behavior change in v6.x.

Frequently Asked Questions about terraform-gcp-provider

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I resolve unexpected Terraform diffs after upgrading the GCP provider to v6.x?

Unexpected Terraform diffs in GCP provider v6.x often stem from breaking changes to default behaviors, such as label attribution and deletion protection. Adjust your resource configurations to explicitly declare these attributes and align with the new defaults to clear the diffs.

Why does Terraform fail when enabling Google Cloud APIs during the same run?

Terraform fails to enable Google Cloud APIs during the same run due to eventual consistency timing issues. You must wait for the API enablement to fully propagate before provisioning dependent resources, applying a targeted execution sequence to resolve the error.

What is the best way to handle multi-project deployments and service account impersonation in GCP Terraform?

The best way to handle multi-project deployments and service account impersonation is to follow secure authentication patterns. Properly configure provider blocks with target project scopes and impersonation chains to manage resources across distinct Google Cloud projects securely.

Can I use the GCP Terraform provider v6.x for regional resource management and specific configurations like GKE?

Yes, the GCP Terraform provider v6.x supports regional resource management and specific configurations for GKE and Cloud SQL. You can implement recommended best practices to define regional clusters and database instances effectively within your infrastructure as code.

How does default label behavior change in GCP Terraform provider v6.x?

Default label behavior in GCP Terraform provider v6.x changes how labels are attributed to resources, often causing unexpected state drift. You must review your configurations and explicitly manage label assignments to match the new provider expectations and maintain clean state.