use hclmerge to merge a new tflint config file when there is override hcl config #25
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 past we'll use
.tflint_alt.hcl
instead of downloadedavm.tflint.hcl
, so the repo's owner could customize their own tflint config. But once we've upgraded theavm.tflint.hcl
in the center repo, we might need upgrade all.tflint_alt.hcl
files to adapt the new config, and that could be very difficult.In this pr I use
hclmerge
to ease the pain. It could merge two hcl files like Terraform override file, so when the repo owners want to customize a config, they don't need to maintain a complete.tflint_alt.hcl
file anymore, instead, they could create aavm.tflint.override.hcl
oravm.tflint_example.override.hcl
file, contains the parts they'd like to patch on the centralized version config file.