ferraus pipeline validate

Check a pipeline file without running it

Synopsis

ferraus pipeline validate <input> [options] [-o <output>]

What it does

Check a pipeline file without running it

Examples

Validate stage names, arguments, and references

ferraus pipeline validate job.yaml --json

Check a JSON pipeline file; exit code 2 means a stage or argument is wrong

ferraus pipeline validate job.json

Check that an override is valid before running it

ferraus pipeline validate job.yaml --set stages.master.args.lufs=-16LUFS

Options

FlagTypeDefaultMeaning
--settext—Override any field before validating Repeatable.

Global options

Every command also accepts the global options (-o, --json, --dry-run, --overwrite, --progress, ...). See Global options.

Exit codes

CodeMeaning
0Success
1Processing failed
2Usage or parameter error
3Input missing or unreadable
4Unsupported format or codec
8Cancelled
70Internal error (bug)

Common mistakes

  • Forgetting that outputs are never overwritten: pass --overwrite or a new -o path when re-running.

For models

  • MCP tool: ferraus_pipeline_validate
  • Schema: ferraus schema pipeline validate
  • Pipeline: { op: pipeline validate, args: { ... } } (flag names with _ instead of -)
  • fx stage: no
{"command": "pipeline validate", "defaults": {}}