Thanks Brian! I suspected it was a "feature" of ansible. The only workaround then, would to be to add something in the name of every individual task or go back to a single playbook?
On Friday, April 24, 2015 at 12:01:22 PM UTC-5, Brian Coca wrote: > > You added a name to an include and include itself disappears and is > replaced by the included tasks during playbook compilation, these > tasks have names already so even if it were inheritable (it isn't) > they would be overriding it. > > -- > 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 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/9c49b0d5-77e3-41c1-8415-9db56f852707%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
