megamono verify
Syntax, options, and usage for the verify command.
Check that dependencies, built code, and container configuration can work outside your development checkout.
Start with dependency checks
bash
megamono verify dependenciesBuild your application before runtime verification. Use container verification to review Docker build inputs and, when explicitly requested, smoke-test a container build.
Command options
Use the help below for exact syntax and options. You can also run megamono verify --help in your terminal.
text
Usage: megamono verify runtime <project> [options]
megamono verify artifacts [--artifact-manifest=<file>] [--json]
megamono verify dependencies [options]
megamono verify container [options]
Examples:
megamono verify runtime api --outputPath=dist/apps/api
megamono verify runtime api --webpackEvidence=.megamono/api-webpack-evidence.json
megamono verify dependencies --checkActive=false
megamono verify container --dockerfile=apps/api/Dockerfile
megamono verify container --dockerfile=apps/api/Dockerfile --smoke
Qualification commands check .megamono/qualification-artifacts.json when present.
Use --artifact-manifest=<file> to select a different explicit baseline. Drift or
unverifiable selections stop verification; no dependencies are installed.
Verification is read-only unless container --smoke is explicitly requested.