Display the string which is causing an exception to be raised. #14445
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
In the ansible template module, when there is an error while expanding a templated string, displaying the string causing the exception is very useful.
jimi-c
added a commit
that referenced
this pull request
Feb 12, 2016
…ception Display the string which is causing an exception to be raised.
|
Merged, thanks! |
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.
In the ansible template module, when there is an error while
expanding a templated string, displaying the string causing the
exception is very useful.
I had a missing closing } in a string from the group_vars/all file. The error only happened when I was trying to access a hostvars variable in a playbook. With this error message, I found the problem right away.