i believe i had run into something very similar, if not identical, trying
to follow Michael's original post on this. my solution ended up being to
reference the vars dir relatively as opposed to assuming ansible could just
find it; my bad for not submitting a bug. Anand, does something like this
work for you?
- include_vars: "{{ item }}"
with_first_found:
- ../vars/{{ ansible_hostname }}.yml
- ../vars/default.yml
On Sun, Dec 1, 2013 at 9:11 AM, Anand Buddhdev <[email protected]> wrote:
> That's a bummer because I was waiting to make use of this feature in 1.4.
> If I have to wait for 1.5 then I'm stuck using top-level host_vars and
> group_vars :(
>
> Why would you not make a point release for this if it's a bug? My example
> is written exactly as you described in a message several days ago when
> introducing this feature and your own example is actually failing for me.
>
> Anand
>
> On 1 Dec 2013, at 14:55, Michael DeHaan <[email protected]> wrote:
>
> This generally isn't something we'd force a dot release for, unless we
> otherwise thought we needed to cut a dot release.
>
> If we did, we'd likely wait longer as well.
>
>
>
>
>
>
> On Sat, Nov 30, 2013 at 8:19 AM, Anand Buddhdev <[email protected]> wrote:
>
>> On Saturday, 30 November 2013 13:54:40 UTC+1, Michael DeHaan wrote:
>>
>> Hi Michael,
>>
>> Yep, I can replicate this.
>>>
>>
>> Oh, good :)
>>
>>
>>> include_vars is new for 1.4.X so we probably missed a possible use case
>>> that someone would want to try.
>>>
>>> Please file a github ticket.
>>>
>>
>> Filed as issue #5108
>>
>>
>>> Meanwhile, you can work around this in a play like so:
>>>
>>
>> I don't need the work-around urgently, because we're using top-level
>> host_vars and group_vars. When you've fixed this bug, then I will rewrite
>> our playbooks and move those vars files directly into roles. Do you think
>> you will make a 1.4.2 release for this? In that case, I'm happy to just
>> wait a few days for it.
>>
>> Regards,
>>
>> Anand
>>
>> --
>> 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].
>> For more options, visit https://groups.google.com/groups/opt_out.
>>
>
>
>
> --
> Michael DeHaan <[email protected]>
> CTO, AnsibleWorks, Inc.
> http://www.ansibleworks.com/
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Ansible Project" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/ansible-project/UQ_ArPEofFU/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> [email protected].
>
> For more options, visit https://groups.google.com/groups/opt_out.
>
> --
> 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].
> For more options, visit https://groups.google.com/groups/opt_out.
>
--
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].
For more options, visit https://groups.google.com/groups/opt_out.
