coulomb/railiance-cluster
2
0
Fork 0
Code Issues Pull Requests Actions 2 Projects Releases Wiki Activity

Add Railiance promote rollback tooling
Some checks failed
railiance-tests / smoke (push) Has been cancelled
Details

Browse Source
This commit is contained in:
Bernd Worsch
2026-06-27 17:01:11 +02:00
parent 6d862e68be
commit 87bd73b26b
9 changed files with 484 additions and 15 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
docs/app-toml-contract.md
View File

@@ -186,17 +186,17 @@ records only the route, target object, and pass/fail state.
## Command Semantics
Commands in `app.toml` are declarations for Railiance tooling. Stage 1 and
Stage 2 commands now have local CLI support; Stage 3 commands may still point
to existing scripts or runbook commands until T07 lands.
Commands in `app.toml` are declarations for Railiance tooling. Stage 1, Stage
2, and Stage 3 commands now have local CLI support; workload scripts may still
wrap them for service-specific checks.
Expected mapping:
- Stage 1 commands are consumed by `bin/railiance run <overlay-dir>`.
- Stage 2 commands are consumed by `bin/railiance deploy --stage 2 <overlay-dir>`
and `bin/railiance observe --stage 2 <overlay-dir>`.
- Stage 3 commands are consumed by future `bin/railiance promote <overlay-dir>`
and `bin/railiance rollback <overlay-dir>` commands.
- Stage 3 commands are consumed by `bin/railiance promote <overlay-dir>` and
`bin/railiance rollback <overlay-dir>`.
Tooling must emit machine-readable results with workload identity, candidate
revision, checks run, pass/fail status, non-secret evidence, rollback target,