I tried with a "when" statement on the handler definition (with a variable defined by me) but id didn't seem to work either, the handler is executed anyway, and the AMI creation fails for that.
El sábado, 6 de junio de 2015, 12:14:50 (UTC+2), Dan C escribió: > > I would like the same feature. > > I don't know if there is another way to do what I am trying to do. > My case of use would be to be able to use the same roles/playbooks to > mantain the configuration along all my servers and for the AMI creation. In > the case of an ami creation I don't want the services to start o restart, I > don't want to execute a restart when copying the config file. > > Is there any other way to do taht without skiping handlers? > > El jueves, 5 de marzo de 2015, 9:02:17 (UTC+1), Ivaylo Bratoev escribió: >> >> So there is not way to skip a handler through ansible-playbook... >> Consider that a feature request ;) >> >> On Monday, February 23, 2015 at 4:43:42 PM UTC+2, Brian Coca wrote: >>> >>> Handlers ignore tags, they only run when notified and always run when >>> notified >>> -- >>> Brian Coca >>> >> -- 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/3f9e89df-4e70-479e-8dfe-69a68cc00428%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
