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

11
workplans/RAIL-BS-WP-0006-staged-promotion-lifecycle.md
View File

@@ -224,7 +224,7 @@ generated overlays to declare the repeatable Stage 2 plan commands.
```task
id: RAIL-BS-WP-0006-T07
status: todo
status: done
priority: medium
state_hub_task_id: "476198f6-0049-4ac4-9593-6723c86c9602"
```
@@ -242,6 +242,15 @@ Expected output:
**Done when:** a representative app can move Stage 1 -> Stage 2 -> Stage 3 and
back through rollback using documented commands.
2026-06-27: Added `tools/cmd/railiance-stage3` and dispatcher entries for
`bin/railiance promote` and `bin/railiance rollback`. Both commands default to
non-mutating JSON plans, apply modes require approval evidence and Helm, and
rollback apply also requires a Helm revision for `helm-revision` strategy.
Added `docs/promote-rollback-onboarding.md` with the representative Stage 1 ->
Stage 2 -> Stage 3 -> rollback path and explicit human approval points for
critical workloads. Updated generated overlays to declare promote/rollback plan
commands.
## Dependencies
This workplan should be done before the Forgejo production cutover. It can run