Well, this is not include_vars behaviour but 'merge loop results
behaviour' that affects all modules as this is result processing.
The other part of 'saving intermediate results' would also affect all tasks.
I doubt either will change in the future.
--
Brian Coca
--
You received this
I'm falling back to the six tasks for now (three stat file, three include
when exists).
In my mind this is a bug; the "ignore_errors" setting should let it keep
the partial result. The parallel being that the file module could
partially succeed in setting a file owner but SELinux or other meth
The merge setting will affect the result of the task, but not the
internal iterator of the task.
You might want to make this 3 tasks or use vars_files.
--
--
Brian Coca
--
You received this message because you are subscribed to the Google Groups
"Ansible Project" group.
To unsubscrib
I forgot to add that I've defined the hash_behaviour to "merge" just for
this express purpose of keeping and stacking/appending variables so the
normal behavior is suppose to be modified here.
On Monday, July 10, 2017 at 2:59:22 PM UTC-5, Brian Coca wrote:
>
> Well, when you include_vars you are
Well, when you include_vars you are normally overwriting existing
vars, this will happen in a with_ loop or outside of it, that is
normal behaviour.
As for the error wiping out myvars ... the task failed, so none of the
work was done. The previously accumulated data in the 2 files that did
work is
I'm trying to setup a hierarchical set of variable files so that different
teams can setup value, permitting more specific instances to override
generic ones. The key is that the more specific instances may not be
defined in all cases. I thought I solved it with a combination of
"include_vars
