Workflow Start
Start workflow from first step
Usage
Terminal
dxflow workflow start <IDENTITY> [OPTIONS]
Options
| Flag | Shorthand | Description | Type | Default |
|---|---|---|---|---|
--link | -l | Assign a link to every step declaring one | bool | false |
--override | -o | Override value as key=value; repeatable | stringSlice | `` |
Override keys are <category>.<step>.<key>, scoped to a step by its name — volume.<step>.<volume-name> and port.<step>.<port-name> (host side), env.<step>.<VAR>, and resource.<step>.<cpu\|memory\|gpu>. The values are written to the workflow's workflow.ini before it starts and applied only at launch — they never modify the workflow definition (workflow.json). An unknown step / volume / port name, or an invalid cpu/memory/gpu value, fails the start.
--link assigns a link to every step declaring one under link in the definition, while the license carries any. Left out, the start runs the steps with their declared links idle. The success line carries what the start assigned, one [link → step] detail per link.
Example
Terminal
dxflow workflow start my-workflow \
--link \
--override volume.step-name.data=/mnt/host/data \
--override env.step-name.KEY=value \
--override resource.step-name.cpu=8