Status & connection vocabulary
Cushy's status words: the connection health ladder (connecting/healthy/warning/error/disconnected) and the universal ok/warn/crit/unknown resource status scale.
Connection health
Every cloud account carries one of these statuses. See Connecting an AWS account.
| Status | Meaning |
|---|---|
connecting | Created but not yet verified healthy — finish onboarding and click Verify. |
healthy | All checks pass; the account is syncing. The first healthy connection fires the cutover. |
warning | A recoverable problem (for example limited or expiring access). Sync pauses; the last known-good inventory is still served (stale-but-served). |
error | A check failed. Fix the cause (often a missing permission named in the response) and re-verify. |
disconnected | You disconnected it. Sync stopped; discovered rows are retained and marked account_disconnected. |
Resource & topology status
Resources, alerts and network links share one status scale, always shown as colour plus glyph plus text so it is colour-blind safe and identical in both themes. A resource that is not yet live carries a lifecycle status instead of a health status.
| Glyph | Key | Meaning |
|---|---|---|
| ● ok | ok | Healthy / operating normally. |
| ▲ warn | warn | Degraded or anomalous; needs attention. |
| ■ crit | crit | Failing; likely impacting. |
| ◇ unknown | unk | Insufficient signal, or a read-only view. |
| ◌ draft | planned | Lifecycle: in a Terraform plan, not applied yet (muted, dashed — deliberately not a health colour). |
| ✕ deploy failed | failed | Lifecycle: an apply failed and nothing exists in the cloud — visually distinct from a live critical alert. |
Soft-delete reasons
| Reason | Meaning |
|---|---|
removed_upstream | The resource disappeared in the cloud; its row is kept, soft-deleted. |
account_disconnected | Its account was disconnected; the row is retained for history. |