dodil ignite invoke + dodil ignite execution
Two things live here: invoke (run a published app) and execution (inspect the records invocations produce). Maps to ComputeService → Invocation & Executions.
| Command | API |
|---|---|
dodil ignite invoke | Invoke |
dodil ignite execution get | GetExecution |
dodil ignite execution logs | GetExecution (reads buffered logs) |
dodil ignite execution stream | WatchExecution |
dodil ignite execution watch | WatchExecution |
dodil ignite invoke
dodil ignite invoke <id> [-p '<json>'] [-f <file>] [--timeout-ms N]Invokes an app. Alias call. The <id> is org:app. The CLI reads the streamed response (head → body chunks → trailer) and prints the result plus the execution_id, HTTP status, and duration.
| Flag | Short | Default | Description |
|---|---|---|---|
--payload | -p | {} | JSON payload to send |
--payload-file | -f | — | Path to a JSON payload file (overrides -p) |
--timeout-ms | 0 | Execution timeout in milliseconds (0 = app default) |
dodil ignite invoke org:myapp -p '{"key":"value"}'
dodil ignite invoke org:myapp -f input.json
dodil ignite invoke org:myapp --timeout-ms 60000 -o json | jq '.body'Every invoke produces an execution record. Capture the
execution_idfrom the output and follow it withexecution get/watch. The structured server-stream framing ofInvokedescribed on the API invoke page is consumed by the CLI internally; for raw frames call the API directly.
dodil ignite execution
Track and inspect executions. Alias exec. Subcommands: get, logs, stream, watch (plus list, which is not supported by the current API — see below).
dodil ignite execution get
dodil ignite execution get <exec-id>Full execution detail — status, version, result, error, logs, timestamps, and metrics (cold-start ms, execution ms, memory, CPU, warm/cold). Alias show. Works for records from invoke and the test commands.
dodil ignite execution get <exec-id> -o json | jq '{status, metrics}'dodil ignite execution list
dodil ignite execution list <app-id>Listing executions for an app is not supported by the current API — the command returns an error. Use execution get with an execution_id captured from invoke.
dodil ignite execution logs
dodil ignite execution logs <exec-id> [--offset N] [--limit N]Fetches buffered logs for one execution (point-in-time, not streaming). --offset is a byte offset; --limit/-l caps bytes returned (default 65536).
dodil ignite execution logs <exec-id>
dodil ignite execution logs <exec-id> -l 131072dodil ignite execution stream
dodil ignite execution stream <exec-id>Streams execution output in real time, exiting when the execution reaches a terminal state (COMPLETED / FAILED / TIMEOUT). Alias tail.
dodil ignite execution stream <exec-id>dodil ignite execution watch
dodil ignite execution watch <exec-id>Watches status changes in real time (and prints any output chunks), exiting when the execution reaches a terminal state (COMPLETED / FAILED / TIMEOUT).
dodil ignite invoke org:myapp -o json | jq -r '.execution_id' | xargs dodil ignite execution watchSee also
- Invocation & Executions — API Reference —
Invokestreaming frames,GetExecutionStats, and the execution record contract dodil ignite draft&version—draft test/version testalso produce executions- CLI Basics — global flags, output formats, exit codes