portal-terraform-gcp

Defines minimal GCP infrastructure with Terraform for Cloud Run, GCS, and Secret Manager.

Updated Jul 27, 2026
One-click install
npx skills add https://github.com/ArthurZizumbo/karisma-data --skill portal-terraform-gcp-arthurzizumbo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: portal-terraform-gcp
Source: https://github.com/ArthurZizumbo/karisma-data/tree/main/.claude/skills/portal-terraform-gcp
Command: npx skills add https://github.com/ArthurZizumbo/karisma-data --skill portal-terraform-gcp-arthurzizumbo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams need reproducible, cost-controlled GCP infrastructure for a financial data portal without over-provisioning or leaking secrets. This Skill codifies the Terraform module for two scale-to-zero Cloud Run services, a GCS exports bucket with 7-day lifecycle, and Secret Manager injection, enforcing FinOps and security rules. ## Core Features & Use Cases - Minimal Terraform module: Provisions 2 Cloud Run services (frontend/backend) with min_instances = 0, a GCS exports bucket with 7-day lifecycle, and Secret Manager secrets injected via secret_key_ref. - Security guardrails: Secrets never in tfvars or the repo, least-privilege runtime service account, and human review of terraform plan before apply. - Bootstrap and bridge: Documents one-time gcloud setup (APIs, deploy service account) and an accepted gcloud run deploy bridge script while Terraform matures. - Use Case: When creating or modifying the infra/ module for the Portal Centralizado de Datos Financieros, use this Skill to generate compliant HCL and validate it against the QA checklist. ## Quick Start Ask the assistant to create the infra/ Terraform module for the portal with two scale-to-zero Cloud Run services, a GCS exports bucket, and secrets injected from Secret Manager.

Frequently Asked Questions about portal-terraform-gcp

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

FAQPage Schema
How do I inject secrets into Cloud Run with Terraform?

Use the secret_key_ref block inside the Cloud Run v2 service env definition, referencing a google_secret_manager_secret resource. Secret values are loaded outside Terraform with gcloud secrets versions add, never stored in tfvars or the repository.

How do I configure Cloud Run scale-to-zero in Terraform?

Set min_instance_count = 0 in the scaling block of google_cloud_run_v2_service. This skill keeps it at 0 for cost control, raising it to 1 only for documented demo or usability testing days.

Can I use gcloud run deploy instead of Terraform for Cloud Run?

Yes, a documented gcloud run deploy bridge script is an accepted alternative while the Terraform module matures. It must still pass --min-instances=0 and --set-secrets pointing to Secret Manager to stay compliant.

What IAM roles does a Cloud Run runtime service account need?

Follow least privilege: grant only secretmanager.secretAccessor and storage.objectAdmin on its own exports bucket. The separate CI deploy account gets roles/run.admin, artifactregistry.writer, and iam.serviceAccountUser.

Why should terraform plan be reviewed before apply?

Human review of terraform plan catches unintended resource changes, cost increases, and misconfigured IAM before they reach the project. This skill makes plan review a non-negotiable rule before any apply.