atmos-component-hygiene

Atmos Component Hygiene Check

Overview

Automated checklist for validating Atmos Terraform components against common mistakes. Run this after adding or modifying a component to catch issues before they reach PR review.

When to Use

• After creating a new Terraform component
• After modifying an existing component's variables, outputs, or resources
• Before committing component changes
• During PR review of component changes

When NOT to Use

• Reviewing non-Atmos Terraform repos (standard modules without Atmos stack config)
• Pure Atmos stack YAML changes that don't touch component code
• Third-party module reviews where you don't control the component structure
• Cost optimization reviews (use terraform-cost-review instead)

Checks

First detect repo layout, then run checks against every component. Full check definitions and verification steps are in check-tables.md.

Repository-level (R1-R8): Verify gitignore rules for provider.tf, backend.tf, state files, and lock files. Confirm .tflint.hcl exists, terraform-docs is configured in pre-commit, and tflint runs in CI.

Per-component (C1-C10): Verify no committed provider.tf or backend.tf, versions.tf has constraints, baseline variables exist (aws_region, environment, tags, stage), README has terraform-docs markers, no hardcoded regions or account IDs, and tags are applied to resources.

Severity levels: Critical (blocks deployment or causes conflicts), Important (causes maintenance pain), Warning (best practice).

Running the Check

digraph check_flow {
    rankdir=TB;
    node [shape=box];

    start [label="Run repo-level checks (R1-R8)"];
    repo_pass [label="All pass?" shape=diamond];
    fix_repo [label="Report repo-level failures"];
    components [label="For each component\nrun C1-C10"];
    report [label="Report results per component"];
    done [label="Summary: PASS / FAIL with details"];

    start -> repo_pass;
    repo_pass -> components [label="yes"];
    repo_pass -> fix_repo [label="no"];
    fix_repo -> components;
    components -> report;
    report -> done;
}