Extend jinja2 nested undefined support to keys/indices #55094
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
felixfontein
approved these changes
Apr 10, 2019
bcoca
approved these changes
Apr 10, 2019
|
@felixfontein I have gotten approval for merging this as a bugfix for the 2.8 release. So It will go in momentarily. |
|
cc @agaffney |
|
@sivel awesome! :) |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
SUMMARY
Currently the
AnsibleUndefinedclass only implements nested undefined support when using dot notation. This PR extends this functionality to keys/indices via subscript/bracket notation.ISSUE TYPE
COMPONENT NAME
lib/ansible/template/init.py
ADDITIONAL INFORMATION