fix: update tflint script to accept newer versions #40
Conversation
This file contains hidden or 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
kkmlr
reviewed
Feb 13, 2024
zied-elouaer
previously approved these changes
Feb 13, 2024
Esanim
force-pushed
the
update-tflint-script
branch
from
e598189 to
3df7d5e
Compare
zied-elouaer
approved these changes
Feb 13, 2024
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.
Usage of tflint has changed since 0.47 ("command line arguments support was dropped").
Also for providers, tflint now requires a configuration file (e.g. plugin for google) that has to be initialized with
tflint --init.For the CI runs, it will require github token to avoid rate-limiting, that's why the 'init' happens only locally.
In the script, if the tflint version is >= 0.47, it will just run
tflinton the root dir.