ansible/changelogs/fragments/72615-jinja-import-context-fix.yml at 5411090f51a553995fcc7f728c5cf98e0bcf76fb - cmueller/ansible - tilera Git

cmueller/ansible

Martin Krizek 2c8c02c816

Local vars should have highest precedence in AnsibleJ2Vars (#72830 ) (#73370 )

Ability to add local variables into AnsibleJ2Vars was added in
18a9eff11f to fix #6653. Local variables
are added using ``AnsibleJ2Vars.add_locals()`` method when creating a
new context - typically when including/importing a template with
context. For that use case local template variables created using
``set`` should override variables from higher contexts - either from the
play or any parent template, or both; Jinja behaves the same way.

Also removes AnsibleJ2Vars.extras instance variable which is not used.

Also adds missing test for #6653.

Fixes #72262
Fixes #72615

ci_complete

(cherry picked from commit a2af8432f3)

2021-02-07 01:30:47 -06:00

2 lines

151 B

YAML

Raw Blame History

	`bugfixes:`
	- Fix incorrect variable scoping when using ``import with context`` in Jinja2 templates. (https://github.com/ansible/ansible/issues/72615)