Adding ability to sanitize output for jinja templating #79
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What am I trying to do?
I am trying to sanitize output of jira, at all levels of any jinja templating things that would be markdown artifacts from getting jira data from the API so that it does not cause issues after you get it and try to use it as a var in a workflow due to those artifacts existing and causing stackstorm to think it is missing a variable.
I went for minimal touch instead of making it default, it is leaving it how it was unless you set it to true. Then it will iterate through all levels of the data to remove any of the jinja templating which from what I have found is mainly the
{{and}}.