expanso-edge validate

`expanso-edge validate`

Validate pipeline configs locally

Synopsis

Validate one or more pipeline configs offline, without contacting an orchestrator.

Input is read from the given FILE paths, or from stdin when no file is given or the path is "-". A file may contain multiple YAML documents separated by "---"; each is validated independently. Each document is auto-detected:

A bare pipeline config (top-level "input"/"output") is fully validated (config schema, mapping expressions, and component types).
A job spec (has a "config" block) is NOT validated as a job spec -- it is only parsed structurally to reach the pipeline config it carries. The spec just has to be well-formed YAML/JSON that parses as a job; its job-level fields are ignored. For a pipeline job the embedded config IS fully validated (a pipeline job with no config is an error).

This validates pipeline config syntax and structure only. It does NOT validate the job spec itself: job-level fields (name, type, selectors, rollout, restart policy) are not checked, and it does not run the orchestrator's submission validation or any server dry-run -- a config that passes here can still be rejected at submission.

expanso-edge validate [FILE...] [flags]

Examples

  # Validate a config file
  expanso-edge validate pipeline.yaml

  # Validate a piped config
  cat pipeline.yaml | expanso-edge validate -

  # Validate several files with JSON output
  expanso-edge validate a.yaml b.yaml --output json

Options

  -h, --help                 help for validate
  -o, --output {text|json}   Output format (default text)

Options inherited from parent commands

  -v, --verbose   Enable verbose logging