Conversation

Notices

1. Embed this notice
   Andreas Scherbaum (ascherbaum@mastodon.social)'s status on Thursday, 07-Nov-2024 08:16:25 JST Andreas Scherbaum

   in reply to

   • zhenech

   @zhenech I don't get why the handler aren't forced by #Ansible at the end of the Role, logically that makes sense because the concept "encapsulated tasks in a Role" ends at the end of the Role.

   And I have "meta: flush_handlers" at the end of every role ...

   • Embed this notice
     zhenech (zhenech@chaos.social)'s status on Thursday, 07-Nov-2024 08:16:27 JST zhenech

     Days since the fact that Ansible runs handlers at the end of the play and not at the end of the role that triggered them broke shit for me: 0️⃣

   • Embed this notice
     Andreas Scherbaum (ascherbaum@mastodon.social)'s status on Thursday, 07-Nov-2024 09:45:58 JST Andreas Scherbaum

     • zhenech
     • Mauricio Teixeira 🇧🇷🇺🇲

     @badnetmask @zhenech You know, documented != useful.

     When I create a role, the intention is to wrap a certain piece of action/state in this role. Once the role execution is finished, there's nothing which prevents #Ansible from running all notified handlers.

     I get the argument about not running handlers multiple time, the counter argument is that a role which is executed later might find a situation where the service is not yet in the desired state.