mirror of
https://github.com/kevinveenbirkenbach/computer-playbook.git
synced 2026-11-06 10:59:59 +00:00
kevinveenbirkenbachandClaude Opus 5
a46348b6cf
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>
14 lines
324 B
YAML
14 lines
324 B
YAML
---
|
||
- name: "🧩 load docker, db and proxy for {{ application_id }}"
|
||
include_role:
|
||
name: sys-stk-full
|
||
vars:
|
||
compose_handlers_flush: false
|
||
|
||
- name: ➕ add config.exs
|
||
stack_host_template:
|
||
src: "config.exs.j2"
|
||
dest: "{{ mobilizon_host_conf_exs_file }}"
|
||
notify: compose-up
|
||
when: IS_STACK_HOST | bool
|