validate
Check a configuration file before you run it.validate parses the manifest,
resolves the dependency graph, and — when something is wrong — tells you the
exact line, why it’s an error, and how to fix it.
0:
Options
| Short | Long | Description |
|---|---|---|
-c | --config | Path to the configuration file (defaults to systemg.yaml) |
- | --format | Emit machine-readable output (json) |
- | --no-color | Disable ANSI colors |
- | --plain | Agent-friendly output (also disables color) |
What it checks
- Schema — a supported
version, aservicesmap, and acommandper service. - Syntax — YAML that parses, with a caret pointing at the offending token.
- Health checks — every
deployment.health_checkhas aurlor acommand. - Dependencies —
depends_onreferences exist and form no cycle. - Project id — a valid, non-empty
project.id. - Environment —
${VAR}interpolations resolve from the environment or env file.
Exit codes
| Code | Meaning |
|---|---|
0 | Configuration is valid |
1 | Configuration has one or more problems |
JSON output
Use--format json for CI gates and tooling. Each diagnostic carries its
location, category, message, and remediation:
Example
Gate a deploy on a valid manifest:See also
- Configuration - Full manifest reference
start- Launch a validated manifeststatus- Check services once they’re running

