mirror of
https://github.com/kevinveenbirkenbach/computer-playbook.git
synced 2025-10-09 18:28:10 +02:00
- Added MODE_BACKUP to trigger backup before the rest of the deployment - sys-ctl-bkp-docker-2-loc: force linear sync and force flush when MODE_BACKUP is true - Unified name resolution via system_service_name across handlers and tasks - Introduced system_service_force_linear_sync and system_service_force_flush (rename from system_force_flush) - Drive async/poll via system_service_async/system_service_poll using omit when disabled - Propagated per-role overrides (cleanup, repair, cert tasks) for clarity and safety - Minor formatting and consistency cleanups Why: Ensure the backup runs before the deployment routine to safeguard data integrity. Refs: Conversation https://chatgpt.com/share/68de4c41-b6e4-800f-85cd-ce6949097b5e Signed-off-by: Kevin Veen-Birkenbach <kevin@veen.world>
Cleanup Failed Backups
This role installs and runs the cleanback CLI to validate and delete failed Docker backups under /Backups/*/backup-docker-to-local
.
Validation is performed via dirval
; failures can be removed automatically in a non-interactive service execution.
Behavior
- Installs
cleanback
viapkgmgr
. - Runs
cleanback
(main.py
) as a systemd oneshot service. - Executes
--all
with--yes
so failing directories are deleted automatically. - No defaults for runtime knobs:
CLEANBACK_TIMEOUT_SECONDS
(required)SYS_SCHEDULE_CLEANUP_FAILED_BACKUPS
(required)
- Workers (
CLEANUP_FAILED_BACKUPS_WORKERS
) are derived from Ansible facts only (no arbitrary defaults). Facts must be gathered.