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.
If tfsec doesn't find any valid terraform files within a certain range, it will scan recursively until it finds them. On Windows, with junctions this ends up cascading into our plugins repo. On other platforms, when running outside of a sandbox, this can also recurse into our test data, one of which is the checkov test data file, which tfsec incorrectly fails to parse (even though it is valid tf).
I've added a flag to not error on parsing errors like this one. It's a bit heavy-handed, but we have other tf linters in order to address issues like this, and it's better than failing outright, particularly for the users out in the world who already have tfsec enabled.