Actually I just observed that a separate bug report has been filed and is
still open about this exact issue in: "include_role : troubleshooting
passing variables #18217"
On Tuesday, November 15, 2016 at 8:23:49 PM UTC-8, Jorge Moraleda wrote:
>
> I believe variable resolution in nested add_role is still not working
> properly. For example if we change the example shown in the ticket above
> such that instead of the line
> b: "{{ a+1 }}"
> in ./roles/a/tasks/main.yml where (a is a variable that was passed to the
> add_role) we had instead
> b: "{{a_defaults_var}}"
> where a_defaults_var was a variable *not passed* to the add_role. (It was
> for example defined in roles/a/defaults/main.yml) then we get a
> a_defaults_var not defined.
>
--
You received this message because you are subscribed to the Google Groups
"Ansible Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to ansible-devel+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
