terraform-gcp

Validate Terraform for Google Cloud specs for safe, production-ready patterns.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/Pyl-Tech/stream-coding --skill terraform-gcp-pyl-tech
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: terraform-gcp
Source: https://github.com/Pyl-Tech/stream-coding/tree/main/.agents/skills/terraform-gcp
Command: npx skills add https://github.com/Pyl-Tech/stream-coding --skill terraform-gcp-pyl-tech

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents broken or insecure Google Cloud Terraform changes by forcing your infrastructure specs to include the exact structure, state, security, and validation constraints before code is generated.

Core Features & Use Cases

  • Terraform/GCP documentation constraints: Enforces how modules, environments, and configuration must be written to stay portable and maintainable.
  • Safe configuration patterns: Requires YAML-driven inputs via yamldecode() with no secrets in config or state, plus Workload Identity Federation for authentication.
  • Production-grade guardrails: Mandates remote GCS state with locking, least-privilege IAM patterns, version pinning, and testing/verification expectations.

Quick Start

Ask your AI agent to generate a complete Terraform/GCP spec and module skeleton that follows this Skill’s rules, including YAML-based environment configs, GCS remote state per environment, least-privilege IAM (_iam_member), and a validation/testing section.

Frequently Asked Questions about terraform-gcp

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

FAQPage Schema
How do I enforce production-ready guardrails for GCP Terraform before generating code?

Apply YAML-driven configuration constraints with yamldecode(), remote GCS state locking, and least-privilege IAM patterns to enforce production-ready guardrails for GCP Terraform before code generation.

What's the best way to manage Terraform state and authentication for Google Cloud securely?

The best way to manage Terraform state securely is mandating remote GCS state with locking alongside Workload Identity Federation and ADC authentication to prevent insecure Google Cloud state configurations.

Can I use YAML configuration to define environment variables and modules in GCP Terraform?

Yes, you can use YAML configuration via yamldecode() to define environment inputs and module structures in GCP Terraform, ensuring portable and maintainable infrastructure-as-code without hardcoding secrets.

Does this approach to GCP Terraform support least-privilege IAM for resources like GKE and Cloud SQL?

Yes, this GCP Terraform approach supports least-privilege IAM by mandating specific _iam_member resource choices for services like GKE, Cloud SQL, and Cloud Run to avoid over-permissioned security anti-patterns.

Why does my GCP Terraform setup fail without version pinning and testing verification gates?

Your GCP Terraform setup fails because production-grade constraints require explicit version pinning and testing/verification gates to prevent broken or insecure infrastructure changes before deployment.

When do I need to refactor infrastructure-as-code for Google Cloud using module-based environments?

You need to refactor infrastructure-as-code for Google Cloud when establishing module-based environment setups for VPC, GKE, and Cloud Run that require safe, portable, and maintainable YAML-driven specifications.