steps:
  # The service was `beszel-althing` until 2026-09-21, when it gained a /kuma
  # route and the Beszel-specific name became a lie. Stop and remove the old
  # unit FIRST: both bind 10.100.10.50:8096, so they cannot run side by side.
  - name: Stop and remove the superseded beszel-althing unit
    sudo: true
    shell: >-
      systemctl disable --now beszel-althing.service 2>/dev/null || true;
      rm -f /etc/systemd/system/beszel-althing.service;
      rm -rf /opt/beszel-althing;
      systemctl daemon-reload
  - name: Install fleet alert bridge
    sudo: true
    upload:
      src: services/althing-alert-bridge/bridge.py
      dest: /opt/althing-alert-bridge/bridge.py
      mode: '0644'
  - name: Install fleet alert bridge unit
    sudo: true
    upload:
      src: services/althing-alert-bridge/althing-alert-bridge.service
      dest: /etc/systemd/system/althing-alert-bridge.service
      mode: '0644'
  - name: Start fleet alert bridge
    sudo: true
    shell: systemctl daemon-reload && systemctl enable althing-alert-bridge.service && systemctl restart althing-alert-bridge.service
verify:
  - name: Verify bridge process and BOTH routes are advertised
    shell: >-
      systemctl is-active althing-alert-bridge.service &&
      curl --retry 5 --retry-connrefused --retry-delay 1 -fsS http://10.100.10.50:8096/healthz | grep -q '"/kuma"' &&
      curl -fsS http://10.100.10.50:8096/healthz | grep -q '"/beszel"'
    changed_when: 'false'