On 24 February 2015 at 14:21, Jiri <[email protected]> wrote:
> The question is why it's even trying to merge the two variables? I would
> expect the variable to be replaced and not merged as per default setting
> hash_behaviour=replace in ansible.cfg.
>
That reason seems to be, merging happens on higher-level internal
variables (setup cache, various play vars, inventory vars, etc.)
The merge_hash then happens recursively, which is why you see that error,
even if you don;t have the merge setting.
I'm not sure your proposed patch solves the deeper issue, only what happens
in your case, and might potentially break other things.
The issue here is {{ my_xxx }} being cast to a string instead of a
dictionary.
--
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/CAEhzMJD9Qjh8T4rTcv2YDd1x0iWEqtonot_H1nD5JsCfE-e_HQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
