Hi, recently I added this ticket to V2: https://github.com/ansible/ansible/issues/11807
It was closed with explanation that this is expected behaviour. I will have to argue on this one. Lets say that *roleA* installs i don't know Apache Maven or what ever and *MY_VARIABLE* would be version that should be installed. For some reason it uses *include_vars* for including *MY_VARIABLE*. Now lets say *roleB* is generic role, that will install all my different web apps, all I have to do is to provide different *vars_files* for the play. So I will provide version of my web app to be installed again in variable *MY_VARIABLE.* And unexpectedly when these roles will be used in same playbook (different plays of course) it will not work, as demonstrated in the ticket. So I ask, why should some hidden *include_vars* task in some role from different play have higher priority than *vars_files* I specify in the current play? Thanks Martin -- 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/141d8e68-bc41-45de-8b1f-d29a7a10f9f8%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
