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
| Flag | Type | Default | Meaning |
|---|---|---|---|
--set | text | — | 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
| Code | Meaning |
|---|---|
| 0 | Success |
| 1 | Processing failed |
| 2 | Usage or parameter error |
| 3 | Input missing or unreadable |
| 4 | Unsupported format or codec |
| 8 | Cancelled |
| 70 | Internal error (bug) |
Common mistakes
- Forgetting that outputs are never overwritten: pass
--overwriteor a new-opath 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": {}}