On Tue, Mar 4, 2014 at 11:51 AM, Aaron Hunter <aaron.hunt...@gmail.com>wrote:
> >> A chinstrap role that James mentions could work but it has no way of > knowing that a change has taken place (ie., a new snippet was added, > changed, or removed). At least none that I know of. The alternative is > simply to make the chinstrap role at the end always fire which would work > but you then lose idempotency. > With a chinstrap role, if there are no changes to the snippets there is no change in the result of the assemble, thus no handler would be fired. So it is indeed idempotent. It is true that the role would always have to run. Many people use a "common" role that runs before other roles, think of this as the antithesis. - James -- 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 ansible-project+unsubscr...@googlegroups.com. To post to this group, send email to ansible-project@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/CAJvmrNORjuR-d8C8guPLBuNT%3D9d8JpGzknzeX7J4bLV_uiU5HQ%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
