How do I run the workflow_plan_dependencies commands from the shell?

Reads one page of the collection. Nothing addresses it but the caller's tenant, so it is the read that shows what exists.

The command is shaped like this:

workflow_plan_dependencies list [--offset <n>] [--limit <n>] [--order <field>] [--desc]

It is addressed at workflow.v1.workflow_plan_dependencies.list.

workflow_plan_dependencies list --limit 1

Reads the one row its key addresses. A key states every identifying column, so a partial key is refused rather than answered with an arbitrary row.

The command is shaped like this:

workflow_plan_dependencies get <id>

It is addressed at workflow.v1.workflow_plan_dependencies.get.

workflow_plan_dependencies get 00000000-0000-0000-0000-000000000000

Reads several rows in one request, one key group per row.

The command is shaped like this:

workflow_plan_dependencies get-many <id>

It is addressed at workflow.v1.workflow_plan_dependencies.get_many.

workflow_plan_dependencies get-many 00000000-0000-0000-0000-000000000000

Writes a row. The change states that the row must not exist, so a create that collides with an existing row is refused rather than replacing it. The change carries a reason and a commentary, which the server records on it so the row's history says why it moved.

The command is shaped like this:

workflow_plan_dependencies add <workflow_id> <consumer_step_index> <producer_step_index> <reason> <commentary>

It is addressed at workflow.v1.workflow_plan_dependencies.put.

workflow_plan_dependencies add 00000000-0000-0000-0000-000000000000 0 0 system.new_record generated_script

Writes a row. The change states no precondition, so it replaces whatever row the key already addresses. The change carries a reason and a commentary, which the server records on it so the row's history says why it moved. Passing –version makes the write conditional on the version the caller last read.

The command is shaped like this:

workflow_plan_dependencies set <id> <workflow_id> <consumer_step_index> <producer_step_index> <reason> <commentary> [--version <n>]

It is addressed at workflow.v1.workflow_plan_dependencies.put.

workflow_plan_dependencies set 00000000-0000-0000-0000-000000000000 00000000-0000-0000-0000-000000000000 0 0 system.new_record generated_script

Writes several rows in one request. The count states how many field groups follow. The change carries a reason and a commentary, which the server records on it so the row's history says why it moved.

The command is shaped like this:

workflow_plan_dependencies put-many --count <n> <id> <workflow_id> <consumer_step_index> <producer_step_index> <reason> <commentary>

It is addressed at workflow.v1.workflow_plan_dependencies.put_many.

workflow_plan_dependencies put-many --count 1 00000000-0000-0000-0000-000000000000 00000000-0000-0000-0000-000000000000 0 0 system.new_record generated_script

Removes a row. The change carries a reason and a commentary, which the server records on it so the row's history says why it moved. Passing –version makes the write conditional on the version the caller last read.

The command is shaped like this:

workflow_plan_dependencies delete <id> <reason> <commentary> [--version <n>]

It is addressed at workflow.v1.workflow_plan_dependencies.delete.

workflow_plan_dependencies delete 00000000-0000-0000-0000-000000000000 system.new_record generated_script

Removes several rows in one request. The change carries a reason and a commentary, which the server records on it so the row's history says why it moved.

The command is shaped like this:

workflow_plan_dependencies delete-many <id> <reason> <commentary>

It is addressed at workflow.v1.workflow_plan_dependencies.delete_many.

workflow_plan_dependencies delete-many 00000000-0000-0000-0000-000000000000 system.new_record generated_script

Reads one page of the rows that share a relation value. The relation is part of the address rather than a filter applied after the read.

The command is shaped like this:

workflow_plan_dependencies by-workflow-id <workflow_id> [--offset <n>] [--limit <n>] [--order <field>] [--desc]

It is addressed at workflow.v1.workflow_plan_dependencies.list_by_workflow_id.

workflow_plan_dependencies by-workflow-id 00000000-0000-0000-0000-000000000000 --limit 1

Reads the row's recorded history, newest first.

The command is shaped like this:

workflow_plan_dependencies versions <id> [--offset <n>] [--limit <n>] [--order <field>] [--desc]

It is addressed at workflow.v1.workflow_plan_dependencies_versions.list.

workflow_plan_dependencies versions 00000000-0000-0000-0000-000000000000 --limit 1

Reads one recorded version of the row.

The command is shaped like this:

workflow_plan_dependencies version <id> --version <n>

It is addressed at workflow.v1.workflow_plan_dependencies_versions.get.

workflow_plan_dependencies version 00000000-0000-0000-0000-000000000000 --version 1