Validate deployment health across targets
audit-deploy-configsworkflowsetup L3★0
overthinkos/overthink ↗What it does
Audit deployment configs via read-only verification passes
Best for
Validating deployment configuration correctness and health before release without risking mutation of running systems.
Inputs
- · optional: array of target names (images/deploys) to audit
- · charly.yml / box.yml / deploy.yml config files
Outputs
- · validation report (ok, warnings, errors)
- · per-target health verdict (healthy | DEGRADED | NOT-RUNNING | CHECKS-FAILED | NOT-BUILT)
- · failing checks list with verbatim output
Requires
- · charly CLI (box validate, eval box, eval live, status)
- · bash shell
Preconditions
- · charly CLI installed and in PATH
- · box.yml / charly.yml files present
- · Built images exist locally if auditing built status
- · Current deploy accessible if auditing live status
Failure modes
- · charly box validate returns errors → blocks audit (no fallback)
- · Built image not found locally → target marked NOT-BUILT (non-fatal)
- · Deploy not currently running → target marked NOT-RUNNING (non-fatal)
- · Health probe timeout → skipped (non-fatal)
Trust signals
- · Read-only design: never builds, deploys, rebuilds, or tears down
- · Three independent probe types (box validate, box eval, live eval)
- · Verbatim failing check output surfaced (never hidden)
- · Schema validation enforces all returned fields (ok, warnings, errors, health verdict)