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>
18 lines
496 B
YAML
18 lines
496 B
YAML
---
|
|
- name: "🚀 Deploy '{{ MATOMO_BOOTSTRAP_ENV_FILE }}'"
|
|
stack_host_template:
|
|
src: "templates/bootstrap.env.j2"
|
|
dest: "{{ MATOMO_BOOTSTRAP_ENV_FILE }}"
|
|
mode: "0640"
|
|
force: true
|
|
notify: compose-up
|
|
|
|
- name: 🚿 flush docker service
|
|
meta: flush_handlers
|
|
|
|
- name: "🔍 Matomo install | Resolve hosting node + local container ID"
|
|
include_tasks: utils/resolve/host_cid.yml
|
|
|
|
- name: "▶️ Matomo install | Run downstream install path"
|
|
include_tasks: 03_install_path.yml
|