Auto-teardown — how environment cleanup works

Turtini automatically cleans up GCP resources when an environment is closed or deleted — no manual GCP console cleanup needed.

Teardown is triggered in three ways:
1. You click "Close" on an active environment (manual teardown)
2. The environment's TTL expires (automatic expiry teardown)
3. You delete the environment record entirely (delete teardown)

What happens during teardown:
• A Cloud Build teardown job is submitted automatically
• The job restores the OCP IPI installer state from GCS, runs "openshift-install destroy cluster", and removes all VMs, disks, VPC resources, and DNS records
• The environment status changes: active → teardown → closed
• A draft chargeback accounting entry is written when status reaches "closed"

Delete vs. Close:
• Close — marks the environment as "teardown", triggers cleanup, keeps the record for your history
• Delete — removes the record from Turtini and triggers cleanup if a GCS installer state file exists (meaning the cluster fully or partially provisioned)

If an environment never fully provisioned (no GCS state), delete exits cleanly with no Cloud Build job — there's nothing to clean up.

You can verify teardown ran by checking Accounting → Journal Entries for a draft chargeback entry, or by watching the environment status change to "closed".