Runtimes
Manage agent runtime environments.
$ dn runtime <command>Manage agent runtime environments.
Aliases: ls
$ dn runtime listList runtimes in your workspace.
Runtimes you do not own are listed too — reads span the workspace — and are
marked read-only, since starting, pausing, resuming or resetting one
answers 403. Use --mine to leave them out.
Options
--state,--status— Filter by runtime status (idle,running,paused). Repeatable; values combine with OR. Also accepts--status. [choices: idle, running, paused]--project-id— Only show runtimes belonging to this project UUID.--mine(defaultFalse) — Only show runtimes you own, and can therefore operate.--limit(default50) — Maximum results to show. Server pages are walked internally.--json(defaultFalse) — Output as JSON.
$ dn runtime get <runtime-id>Get details of a runtime.
Options
<runtime-id>,--runtime-id(Required) — Runtime key or UUID, as shown bydn runtime list.--json(defaultFalse) — Output as JSON.
create
Section titled “create”Aliases: new
$ dn runtime createEnsure a runtime exists for a project or the workspace default project.
Idempotent — re-running against an existing runtime returns it unchanged.
Options
<project-ref>,--project-ref— Project key or UUID. Defaults to the active project scope, then workspace default.--key— Runtime key. Required with —name when no project is resolved.--name— Runtime display name. Required with —key when no project is resolved.--description— Optional runtime description.--file— Load runtime.yaml from a file or directory.--json(defaultFalse) — Output as JSON.
$ dn runtime startStart a runtime, creating it first when the target flow requires it.
A cold start provisions a sandbox and can take a couple of minutes. Every successful call returns the runtime’s credential; retry the command if its response is lost.
Options
<target>,--target— Runtime key/UUID, or project key/UUID. Resolved as a runtime first. Defaults to the active project scope.--runtime-id— Start a specific runtime by key or UUID. Mutually exclusive with <target>.--key— Runtime key to ensure before starting.--name— Runtime name to ensure before starting.--description— Optional runtime description when ensuring a runtime.--file— Load runtime.yaml from a file or directory.--json(defaultFalse) — Output as JSON.
$ dn runtime pause <runtime-id>Pause a runtime’s sandbox, preserving its state.
Options
<runtime-id>,--runtime-id(Required) — Runtime key or UUID, as shown bydn runtime list.--json(defaultFalse) — Output as JSON.
resume
Section titled “resume”$ dn runtime resume <runtime-id>Resume a paused runtime’s sandbox.
Resuming does not return an access token. Run dn runtime start afterward
when the credential is needed.
Options
<runtime-id>,--runtime-id(Required) — Runtime key or UUID, as shown bydn runtime list.--json(defaultFalse) — Output as JSON.
keepalive
Section titled “keepalive”$ dn runtime keepalive <runtime-id>Push back a running runtime’s expiry.
Options
<runtime-id>,--runtime-id(Required) — Runtime key or UUID, as shown bydn runtime list.--extend-seconds(default300) — Seconds to extend the runtime’s expiry by.--json(defaultFalse) — Output as JSON.
$ dn runtime reset <runtime-id>Discard a runtime’s sandbox, returning the runtime to idle.
The runtime, its configuration, and its capability bindings survive; only
the compute instance and everything inside it is destroyed. This is how a
configuration change is applied to a running runtime — start never
rebuilds implicitly.
Options
<runtime-id>,--runtime-id(Required) — Runtime key or UUID, as shown bydn runtime list.--yes,-y(defaultFalse) — Skip the confirmation prompt.--json(defaultFalse) — Output as JSON.