mirror of
https://github.com/kevinveenbirkenbach/computer-playbook.git
synced 2026-11-06 19:01:54 +00:00
A handler name was doing two jobs at once: the line an operator reads in the
play output, and the identifier a `notify:` binds to. The two pull in opposite
directions -- the log wants "restart the SSH service, with diagnostics", the
binding wants a token that survives quoting, YAML flow style and a shell
round-trip -- and a name that changes for readability silently changes which
handler runs.
Every handler that a notify reached by name now carries a `listen:` with that
exact wording, so the binding is explicit before anything is renamed. The
topics themselves become identifiers: `compose up` reads `compose-up`,
`Restart NFS ganesha` reads `restart-nfs-ganesha`, 22 of them across both
sides of every notify. Where the topic is assembled at runtime, both branches
moved together: the conditional in sys-service carries two literals, and the
LDAP renderer interpolates `import-{{ folder }}-ldif-files`, which is what
makes those handlers reachable at all.
Freed from the binding, the names take the emoji prefix every other task line
already has.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
21 lines
720 B
YAML
21 lines
720 B
YAML
---
|
|
- name: 🔄 Trigger container manager restart non-blocking (hard timeout)
|
|
ansible.builtin.command: "timeout 10s systemctl restart docker.service --no-block"
|
|
register: restart_cmd
|
|
changed_when: true
|
|
failed_when: false
|
|
|
|
- name: ⏳ Wait up to 60s for docker.service to become active
|
|
ansible.builtin.command: "systemctl is-active docker.service"
|
|
register: docker_active
|
|
changed_when: false
|
|
retries: 60
|
|
delay: 1
|
|
until: docker_active.stdout.strip() == "active"
|
|
|
|
- name: ✅ Assert docker is active
|
|
ansible.builtin.assert:
|
|
that:
|
|
- docker_active.stdout.strip() == "active"
|
|
fail_msg: "docker.service did not become active within 60s (is-active={{ docker_active.stdout | default('') }})"
|