Three files existed only as second copies of things group_vars/all already
auto-loads, and 34 playbooks named them in vars_files: - which outranks
group_vars, so the copies won. The day someone edited one and not the other,
those plays would silently keep the stale value. infra_vars.yml was already
drifting: group_vars/all/main.yml had grown age_backup_recipient and
backup_pull_public_key that it lacked.
infra_vars.yml - a strict subset of group_vars/all/main.yml
infra_secrets.yml - decrypts byte-identical to group_vars/all/vault.yml
infra_secrets.yml.example - documented Uptime Kuma credentials as the reason
the file exists, which stopped being true
Deleted, along with 62 vars_files entries across 34 playbooks (12 of which
named ../../group_vars/all/main.yml directly - same defect, a vars_files entry
duplicating an auto-loaded file at higher precedence than the file itself).
Checked before touching anything: infra_secrets.yml was listed LAST in 10 plays,
after services_config.yml, so removal would flip precedence if the two shared a
key. They share none, and neither does services_config.yml with
group_vars/all/main.yml, so the removal is provably inert.
services_config.yml was the last one standing. It held four unrelated things:
caddy_sites_dir - an identical copy of roles/caddy_site/defaults/.
Deleted; the role default is now the only one.
*.tailscale_hostname (x3) - a THIRD copy of each box's identity, which
inventory.ini already holds as ansible_host.
Deleted. Edge plays now read
hostvars['<host>'].ansible_host - verified an
edge play resolves that with nothing loaded and
the other host in no play. Three copies of one
name is how bitcoin_rpc_host ended up labelled
"knots_box" while pointing at fulcrum-box.
subdomains, ntfy topic, - genuinely global: their readers span managed,
headscale namespace monitoring, vpn_control and edge, so no single
group covers them. Moved to group_vars/all/main.yml
where they auto-load. The ntfy_topic and
headscale_namespace indirection through
service_settings collapses to the global name.
the four cross-host ports - the only entries with a real justification.
Left in place; they move in the next commit.
Also dead, all Uptime Kuma residue or duplication:
phoenixd_monitor_name, forgejo_runner healthcheck_timeout_seconds/retries,
fulcrum_tailscale_hostname, and bitcoin_knots_version - the last being a
v-prefixed copy of bitcoin_knots_version_short that nothing read, two
hand-maintained copies of one version string.
Corrected a false comment: services_config.yml claimed the uptime_kuma subdomain
"no longer resolves to anything". It resolves to 164.92.239.72 and answers HTTP
302, and 11 playbooks still template it. Same wrong premise as PLAN_3.
Verification: all 37 playbooks' --list-tasks output is byte-identical before and
after. A probe resolving all 22 values services_config.yml used to supply returns
21 identical and one intended deletion (caddy_sites_dir, now role-only - confirmed
the role still resolves it: "Ensure Caddy sites-enabled directory exists" comes
back ok against the real path). memos check-diff identical before and after.
Syntax passes on every playbook.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
165 lines
6.4 KiB
YAML
165 lines
6.4 KiB
YAML
# ═════════════════════════════════════════════════════════════════════════════
|
|
# DEPRECATED — Uptime Kuma was decommissioned on 2026-09-11.
|
|
#
|
|
# This play WILL FAIL if run as-is, and that is deliberate: uptime_kuma_username
|
|
# and uptime_kuma_password were removed from the vault, so the "Validate Uptime
|
|
# Kuma configuration" assert stops it before anything is installed or changed.
|
|
#
|
|
# It is kept because the CHECK LOGIC is the durable part — what gets measured,
|
|
# the thresholds, and the systemd timer plumbing. When something replaces Uptime
|
|
# Kuma, only the push transport needs rewriting; the rest still applies.
|
|
#
|
|
# What was being monitored: archive/uptime_kuma/MONITORS.md
|
|
# ═════════════════════════════════════════════════════════════════════════════
|
|
- name: Setup ntfy as Uptime Kuma Notification Channel
|
|
hosts: monitoring
|
|
become: no
|
|
vars_files:
|
|
- ../../services_config.yml
|
|
- ./ntfy_vars.yml
|
|
|
|
vars:
|
|
ntfy_subdomain: "{{ subdomains.ntfy }}"
|
|
uptime_kuma_subdomain: "{{ subdomains.uptime_kuma }}"
|
|
ntfy_domain: "{{ ntfy_subdomain }}.{{ root_domain }}"
|
|
ntfy_server_url: "https://{{ ntfy_domain }}"
|
|
ntfy_priority: 4 # 1=min, 2=low, 3=default, 4=high, 5=max
|
|
uptime_kuma_api_url: "https://{{ uptime_kuma_subdomain }}.{{ root_domain }}"
|
|
|
|
tasks:
|
|
- name: Validate Uptime Kuma configuration
|
|
assert:
|
|
that:
|
|
- uptime_kuma_api_url is defined
|
|
- uptime_kuma_api_url != ""
|
|
- uptime_kuma_username is defined
|
|
- uptime_kuma_username != ""
|
|
- uptime_kuma_password is defined
|
|
- uptime_kuma_password != ""
|
|
fail_msg: "uptime_kuma_api_url, uptime_kuma_username and uptime_kuma_password must be set"
|
|
|
|
- name: Validate ntfy configuration
|
|
assert:
|
|
that:
|
|
- ntfy_domain is defined
|
|
- ntfy_domain != ""
|
|
- ntfy_topic is defined
|
|
- ntfy_topic != ""
|
|
- ntfy_username is defined
|
|
- ntfy_username != ""
|
|
- ntfy_password is defined
|
|
- ntfy_password != ""
|
|
fail_msg: "ntfy_domain, ntfy_topic, ntfy_username and ntfy_password must be set"
|
|
|
|
- name: Create Uptime Kuma ntfy notification setup script
|
|
copy:
|
|
dest: /tmp/setup_uptime_kuma_ntfy_notification.py
|
|
content: |
|
|
#!/usr/bin/env python3
|
|
import sys
|
|
import json
|
|
from uptime_kuma_api import UptimeKumaApi
|
|
|
|
def main():
|
|
api_url = sys.argv[1]
|
|
username = sys.argv[2]
|
|
password = sys.argv[3]
|
|
notification_name = sys.argv[4]
|
|
ntfy_server_url = sys.argv[5]
|
|
ntfy_topic = sys.argv[6]
|
|
ntfy_username = sys.argv[7]
|
|
ntfy_password = sys.argv[8]
|
|
ntfy_priority = int(sys.argv[9])
|
|
|
|
api = UptimeKumaApi(api_url, timeout=60, wait_events=2.0)
|
|
api.login(username, password)
|
|
|
|
# Get all notifications
|
|
notifications = api.get_notifications()
|
|
|
|
# Find existing ntfy notification by name
|
|
existing_notification = next((n for n in notifications if n.get('name') == notification_name), None)
|
|
|
|
notification_data = {
|
|
'name': notification_name,
|
|
'type': 'ntfy',
|
|
'isDefault': True, # Apply to all monitors by default
|
|
'applyExisting': True, # Apply to existing monitors
|
|
'ntfyserverurl': ntfy_server_url,
|
|
'ntfytopic': ntfy_topic,
|
|
'ntfyusername': ntfy_username,
|
|
'ntfypassword': ntfy_password,
|
|
'ntfyPriority': ntfy_priority
|
|
}
|
|
|
|
if existing_notification:
|
|
notification = api.edit_notification(existing_notification['id'], **notification_data)
|
|
action = "updated"
|
|
else:
|
|
notification = api.add_notification(**notification_data)
|
|
action = "created"
|
|
|
|
# Output result as JSON
|
|
result = {
|
|
'notification_id': notification['id'],
|
|
'notification_name': notification_name,
|
|
'ntfy_server': ntfy_server_url,
|
|
'ntfy_topic': ntfy_topic,
|
|
'action': action
|
|
}
|
|
print(json.dumps(result))
|
|
|
|
api.disconnect()
|
|
|
|
if __name__ == '__main__':
|
|
main()
|
|
mode: '0755'
|
|
delegate_to: localhost
|
|
become: no
|
|
|
|
- name: Run Uptime Kuma ntfy notification setup script
|
|
command: >
|
|
{{ ansible_playbook_python }}
|
|
/tmp/setup_uptime_kuma_ntfy_notification.py
|
|
"{{ uptime_kuma_api_url }}"
|
|
"{{ uptime_kuma_username }}"
|
|
"{{ uptime_kuma_password }}"
|
|
"ntfy ({{ ntfy_topic }})"
|
|
"{{ ntfy_server_url }}"
|
|
"{{ ntfy_topic }}"
|
|
"{{ ntfy_username }}"
|
|
"{{ ntfy_password }}"
|
|
"{{ ntfy_priority }}"
|
|
register: notification_setup_result
|
|
delegate_to: localhost
|
|
become: no
|
|
changed_when: false
|
|
|
|
- name: Parse notification setup result
|
|
set_fact:
|
|
notification_info_parsed: "{{ notification_setup_result.stdout | from_json }}"
|
|
|
|
- name: Display notification information
|
|
debug:
|
|
msg: |
|
|
✓ ntfy notification channel {{ notification_info_parsed.action }} successfully!
|
|
|
|
Notification Name: ntfy ({{ ntfy_topic }})
|
|
ntfy Server: {{ ntfy_server_url }}
|
|
ntfy Topic: {{ ntfy_topic }}
|
|
Priority: {{ ntfy_priority }} (4=high)
|
|
Default for all monitors: Yes
|
|
Applied to existing monitors: Yes
|
|
|
|
All Uptime Kuma monitors will now send alerts to your ntfy server
|
|
on the "{{ ntfy_topic }}" topic.
|
|
|
|
You can subscribe to alerts at: {{ ntfy_server_url }}/{{ ntfy_topic }}
|
|
|
|
- name: Clean up temporary Uptime Kuma setup script
|
|
file:
|
|
path: /tmp/setup_uptime_kuma_ntfy_notification.py
|
|
state: absent
|
|
delegate_to: localhost
|
|
become: no
|
|
|