Just came across a really hard bug to track down. The code in question
looked, essentially, like this:
[[[
- include: some_file.yml
vars:
x: 1
]]]
The problem here was that some_file.yml was not being invoked with x set to
1. The reason for this was that another included playbook had done the
following:
[[[
- set_fact:
x: 2
]]]
As you might imagine, this behaviour leads to bugs that are almost
impossible to track down: one cannot examine an include and know for
certain the variables that will be passed into the included task.
I've raised a bug on this but I'd appreciate feedback about whether this
really is broken by accident: I find it hard to believe that anyone's
depending on the current behaviour.
https://github.com/ansible/ansible/issues/12277
Cheers,
jan
--
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/ff7a6acf-efe5-42df-9179-7cf5ca13fc22%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
