Support Sprig functions in templating #81
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
Oded-B
changed the title
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
Adding support for Sprig functions (https://github.com/Masterminds/sprig) in the templating mechanisms.
WHY
Sprig provide all kind for text manipulation functions (and more).
We use this code in our plan template to remove terrafrom's overly verbose "Refreshing state" lines and the trailing suffix meant for manual user interaction, by cutting above and bellow the "------" delimiter terrafrom adds:
index (regexSplit "(?m)^---+$\n" .Body -1 ) 1