Managing DigitalOcean App Platform
Manage DigitalOcean App Platform using the doctl apps CLI.
MANDATORY: Discovery-First Pattern
Always discover available resources before performing analysis.
Phase 1: Discovery
#!/bin/bash
echo "=== Apps ==="
doctl apps list --format ID,Spec.Name,DefaultIngress,ActiveDeployment.Phase,Region,UpdatedAt --no-header 2>/dev/null | head -20
echo ""
echo "=== App Tiers ==="
doctl apps tier list --format Name,Slug,BuildSeconds,EgressBandwidthBytes --no-header 2>/dev/null | head -10
echo ""
echo "=== App Regions ==="
doctl apps region list --format Slug,Label,Default --no-header 2>/dev/null | head -10
Phase 2: Analysis
#!/bin/bash
APP_ID="${1:?App ID required}"
echo "=== App Details ==="
doctl apps get "$APP_ID" --format ID,Spec.Name,DefaultIngress,ActiveDeployment.Phase,Region,CreatedAt,UpdatedAt --no-header 2>/dev/null
echo ""
echo "=== App Components ==="
doctl apps get "$APP_ID" -o json 2>/dev/null | jq '{
services: [.spec.services[]? | {name, http_port, instance_count, instance_size_slug, source: (.github.repo // .git.repo_clone_url // "N/A")}],
workers: [.spec.workers[]? | {name, instance_count, instance_size_slug}],
static_sites: [.spec.static_sites[]? | {name, source: (.github.repo // "N/A")}],
databases: [.spec.databases[]? | {name, engine, version, production}],
jobs: [.spec.jobs[]? | {name, kind, instance_count}]
}' | head -30
echo ""
echo "=== Recent Deployments ==="
doctl apps list-deployments "$APP_ID" --format ID,Phase,Progress,CreatedAt,UpdatedAt --no-header 2>/dev/null | head -10
echo ""
echo "=== App Logs (Recent) ==="
doctl apps logs "$APP_ID" --type run --follow=false 2>/dev/null | tail -20
echo ""
echo "=== App Domains ==="
doctl apps list-domains "$APP_ID" --format ID,Spec.Domain,Phase --no-header 2>/dev/null | head -10
echo ""
echo "=== Alerts ==="
doctl apps list-alerts "$APP_ID" --format ID,Spec.Rule,Spec.Disabled --no-header 2>/dev/null | head -10
echo ""
echo "=== Deployment Details (Latest) ==="
DEPLOY_ID=$(doctl apps list-deployments "$APP_ID" --format ID --no-header 2>/dev/null | head -1)
if [ -n "$DEPLOY_ID" ]; then
doctl apps get-deployment "$APP_ID" "$DEPLOY_ID" -o json 2>/dev/null | jq '{
id, phase, progress,
services: [.services[]? | {name, source_commit_hash: .source_commit_hash[:8]}],
created_at, updated_at
}'
fi
Output Format
APP_ID NAME INGRESS PHASE REGION
abc123-def456-ghi789 my-app my-app-abc12.ondigitalocean ACTIVE nyc
Safety Rules
- Use read-only commands:
list, get, logs
- Never run
delete, update, create without explicit user confirmation
- Use
--format and --no-header for clean output
- Limit output with
| head -N and | tail -N to stay under 50 lines
Anti-Hallucination Rules
- NEVER assume resource names — always discover via CLI/API in Phase 1 before referencing in Phase 2.
- NEVER fabricate metric names or dimensions — verify against the service documentation or
--help output.
- NEVER mix CLI commands between service versions — confirm which version/API you are targeting.
- ALWAYS use the discovery → verify → analyze chain — every resource referenced must have been discovered first.
- ALWAYS handle empty results gracefully — an empty response is valid data, not an error to retry.
Counter-Rationalizations
| Shortcut |
Counter |
Why |
| "I'll skip discovery and check known resources" |
Always run Phase 1 discovery first |
Resource names change, new resources appear — assumed names cause errors |
| "The user only asked for a quick check" |
Follow the full discovery → analysis flow |
Quick checks miss critical issues; structured analysis catches silent failures |
| "Default configuration is probably fine" |
Audit configuration explicitly |
Defaults often leave logging, security, and optimization features disabled |
| "Metrics aren't needed for this" |
Always check relevant metrics when available |
API/CLI responses show current state; metrics reveal trends and intermittent issues |
| "I don't have access to that" |
Try the command and report the actual error |
Assumed permission failures prevent useful investigation; actual errors are informative |
1---2name: managing-digitalocean-app-platform3description: Use when working with Digitalocean App Platform — digitalOcean App Platform management via the doctl CLI. Covers apps, components, deployments, logs, domains, alerts, and billing. Use when managing App Platform applications or checking deployment health.4---56# Managing DigitalOcean App Platform78Manage DigitalOcean App Platform using the `doctl apps` CLI.910## MANDATORY: Discovery-First Pattern1112**Always discover available resources before performing analysis.**1314### Phase 1: Discovery1516```bash17#!/bin/bash1819echo "=== Apps ==="20doctl apps list --format ID,Spec.Name,DefaultIngress,ActiveDeployment.Phase,Region,UpdatedAt --no-header 2>/dev/null | head -202122echo ""23echo "=== App Tiers ==="24doctl apps tier list --format Name,Slug,BuildSeconds,EgressBandwidthBytes --no-header 2>/dev/null | head -102526echo ""27echo "=== App Regions ==="28doctl apps region list --format Slug,Label,Default --no-header 2>/dev/null | head -1029```3031### Phase 2: Analysis3233```bash34#!/bin/bash3536APP_ID="${1:?App ID required}"3738echo "=== App Details ==="39doctl apps get "$APP_ID" --format ID,Spec.Name,DefaultIngress,ActiveDeployment.Phase,Region,CreatedAt,UpdatedAt --no-header 2>/dev/null4041echo ""42echo "=== App Components ==="43doctl apps get "$APP_ID" -o json 2>/dev/null | jq '{44 services: [.spec.services[]? | {name, http_port, instance_count, instance_size_slug, source: (.github.repo // .git.repo_clone_url // "N/A")}],45 workers: [.spec.workers[]? | {name, instance_count, instance_size_slug}],46 static_sites: [.spec.static_sites[]? | {name, source: (.github.repo // "N/A")}],47 databases: [.spec.databases[]? | {name, engine, version, production}],48 jobs: [.spec.jobs[]? | {name, kind, instance_count}]49}' | head -305051echo ""52echo "=== Recent Deployments ==="53doctl apps list-deployments "$APP_ID" --format ID,Phase,Progress,CreatedAt,UpdatedAt --no-header 2>/dev/null | head -105455echo ""56echo "=== App Logs (Recent) ==="57doctl apps logs "$APP_ID" --type run --follow=false 2>/dev/null | tail -205859echo ""60echo "=== App Domains ==="61doctl apps list-domains "$APP_ID" --format ID,Spec.Domain,Phase --no-header 2>/dev/null | head -106263echo ""64echo "=== Alerts ==="65doctl apps list-alerts "$APP_ID" --format ID,Spec.Rule,Spec.Disabled --no-header 2>/dev/null | head -106667echo ""68echo "=== Deployment Details (Latest) ==="69DEPLOY_ID=$(doctl apps list-deployments "$APP_ID" --format ID --no-header 2>/dev/null | head -1)70if [ -n "$DEPLOY_ID" ]; then71 doctl apps get-deployment "$APP_ID" "$DEPLOY_ID" -o json 2>/dev/null | jq '{72 id, phase, progress,73 services: [.services[]? | {name, source_commit_hash: .source_commit_hash[:8]}],74 created_at, updated_at75 }'76fi77```7879## Output Format8081```82APP_ID NAME INGRESS PHASE REGION83abc123-def456-ghi789 my-app my-app-abc12.ondigitalocean ACTIVE nyc84```8586## Safety Rules87- Use read-only commands: `list`, `get`, `logs`88- Never run `delete`, `update`, `create` without explicit user confirmation89- Use `--format` and `--no-header` for clean output90- Limit output with `| head -N` and `| tail -N` to stay under 50 lines9192## Anti-Hallucination Rules93941. **NEVER assume resource names** — always discover via CLI/API in Phase 1 before referencing in Phase 2.952. **NEVER fabricate metric names or dimensions** — verify against the service documentation or `--help` output.963. **NEVER mix CLI commands between service versions** — confirm which version/API you are targeting.974. **ALWAYS use the discovery → verify → analyze chain** — every resource referenced must have been discovered first.985. **ALWAYS handle empty results gracefully** — an empty response is valid data, not an error to retry.99100## Counter-Rationalizations101102| Shortcut | Counter | Why |103|----------|---------|-----|104| "I'll skip discovery and check known resources" | Always run Phase 1 discovery first | Resource names change, new resources appear — assumed names cause errors |105| "The user only asked for a quick check" | Follow the full discovery → analysis flow | Quick checks miss critical issues; structured analysis catches silent failures |106| "Default configuration is probably fine" | Audit configuration explicitly | Defaults often leave logging, security, and optimization features disabled |107| "Metrics aren't needed for this" | Always check relevant metrics when available | API/CLI responses show current state; metrics reveal trends and intermittent issues |108| "I don't have access to that" | Try the command and report the actual error | Assumed permission failures prevent useful investigation; actual errors are informative |109