From d19553f587cb105b7c7f2d3d83c59c876ec59ebe Mon Sep 17 00:00:00 2001 From: counterweight Date: Mon, 19 Oct 2026 22:10:25 +0200 Subject: [PATCH] gatus: turn Signal alerting back on signal-api is relinked (test message delivered; the vault's signal_number matches the linked account). No endpoint overrides `enabled`, so this one key still switches every alert in the estate. Co-Authored-By: Claude Opus 5.5 (1M context) --- ansible/services/gatus/deploy_gatus_playbook.yml | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/ansible/services/gatus/deploy_gatus_playbook.yml b/ansible/services/gatus/deploy_gatus_playbook.yml index 94cd325..26b8c8e 100644 --- a/ansible/services/gatus/deploy_gatus_playbook.yml +++ b/ansible/services/gatus/deploy_gatus_playbook.yml @@ -22,9 +22,10 @@ number: "{{ signal_number }}" recipients: "{{ signal_recipients }}" default-alert: - # ── SIGNAL ALERTING IS OFF ────────────────────────────────────── - # Flip to true to turn the phone back on. Nothing else needs to - # change: this ONE key disables every Signal alert in the estate. + # ── SIGNAL ALERTING IS ON ─────────────────────────────────────── + # Flip to false to silence the phone. Nothing else needs to + # change: this ONE key switches every Signal alert in the estate. + # (Re-enabled 2026-10-18 after relinking signal-api post-rebuild.) # # It works because `enabled` is the only alert field no registration # playbook sets. Gatus merges a provider's default-alert into each @@ -36,7 +37,7 @@ # Deliberately NOT done by deleting the `signal:` provider block: # that would strand ~90 endpoints referencing a provider that no # longer exists, and lose the number and recipients. - enabled: false + enabled: true # Overridden per group by the registration playbooks; these are the # values that apply if a caller sets nothing. failure-threshold: 1