── CLI REFERENCE ──
exo validate
Validate the .exo.yaml config and optionally run a Trivy security scan on the generated Dockerfile.
## Synopsis
bash
exo validate [--security]## Description
Without flags, reads .exo.yaml and checks all field values against the set of allowed options. Reports errors for invalid languages, providers, CI platforms, monitoring options, or database types.
With --security, additionally invokes Trivy (if installed) to scan Dockerfile for known CVEs, outdated base images, and misconfiguration issues.
## Flags
| Flag | Description |
|---|---|
--security | Run Trivy security scan on Dockerfile after config validation |
## Validation Rules
| Field | Valid Values |
|---|---|
name | Non-empty string |
language | go, node, python, java, rust |
provider | aws, gcp, azure, none |
ci | github-actions, gitlab-ci, none |
monitoring | prometheus, none |
database | postgres, mysql, mongo, redis, none |
## Examples
Config validation only
bash
$ exo validateValidating .exo.yaml... ✓ name: my-service ✓ language: go ✓ provider: aws ✓ ci: github-actions ✓ monitoring: prometheus ✓ database: postgresConfiguration is valid.With Trivy security scan
bash
$ exo validate --securityValidating .exo.yaml... ✓ validRunning Trivy security scan on Dockerfile... 2024-01-15T10:23:45Z INFO Scanning Dockerfile... Dockerfile (dockerfile) ======================= Tests: 24 (SUCCESSES: 22, FAILURES: 2, EXCEPTIONS: 0) FAILURES: 2 (HIGH: 1, MEDIUM: 1) HIGH: Specify a tag in the FROM statement MEDIUM: Last USER command is rootWhen Trivy is not installed
bash
$ exo validate --securityValidating .exo.yaml... ✓ valid[warn] trivy not found in PATH — skipping security scan. Install: https://github.com/aquasecurity/trivy