Is there really no better way to do it? While Leo's method works it's extremely ugly to look at nor easily reusable.
On Friday, 31 January 2014 22:58:17 UTC+11, Stephen Ryan wrote: > > > > Best to explain with an example > > We have tasks setup like > > - name: do something > shell: do task > when: foo is defined > > This works perfectly for most situations however we have a number of > places where we need to unset the variable to stop the command on certain > hosts. Neither of the following work when set in the group vars and result > in the task working. > > foo: > foo: "" > > So my question is how would one normally unset a variable like this or > correctly test for it. Jinja docs suggest its just an "if variable" [1], so > "when: foo" but that doesn't work whenever the variable has a value > > fatal: [127.0.0.1] => error while evaluating conditional: foo > > The closest I've gotten is > when: foo is defined and foo is string > but this feels wrong and there is no reference to using an "is string" > check in the ansible docs. > > [1] http://jinja.pocoo.org/docs/templates/#if > -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/5de066bb-e937-4613-bc95-66e6472e0a25%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
