Hi,
Okay, thanks, that does help a little because in the playbook what I
can do is:
- hosts: some_group
roles:
- {
role: app,
}
- hosts: all
roles:
- {
role: configure,
}
handlers:
- include: roles/app/handlers/main.yml
meaning that the
I don't know if this is the best way, but I have a role consisting of just
handlers that is included as a metal dependency by other roles. This helps
me get around having multiple handlers that do the same thing and also
allows me to enforce the order that they are run (eg, I have a reboot
handler
Hello,
Say I have a playbook a bit like this:
- hosts: some_group
roles:
- {
role: app,
}
- hosts: all
roles:
- {
role: configure,
}
That second role "configure" does something that will require the
apache2 service on hosts in some_group to be
