Add support for arbitrary terraform functions #11542
Merged
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.
This allows
terraformWriter.LiteralFunctionExpression
to be used with any terraform function.The arguments must be strings, which means that any string arguments must include quotes. I was debating between this and using a slice of interfaces for
Literal.FnArgs
and passing each tojson.Marshal
to get their string representations (which would quote the strings for us). This would require either returning thejson.Marshal
error up through all of the HCL2 rendering (which doesn't currently return errors) or adding a panic which I'm not excited about.Feedback welcome.
/hold