On Fri, Jun 18, 2021 at 5:26 PM Wei-Yen Tan <[email protected]> wrote: > > That's what handlers are for. If the app has not changed the app will not be > reloaded >
Right. The app consists of multiple artifacts, that are updated independently. There are also several services that depend on multiple artifacts. Consider: service A and service B depend on artifact1 service A depends on artifact 2 service C depends on artifact1 and artifact3 By restarting each service from a handler, that is notified by per-artifact update task, this dependency structure is re-implemented in Ansible. That's complexity and fragility. Application should be able to change its dependency structure, for example, so that service C now depends on artifacts1, 2 and 3, and ansible playbook should not have to change. Or at least fail in an obvious way. Instead, with handler implementation, service C will not be restarted when artifact 2 is updated, and will continue running its older version. -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/CAGB%3D%3DuJ8pDPCs0h%3DY038i5DgEE%2BvPQgEehxUCNLUJaZKaGeHRw%40mail.gmail.com.
