counterweight 2dabc6ad62 uptime-kuma: add uptime_kuma_enabled flag and make monitoring blocks inert ... Removing the credentials would otherwise break these playbooks mid-deploy: they template uptime_kuma_password with no assert to stop them first. 100 tasks are now guarded by uptime_kuma_enabled (false), so deployments run normally and the monitoring sections skip. A further 28 tasks were already self-guarding on monitor_setup/push_url being defined; verified that a skipped task's registered variable makes those skip cleanly rather than error. The blocks are kept on purpose — the health-check logic is the durable part and should be rewired to whatever replaces Uptime Kuma. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>		2026-09-11 22:43:55 +02:00
..
deploy_lnbits_playbook.yml	uptime-kuma: add uptime_kuma_enabled flag and make monitoring blocks inert	2026-09-11 22:43:55 +02:00
lnbits_vars.yml	vars: derive remote_host_name from role groups instead of hostnames	2026-09-11 22:00:43 +02:00
setup_backup_lnbits_to_lapy.yml	backups: target control group instead of lapy	2026-09-11 21:56:24 +02:00