plugin: Add support for fetching rule config #1003
Merged
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
wata727
force-pushed
the
add_support_for_decode_rule_config
branch
3 times, most recently
from
56a2891
to
a591192
Compare
wata727
force-pushed
the
add_support_for_decode_rule_config
branch
from
a591192
to
a4f3b6a
Compare
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.
To cut out the
aws_resource_missing_tagsrule into a plugin, this PR adds a new runner API, calledRuleConfig.This API returns an encoded HCL format rule config like the plugin configuration. See also #967
On the plugin side, they can decode the rule config and reflects it into the config structure defined in the rule implementation using
gohcl.DecodeBody.See also terraform-linters/tflint-plugin-sdk#82