Brian, I find the current usage of "tags" when calling a role via "roles:" or "include_role/import_role" is counter intuitive. The reason we tag tasks in our playbooks is for the purpose of filtering which we would expect to be the case in the above mentioned scenarios as well. But it is not, and that is major draw back in making reusable (DRY) code.
I constantly find my self in need to execute just a part of some role tasks, lets say the ones tagged with "install" but skip the ones tagged with "configure" lets say. This is exactly what we get by passing "--tags" or "--skip-tags" on the command line so why not make this consistent everywhere? On Saturday, February 2, 2019 at 6:07:44 AM UTC+11, Brian Coca wrote: > > No, it is not possible > > ---------- > 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/1b7ba93b-4cc5-48f1-a264-6346269ec5bf%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
