1.7 KiB
Step 11 — Implementation Detail
Built on 2026-10-07 as skills/google-cloud-iac-patterns/. The name carries the Cloud provider because the content does; the provider bundle assigns it to the IaC author (role_skills.iac-author), so another provider brings its own patterns Skill with no code change.
SKILL.mdsays how to use the patterns and lists one reference per product.assets/versions.tfpinshashicorp/google8.6.0, the versionproviders/gcp.yamlpins (step 18).- Thirteen references, each a short list of what goes wrong and one self-contained pattern: enabling APIs, IAM, Cloud Run service, Cloud Run job, Pub/Sub, Cloud Storage, Secret Manager, Cloud KMS, Cloud SQL, VPC networking, Cloud Scheduler, Artifact Registry, Monitoring and Logging.
- Seeded from the 2026-10-07 run's lesson candidates. All 13 Terraform refusals were
startup_cpu_boostorcpu_idlein the wrong block or on a Cloud Run job. The service reference says which block each setting sits in; the job reference lists what a job does not have.
Differs from the plan: the plan's acceptance is a fall in IaC author Revisions or tokens on the three cases. No evaluation has run, so that is unmeasured. What is verified is that the patterns are correct.
Tests: tests/test_iac_patterns.py runs terraform validate on every reference's pattern with the Skill's own versions file (13 pass against the real provider from the plugin cache; skipped when the provider cannot be installed), checks every reference is listed in SKILL.md, and checks the Skill and the bundle pin the same version.
Not done: load balancing, Firestore, BigQuery, Eventarc and GKE have no reference. A product with none is written from terraform_schema and the documentation.