I realized how easy it would be to test the precedence so I did so, and
yes, the order you run the group_by is the factor that determines which var
wins.
That is way simpler... I'll try rewriting some stuff that way and see if it
feels any less flexible. Thanks again!!
On Wednesday, January 8, 2014 11:06:49 AM UTC-6, Mark Casey wrote:
>
> I didn't realize if you had a *../group_vars/Debian* file and ran the
> task *group_by: key={{ansible_os_family}}* on a Debian family host that
> in the next play those vars will be available. I just tried it though, and
> it works. Is that what you mean?
>
> If so...one final question (hopefully). If I had *../group_vars/Debian*and
> *../group_vars/DebianUbuntu* but both files defined the same variable,
> would the precedence be defined by which *group_by* I run first?
>
> Thank you,
> Mark
>
> On Tuesday, January 7, 2014 4:38:35 PM UTC-6, Michael DeHaan wrote:
>>
>> That strikes me as making things a bit too complicated, I'd probably just
>> look into putting your hosts into a group and assigning the variables to a
>> group via group_vars and keeping it simple.
>>
>> But that's me.
>>
>>
>> ...
>>
>
--
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.
For more options, visit https://groups.google.com/groups/opt_out.
