compare-environments

Compare Environments

Compare the local Tilt development environment against the staging (ArgoCD-managed) environment to identify differences in versions, configuration, and health.

Arguments

• {application} — ArgoCD application name to compare against (optional — if omitted, compare all matching resources)

Process

Step 1: Local State

Call tilt_get_resources to get all local Tilt resources with their status.

For each service resource, call tilt_get_resource to get:

• Runtime and update status
• Pod status and image info
• Build history (latest build timestamp)
• Endpoint URLs

Step 2: Staging State

If a specific application is provided, call get_application for that app. Otherwise, use a naming convention to match Tilt resources to ArgoCD applications.

For each matched application:

• Call get_application — sync status, health, deployed revision
• Call get_application_managed_resources with kind=Deployment — extract container images and replica counts

Step 3: Diff

Compare matched resources:

Dimension	Local (Tilt)	Staging (ArgoCD)
Image tag	latest (local build)	v1.2.3
Replicas	1	3
Health	ok	Healthy
Config	dev values	staging values

Step 4: Report

## Environment Comparison: Local vs Staging

| Service | Local Status | Staging Status | Local Image | Staging Image | Staging Replicas |
|---------|-------------|----------------|-------------|---------------|------------------|
| user-svc | ok | Healthy | local-build | v1.2.3 | 3 |
| order-svc | error | Degraded | local-build | v1.2.1 | 2 |

### Key Differences
- **order-svc**: Failing in both environments — likely a code issue, not env-specific
- **user-svc**: Healthy everywhere — local changes not yet deployed to staging

### Commits Not Yet in Staging
{git log between staging revision and HEAD}

Use Cases

• Pre-deploy check: "Does staging match what I've tested locally?"
• Bug reproduction: "Is this bug in staging or only local?"
• Version tracking: "Which services are behind in staging?"