personal_infra/ansible
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
..
group_vars/all uptime-kuma: add uptime_kuma_enabled flag and make monitoring blocks inert 2026-09-11 22:43:55 +02:00
host_vars/nodito vars 2026-09-11 22:17:13 +02:00
infra uptime-kuma: remove credentials from the vaults 2026-09-11 22:43:15 +02:00
services uptime-kuma: add uptime_kuma_enabled flag and make monitoring blocks inert 2026-09-11 22:43:55 +02:00
ansible.cfg now using password 2026-09-11 17:59:41 +02:00
infra_secrets.yml uptime-kuma: remove credentials from the vaults 2026-09-11 22:43:15 +02:00
infra_secrets.yml.example uptime-kuma: remove credentials from the vaults 2026-09-11 22:43:15 +02:00
infra_vars.yml uptime-kuma: add uptime_kuma_enabled flag and make monitoring blocks inert 2026-09-11 22:43:55 +02:00
inventory.ini new groups, stop using all 2026-09-11 21:51:50 +02:00
requirements.yml lots of stuff man 2025-11-06 23:09:44 +01:00
services_config.yml stuffy stuff 2026-08-08 12:00:27 +02:00