Option to display parsing errors
See original GitHub issueWhen checkov reports parsing errors there’s no way to see the error or even the file which caused it. I’m testing this in a project which passes terraform validate
.
$ checkov -f main.tf
_ _
___| |__ ___ ___| | _______ __
/ __| '_ \ / _ \/ __| |/ / _ \ \ / /
| (__| | | | __/ (__| < (_) \ V /
\___|_| |_|\___|\___|_|\_\___/ \_/
version: 1.0.181
Passed checks: 0, Failed checks: 0, Skipped checks: 0, Parsing errors: 1
Issue Analytics
- State:
- Created 4 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
Parse Error: What It Is and How to Fix It - Lifewire
A parse error is an error message you sometimes get on Android devices when an app fails to install. The message itself is...
Read more >Option Parsing: Error Handling - Stephen Cleary
The Nito.KitchenSink Option Parsing Library wraps all option parsing errors into an exception derived from Nito.KitchenSink.OptionParsing.
Read more >Understanding parsing errors - Appl. programming - IBM
Incorrectly specified length fields can cause errors when IMS checks for valid keywords. When IMS is checking the validity of keywords on the...
Read more >Parsing Arguments with Your Own Error Messages - O'Reilly
You are using getopts to parse your options for your shell script. But you don't like the error messages that it writes when...
Read more >How to fix Parse Error There was a problem ... - YouTube
How to fix Parse Error There was a problem parsing the package.1. Allow Apps Installation from Unknown Sources.2.Enable USB Debugging.3: ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
You can now get verbose logs using environment variable LOG_LEVEL=DEBUG - it can give further info about what’s checkov is doing
Excellent, thanks!