Re: [ansible-project] Understanding lookup task context

2018-04-06 Thread Brian Coca
No docs really, this is not something people normally hit as it is rare to try to do indirect lookups via hostvars. It has more to do on how hostvars works than anything else, it is a lazy object that is lazy loaded vars, pre 2.5 we woudl load all vars per host and keep that info (w/o it having

Re: [ansible-project] Understanding lookup task context

2018-04-06 Thread Lihu Ber
Hi Brian, thanks so much for being so responsive! Why the difference in 'task awareness' between the two access methods? Also, is there some documentation on which operations are task-aware, and which ones aren't? On Friday, April 6, 2018 at 11:40:56 AM UTC-4, Brian Coca wrote: > > I forgot to

Re: [ansible-project] Understanding lookup task context

2018-04-06 Thread Brian Coca
I forgot to add to the response, that hostvars is not 'task aware' while direct variable access IS task aware. -- -- 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

[ansible-project] Understanding lookup task context

2018-04-06 Thread Lihu Ber
I noticed odd behavior with Ansible lookups a while back and, thinking it was a bug, reported it here . Essentially, when I defined a lookup in host_vars, and referenced it in different ways from the same role, the lookup was executing with a