Thank you. However, our playbooks don't use roles. For our deployment orchestration, it doesn't seem necessary, or at least it works well without them.
Can anyone speak to how that variable is getting set as the playbook executes the second include? Will this absolutely not work without roles? On Friday, July 24, 2015 at 7:16:29 AM UTC-7, Timothy Appnel wrote: > > If I am following what behavior you are looking for (what you describe is > how includes are intended to work) your playbook includes should be > implemented as a role and then called with parameters. See if the added > namespacing protections roles have, but includes does not kicks in. > > <tim/> > -- 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/6d21c77a-7b76-4e09-9d62-dde41ea05dc7%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
