Step Configuration
Steps combine a type with the fields that configure it. See common fields for the complete overview and the step type catalog for type-specific parameters.
| Configure | Reference |
|---|---|
| Conditions and cleanup | Conditional execution, cleanup steps, continue |
| Inputs and freshness | inputs, artifacts, preconditions |
| Execution environment | env, working_directory, identity, container |
| Failure recovery | retry |
| Results and display | outputs, output, show |
| Terminal interaction | tty, interactive |
Execution Context
Workflows and custom commands use structured step objects. Workflow command steps default to type: atmos; custom-command string shorthand runs shell commands. Use an explicit type in reusable examples.
Lifecycle hooks use a hook envelope: kind: step places a single step's parameters under with, while kind: steps places an ordered list there. Hook-level conditions, failure policy, retry boundaries, and template context are documented by the hook reference. A shared step type does not make every workflow execution field a hook-envelope field.
