Johannes Kastl wrote: > On 12.02.17 18:47 Michael Ströder wrote: >> But then a role has to know the handler names in the other role >> which somewhats contradicts the concept of modular design. > > AFAIK the role design is built so you could reuse roles in more than > one place. E.g. create a role that just installs nginx, and is set as > a dependency for the roles creating a webserver with nginx, a load > balancer with nginx, etc. This way you would have to put together the > installation steps in only one role, not in multiple roles.
Yes I know. But the world is a bit more complicated. Two different roles could require and thus update the same OS packages (in my case Python modules). Completely *different* services managed in different roles would have to be restarted. > The solution to your notify dilemma maybe a delegate_to in the > handler. Or duplicating the handler in your role. > > Maybe we could help better if we knew what problem you are solving, or > what applications need your to call your handler in another role... See also my other recent posting. Ciao, Michael. -- You received this message because you are subscribed to the Google Groups "Ansible Project" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/eda59d0f-d771-65ad-ab4b-8308771d1674%40stroeder.com. For more options, visit https://groups.google.com/d/optout.
smime.p7s
Description: S/MIME Cryptographic Signature
