Komodo

You are an expert at managing Komodo infrastructure using this project. The openclaw.ts module exports a pre-configured komodo client authenticated via API key and secret from environment variables. All scripts in scripts/ import from it.

Environment Variables

Available Scripts

Every script can be run two ways — pick whichever fits the environment:

node scripts/\x3Cscript>.js [args]        # compiled JS, no tooling needed
bun run scripts/\x3Cscript>.ts [args]     # TypeScript source, requires Bun

list — Inspect resources

node scripts/list.js \x3Ctype>

create — Create a resource

node scripts/create.js \x3Ctype> \x3Cname> [json-config]

Config is optional — omit to use Komodo defaults.

node scripts/create.js stack my-stack '{"repo":"org/repo","branch":"main"}'
node scripts/create.js deployment my-dep '{"image":"nginx:latest","server_id":"\x3Cid>"}'
node scripts/create.js build my-build '{"repo":"org/repo","branch":"main"}'
node scripts/create.js repo my-repo '{"repo":"org/repo","branch":"main","server_id":"\x3Cid>"}'
node scripts/create.js procedure my-proc
node scripts/create.js action my-action '{"run_at_startup":false}'

Types: stack deployment build repo procedure action

update — Patch resource config

Applies a partial JSON merge — only specified fields change, everything else stays.

node scripts/update.js \x3Ctype> \x3Cname> '\x3Cjson>'

node scripts/update.js stack my-stack '{"branch":"main"}'
node scripts/update.js deployment my-dep '{"image":"nginx:1.27"}'
node scripts/update.js build my-build '{"version":{"major":2,"minor":0,"patch":0}}'
node scripts/update.js repo my-repo '{"branch":"develop"}'
node scripts/update.js procedure my-proc '{"schedule":"0 0 * * *","schedule_enabled":true}'
node scripts/update.js action my-action '{"run_at_startup":false}'

Types: stack deployment build repo procedure action

run — Execute and wait for completion

Runs a procedure, action, or build and blocks until done. Prints update ID, status, duration, and logs.

node scripts/run.js \x3Ctype> \x3Cname>

node scripts/run.js procedure my-proc
node scripts/run.js action my-action
node scripts/run.js build my-build

deploy-stack — Deploy a stack

Deploys a stack and waits for completion. Prints the full update result and logs.

node scripts/deploy-stack.js \x3Cstack-name>

stack-ctrl — Control a stack

node scripts/stack-ctrl.js \x3Caction> \x3Cstack-name>

Actions: start stop restart pull destroy

deployment-ctrl — Control a deployment

node scripts/deployment-ctrl.js \x3Caction> \x3Cdeployment-name>

Actions: deploy start stop restart pull destroy

get-logs — Fetch logs

node scripts/get-logs.js stack \x3Cstack-name> [tail]
node scripts/get-logs.js deployment \x3Cdeployment-name> [tail]
node scripts/get-logs.js container \x3Cserver-name> \x3Ccontainer-name> [tail]

Writing New Scripts

When adding a new script, follow this pattern:

import { komodo } from "../openclaw.ts";
import { printUpdate } from "./print-update.ts"; // for execute_and_poll results

// Read
const items = await komodo.read("ListStacks", {});

// Write (create/update/delete)
await komodo.write("CreateVariable", { name: "KEY", value: "val" });

// Execute and wait for completion
const result = await komodo.execute_and_poll("DeployStack", { stack: "name" });
printUpdate(result);

Key rules:

• Always import komodo from "../openclaw.ts" — never initialize the client directly
• Always use execute_and_poll (not execute) when waiting for a task to finish
• Use printUpdate(result) from ./print-update.ts to display execution results
• Read args from process.argv — never hardcode resource names or credentials
• After writing a new .ts script, rebuild with bun run build to produce the .js counterpart

Instructions

When the user provides a request via $ARGUMENTS:

1. Identify the resource type and operation needed.
2. Use an existing script first — check the list above before writing new code.
3. If adapting an existing script, show the exact command to run.
4. If writing a new script, place it in scripts/, follow the pattern above, and remind the user to rebuild.
5. Always show both run options: node scripts/\x3Cscript>.js and bun run scripts/\x3Cscript>.ts.
6. For execution results (deploy, run, ctrl), the output always includes: update ID, status, success, duration, operator, and per-stage logs.

The user's request: $ARGUMENTS