terraform-gcp
Skill4 starsChanged 4 months agoMITView on GitHub
Terraform patterns for Google Cloud using the official google and google-beta providers and Cloud Foundation Toolkit modules. Covers project structure, state management, IAM, and CFT blueprint usage. Warns before terraform apply (billable and potentially destructive). Use when the user mentions: terraform GCP, terraform google, IaC GCP, terraform plan GCP, terraform apply GCP, GCP modules, landing zone terraform, terraform google provider.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- way-platform/skillstheir own version, first seen Feb 18, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- way-platform/skills★ 4same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository21 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .claude/CLAUDE.mdCLAUDE.md
- agent-architectSkill
- bigquerySkill
- cloud-runSkill
- cloud-storageSkill
- gcloud-guardrailsSkill
- gcp-architectSkill
- gcp-opsSkill
- gcp-project-contextSkill
- gcp-qaSkill
- gcp-securitySkill
- gkeSkill
- google-skills-catalogSkill
- iamSkill
- logging-monitoringSkill
- mcp-serversSkill
- networkingSkill
- solution-designerSkill
- vertex-aiSkill
- well-architectedSkill
The file
Files
Terraform — GCP
Infrastructure as Code for Google Cloud using the official Terraform provider and Cloud Foundation Toolkit (CFT).
Safety Rule — Plan Before Apply
# Always plan first
terraform plan -out=tfplan
# Review the plan — look for unexpected destroys
# Only apply after confirming no unexpected changes
terraform apply tfplanProvider Setup
terraform {
required_providers {
google = {
source = "hashicorp/google"
version = "~> 6.0"
}
}
backend "gcs" {
bucket = "PROJECT_ID-tfstate"
prefix = "env/prod"
}
}
provider "google" {
project = var.project_id
region = var.region
}CFT Module Usage (recommended over writing from scratch)
# Example: GKE cluster via CFT module
module "gke" {
source = "terraform-google-modules/kubernetes-engine/google//modules/autopilot-cluster"
version = "~> 33.0"
project_id = var.project_id
name = "my-cluster"
region = var.region
network = module.vpc.network_name
subnetwork = module.vpc.subnets_names[0]
}State Management
- State in GCS bucket (not local, not git)
- One state file per environment (
env/dev,env/staging,env/prod) - Bucket versioning enabled for state rollback
- State lock via GCS object versioning (built in to google backend)
Module Structure (project convention)
infra/
├── modules/ # Reusable modules
│ └── service/
│ ├── main.tf
│ ├── variables.tf
│ └── outputs.tf
├── environments/
│ ├── dev/
│ │ ├── main.tf # Calls modules
│ │ └── terraform.tfvars
│ └── prod/
│ ├── main.tf
│ └── terraform.tfvars
└── backend.tfReferences
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

