opschain step
Included from Basic tier
The inside-a-step data-passing verbs: they run INSIDE a step's action and publish outputs, property writes and custom events for the engine to apply when the step succeeds. They work by appending to the files the executor names through the step's environment, so they need no server connection and work under hostexec and containerexec alike.
| Subcommand | Appends to | Page |
|---|---|---|
step set-output | $OPSCHAIN_OUTPUT / $OPSCHAIN_OUTPUT_SENSITIVE | opschain docs cli/step-set-output |
step set-property | $OPSCHAIN_PROPERTIES | opschain docs cli/step-set-property |
step remove-property | $OPSCHAIN_PROPERTIES | opschain docs cli/step-remove-property |
step emit-event | $OPSCHAIN_EVENTS | opschain docs cli/step-emit-event |
Each subcommand requires its environment variable to be set and fails with
$<VAR> is not set: opschain step subcommands only work inside a running OpsChain step (exit 2) when run anywhere else. The group itself takes no
flags beyond the globals.
See also
opschain learn 2.1— YAML actions, where step outputs are consumed.opschain learn 5.4— custom events.