The four ports were the only entries in services_config.yml with a real
justification: each is read twice, by the role that deploys the service on its
own box AND by a socket-proxy or Caddy play that runs on the EDGE host and
publishes it. A role default is invisible to that second play.
But the shape was wrong in two ways. The file had to be named in vars_files: by
30 plays - opt-in configuration that someone will eventually forget - and five
role defaults silently interpolated service_settings.*, so bitcoin_knots,
fulcrum, datum_gateway and mempool were not self-contained: using any of them
without that one vars_file entry broke it.
Each port now lives in host_vars/<owning box>/main.yml:
host_vars/knots_box_local/main.yml bitcoin_p2p_port, datum_gateway_api_port,
datum_gateway_stratum_port
host_vars/fulcrum_box_local/main.yml fulcrum_ssl_port
host_vars/mempool_box_local/main.yml mempool_frontend_port
host_vars auto-loads and outranks role defaults, so the owning role picks the
value up with no vars_files at all, and the edge play reads the same single
definition as hostvars['<host>'].<name>. The role defaults keep the protocol
standard (8333, 50002, ...) so each role still works standalone, with the live
deployment's value in host_vars winning.
Also fixed a fourth copy of an inventory identity: the mempool Caddy play had
"mempool-box:{{ ... }}" hardcoded in the upstream. It now derives the host from
hostvars['mempool_box_local'].ansible_host, so inventory is the only place any
box's name is written down.
services_config.yml is deleted, with 25 more vars_files entries across 19
playbooks. Between this and the previous commit, 87 vars_files entries are gone
and every variable in the repo now comes from group_vars/all, host_vars,
inventory, a role default, or that service's own *_vars.yml.
Verification: an edge-host probe resolves all eight ports and hostnames to
byte-identical values to the ones services_config.yml used to supply. Each
owning host resolves its own port through host_vars. All 37 playbooks'
--list-tasks output is unchanged. The four edge plays that consume these values
all check-diff changed=0 - the socket-proxy and Caddy units on vipy are
byte-identical, which is the direct proof the rewiring landed on the same
values. fulcrum and datum-gateway check-diff exactly as before (ok=28/changed=1
and ok=15/changed=1, both the known timer re-arm).
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
164 lines
6.4 KiB
YAML
164 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:
|
|
- ./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
|
|
|