>
> default("127.0.0.1", true)
>
Didn't help.
> It is not clear on the filter description, but without the second argument
> it does not perform a boolean evaluation, but just strict variable
> undefinition. That means that an empty string will not trigger the default.
> Actually, even if the variable you are testing is None, the default will
> not be used.
>
I'm sorry, I didn't specify that I'm getting the same "One or more
undefined variables" as Viktor was. The undefined variable can be in my
case be on any level. So for ansible_eth1.ipv4.address any of ansible_eth1,
ipv4 or address could be undefined.
Cheers,
Paul
--
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/755035f2-a67a-45c3-99d9-ea3382a7250f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
