Generate Plan

From the spec detail page, click Plan. Select a Runner to execute. A PLAN job is queued.

The Runner:

1. Assumes cloud credentials (how)
2. Generates Terraform variable files from the spec's config snapshot
3. Runs terraform init with Supabase S3 backend (state management)
4. Runs terraform plan -out=plan.tfplan
5. Runs terraform show -json for structured output
6. Optionally runs Infracost for cost breakdown (cost estimation)
7. Uploads the plan artifact to Supabase S3
8. Reports resource change counts and costs

Review Plan

The Plan tab in spec detail shows:

Plan Summary Bar:

• Resources to create (green count)
• Resources to update (yellow count)
• Resources to destroy (red count)
• Estimated monthly cost

Resource Groups: Collapsible sections grouped by resource type (e.g., "AWS EKS", "AWS VPC", "AWS RDS"). Each resource shows:

• Resource address (e.g., module.eks.aws_eks_cluster.main)
• Action: create / update / delete
• Per-resource monthly cost (from Infracost)

Cost Breakdown: Total estimated monthly cost with per-resource itemization.

Apply

Click Apply to provision. Select a Runner. A DEPLOY job is queued.

The Runner:

1. Downloads the plan artifact from the PLAN job
2. Validates the config hash — if the spec was modified after planning, the apply fails with a hash mismatch error
3. Runs terraform apply plan.tfplan
4. Extracts Terraform outputs (cluster endpoint, database endpoints, etc.)
5. Installs ArgoCD via Helm (GitOps)
6. Reports cluster metadata back to Alethia

Finalization

On DEPLOY success, Alethia's finalizeDeployment() server action:

• Updates spec_cluster with cluster name, endpoint, ARN, ArgoCD URL and password
• Updates spec_databases with writer/reader endpoints, credentials ARNs
• Updates spec_caches with primary/reader endpoints
• Sets spec status to ACTIVE