@@ -1001,6 +1001,10 @@ Query job status and results. Reads the local database by default.
10011001- ` --limit <n> ` — max results (default: ` 100 ` ).
10021002- ` --json ` — output as JSON.
10031003
1004+ ` --json ` returns the same declared row shape whether the command read the local
1005+ database or a server. The local read used to dump every column, including a
1006+ job's whole ` graph ` and ` logs ` .
1007+
10041008** Examples:**
10051009
10061010``` bash
@@ -1596,8 +1600,8 @@ The file lives in the user config directory, not the working directory:
15961600than guessing the path.
15971601
15981602** Subcommands:** ` init ` , ` add ` , ` edit ` , ` list ` , ` show ` , ` plan ` , ` apply ` ,
1599- ` status ` , ` logs ` , ` destroy ` , plus the remote groups ` workflows ` , ` database ` ,
1600- ` collections ` and the ` users-* ` verbs below.
1603+ ` status ` , ` logs ` , ` destroy ` , plus the remote group ` workflows ` and the
1604+ ` users-* ` verbs below.
16011605
16021606** Options:**
16031607
@@ -1645,33 +1649,22 @@ create it.`
16451649The full server walkthrough is [ Deployment] ( deployment.md ) and
16461650[ Self-Hosted Deployment] ( self-hosted-deployment.md ) .
16471651
1648- #### Remote workflows, rows, and collections
1652+ #### Remote workflows
16491653
1650- Once a target is up, three groups act on it over the admin API rather than on
1651- the local database:
1654+ Once a target is up, ` workflows ` acts on the deployment's ` /api/workflows `
1655+ routes rather than on the local database:
16521656
16531657``` bash
1654- # Push a local workflow and everything it references , then run it there
1658+ # Push a local workflow to the deployment , then run it there
16551659nodetool deploy workflows sync my-server < workflow_id>
16561660nodetool deploy workflows list my-server
16571661nodetool deploy workflows run my-server < workflow_id> -p prompt=" a red fox"
16581662nodetool deploy workflows delete my-server < workflow_id>
1659-
1660- # Read, upsert, and delete a single remote DB row
1661- nodetool deploy database get my-server users alice
1662- nodetool deploy database save my-server users ' {"id":"alice","role":"admin"}'
1663- nodetool deploy database delete my-server users alice
1664-
1665- # Push a local RAG collection to the deployment
1666- nodetool deploy collections sync my-server my_docs
16671663```
16681664
1669- ` workflows run ` takes ` -p, --param <k=v> ` , repeatable. ` <table> ` is passed
1670- through to the deployment, which resolves it against its own adapters — the
1671- valid names are the remote server's tables, not a list this CLI holds. ` save `
1672- takes the row as a positional JSON string, and ` get ` on a row that is not there
1673- answers ` 404 ` . ` collections sync ` uploads in batches of ` --batch-size ` ,
1674- default ` 100 ` .
1665+ ` workflows run ` takes ` -p, --param <k=v> ` , repeatable. ` sync ` pushes the
1666+ workflow row itself; the assets and models its nodes reference must already be
1667+ present on the target.
16751668
16761669#### API users on the deployment
16771670
@@ -1686,7 +1679,7 @@ nodetool deploy users-remove my-server alice
16861679```
16871680
16881681Every subcommand that touches a live deployment — the ` users-* ` verbs and the
1689- three remote groups above — sends an admin bearer token. ` --token <token> `
1682+ ` workflows ` group above — sends an admin bearer token. ` --token <token> `
16901683passes it explicitly and wins over ` NODETOOL_ADMIN_TOKEN ` ; with neither, an
16911684interactive shell prompts and a non-interactive one exits ` 1 ` .
16921685
0 commit comments