Infrastructure-as-Code Quality
weight 20%The pipeline is defined as google-provider Terraform: one root module per stage with separate state, a pinned provider, APIs managed as code, and additive IAM only.
Tier 0 (deterministic)
- • terraform fmt -check (no diffs)
- • terraform validate per stage (passes)
- • tflint (no errors)
- • checkov (no HIGH/CRITICAL severity findings on infra)
Tier 1 (AI scored)
- • Stages are separate root modules with their own state (blast-radius boundaries), composed through outputs/remote state, not cross-stage mutation
- • google provider pinned, project targeting explicit through variables, no hardcoded project IDs or numbers beyond documented variables
- • Discovery-first pattern present: discovery changes nothing and emits a gap map, and activation acts only on the measured gap while continuing to manage what it created
- • APIs enabled as code with disable_on_destroy = false, and IAM written additively (*_iam_member), never authoritative *_iam_policy or *_iam_binding on shared resources
- • Remote state in a versioned Cloud Storage backend with public access prevention and uniform bucket-level access, treated as a controlled resource
Scoring bands
- 90-100
- All Tier 0 pass; staged states with clean contracts; conditional activation driven by discovery outputs; APIs as code; additive IAM throughout; state bucket hardened.
- 70-89
- Tier 0 mostly passes; stages present but some boundary violations, unconditional activation, or an authoritative IAM resource the candidate documents.
- 50-69
- Single monolithic state, hardcoded identifiers, authoritative IAM that would wipe existing access, or multiple Tier 0 failures.
- 0-49
- No Terraform, fails to validate, or the pipeline shape is absent.