Deployment operations
These commands inspect and operate the shared deployment records behind Jobs,
Services, and VMs. For persistent Kubernetes applications, see
anycloud worker.
anycloud status
anycloud status [id]
anycloud status <id> --watch
anycloud status <id> --history
anycloud status <id> --json
| Option | Description |
|---|---|
--verbose | Show detailed events and error information |
--history | Show every Service upgrade section |
-w, --watch | Poll until a terminal state |
--interval SECONDS | Watch interval; default 5, minimum 1 |
-p, --period WINDOW | Picker window, such as 7d or 24h |
-n, --limit COUNT | Picker limit; default 200, maximum 1,000 |
--json | Raw StatusResponse JSON |
For a Service that has been upgraded, human-readable status shows only the
latest upgrade section by default and reports how many earlier deployment
versions are hidden. Pass --history to show the initial deployment and every
upgrade in chronological order. JSON always retains the complete flat
events[] history.
JSON contains deployment, vms[], and events[]. The deployment's
completedAt is when its terminal outcome became known. cleanedAt is null
while provider resources are still being released and becomes the teardown
confirmation time afterward. Each VM's independent endedAt is its compute
spend cutoff. With --watch --json, stdout is newline-delimited JSON with one
response per poll.
anycloud list
Alias: anycloud ls.
anycloud list [options]
| Option | Description |
|---|---|
-f, --filter TEXT | Substring over ID, image, cloud, region, state, session, or agent |
--status STATE | Exact state |
--type TYPE | Exact type: job, service, or vm |
--credential NAME | One named credential |
--user USER | One GitHub username or account ID |
--session ID | Session ID, prefix, label, or agent:hash |
--agent NAME | Agent name |
-p, --period WINDOW | Start-time window |
-n, --limit COUNT | Default 200, maximum 1,000 |
--json | Compact JSON array |
--csv | Header plus one row per deployment |
--only-ids | One deployment ID per line |
A bare interactive command opens a summary picker. Any filter or
machine-readable flag prints directly. Non-interactive agent invocations
default to their own detected session; an explicit --session or --agent
overrides that cooperative scope.
On a hosted API shared with other GitHub users, the listing covers everyone's
deployments. When the returned rows include another account's work, it adds a
USER column naming each creator even if that account is the result's only
creator. The interactive summary offers "by user" when several creators are
present. Narrow to one person with --user, which accepts a username or an
account ID. An account ID still matches work submitted before a username
change; the username does not, because it is recorded once at submit time.
Human-readable, JSON, and CSV output use Service terminology. Machine-readable
rows identify Services with deploymentType: "service".
anycloud exec
anycloud exec [id] "<command>"
On VM-host providers, including Vast, the command runs inside the workload container over the API's SSH transport. Worker-targeted Jobs reject exec because multiple Jobs may share the persistent process.
anycloud logs
anycloud logs [id] [--follow]
| Option | Description |
|---|---|
-f, --follow | Stream until interrupted |
-w, --watch | Alias for --follow |
VM-host deployments stream Docker logs. Worker-targeted Jobs reject logs; observe the persistent application's logs through Kubernetes tooling when needed.
anycloud ssh
anycloud ssh [id]
anycloud ssh <id> --host
anycloud ssh <id> --vm
anycloud ssh <id> --snapshot
The default opens a shell inside the workload container. --host opens the
underlying host; --vm is its compatibility alias. --snapshot commits an
exited container and opens a shell in the snapshot. A stopped VM container is
never bypassed with an implicit host shell, and VMs do not support --snapshot.
Provider-run-image substrates and Worker-targeted Jobs do not support the
interactive SSH shell.
anycloud terminate
Terminate one or more deployments and clean up their cloud resources:
anycloud terminate [ids...]
With no ID in a terminal, choose deployments interactively.
anycloud resubmit
Put terminal deployments back in the queue with the same configuration:
anycloud resubmit [ids...]
VMs cannot be resubmitted; use anycloud vm <image> to create a new host.