Absolutely not.
--- # some var
basedir: '/some/path'
foo:
path1: '{{ basedir }}/filename'
path2: '{{ basedir }}/filename'
What you were doing was reference a structure that somehow 'knew' it's
variable name before it was even created, so I think it's quite fine if
that isn't a thing.
It working before was a side effect of the legacy template engine being
rather ... special.
On Tue, Dec 17, 2013 at 10:09 PM, <[email protected]> wrote:
> So just to be clear to do the example I used earlier using the {{foo}}
> variables I'd need to do what is below? If so I'd have to say that kind of
> sucks. I really preferred the other method unless there is something I'm
> missing to make things work just as easily.
>
> --- # some task
> - name: test
> action: debug msg="got {{foo.path1}}"
> action: debug msg="got {{foo.path2}}"
>
> --- # some var
> foo:
> path1: '/some/path//filename'
> path2: '/some/path//filename'
>
> --
> 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].
> 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 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].
For more options, visit https://groups.google.com/groups/opt_out.
