DC-038: claim for Hermes
This commit is contained in:
+2
-2
@@ -190,8 +190,8 @@
|
|||||||
## P2 — Polish & DX
|
## P2 — Polish & DX
|
||||||
|
|
||||||
### DC-038: Backup trigger.json + result.json in dashcaddy-update.sh — enable one-command rollback
|
### DC-038: Backup trigger.json + result.json in dashcaddy-update.sh — enable one-command rollback
|
||||||
- **status:** todo
|
- **status:** in-progress
|
||||||
- **owner:** unclaimed
|
- **owner:** hermes
|
||||||
- **details:** During the DC-033 fix, recovering from the failed v1.14.4 update required manually mv'ing `trigger.json.processing` back to `trigger.json`, manually running `start.sh`, etc. — because the backup mechanism in `dashcaddy-update.sh` (lines 318-327) only backs up code + data, not the trigger/result state. Fix: in the `backup_data_dir` function (or new `backup_update_state` function), also copy `${UPDATES_DIR}/trigger.json` and `${UPDATES_DIR}/result.json` into the versioned backup directory so rollback tooling can restore them. Effort: ~15 min.
|
- **details:** During the DC-033 fix, recovering from the failed v1.14.4 update required manually mv'ing `trigger.json.processing` back to `trigger.json`, manually running `start.sh`, etc. — because the backup mechanism in `dashcaddy-update.sh` (lines 318-327) only backs up code + data, not the trigger/result state. Fix: in the `backup_data_dir` function (or new `backup_update_state` function), also copy `${UPDATES_DIR}/trigger.json` and `${UPDATES_DIR}/result.json` into the versioned backup directory so rollback tooling can restore them. Effort: ~15 min.
|
||||||
- **impact:** Faster incident recovery. Currently takes 5-10 manual steps to roll back a failed update; would take 1.
|
- **impact:** Faster incident recovery. Currently takes 5-10 manual steps to roll back a failed update; would take 1.
|
||||||
|
|
||||||
|
|||||||
Reference in New Issue
Block a user