Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Checkov return empty result

See original GitHub issue

Describe the bug checkov checks his own version an terminates unexpectly.

$ checkov -f main.tf                                                                                                                                                                                                                  

       _               _
   ___| |__   ___  ___| | _______   __
  / __| '_ \ / _ \/ __| |/ / _ \ \ / /
 | (__| | | |  __/ (__|   < (_) \ V /
  \___|_| |_|\___|\___|_|\_\___/ \_/

By bridgecrew.io | version: 1.0.690
Update available 1.0.690 → 1.0.694
Run pip3 install -U checkov to update

To Reproduce 2020-01-11_15:01 CET:

brew install checkov                                                                                                                                                                                                                
Updating Homebrew...
==> Downloading https://homebrew.bintray.com/bottles/checkov-1.0.690.catalina.bottle.tar.gz
Already downloaded: /Users/petersa/Library/Caches/Homebrew/downloads/524348eefae3d4068a02df846d0547b103a3bbae2c2b5abcfd4b0e11fc5a5be8--checkov-1.0.690.catalina.bottle.tar.gz
==> Pouring checkov-1.0.690.catalina.bottle.tar.gz
🍺  /usr/local/Cellar/checkov/1.0.690: 2,650 files, 66.8MB

$ checkov -f main.tf

Desktop (please complete the following information):

OS: mac os x catalina

Issue Analytics

State:
Created 3 years ago
Comments:21 (11 by maintainers)

Top GitHub Comments

1reaction

AErmiecommented, Feb 2, 2021

Hey @schosterbarak, I’m digging deeper into it now, and it actually (at least in my case) may not be an issue with Checkov.

The scenario where I thought it was not producing anything, was for a customer using Azure DevOps Server (on-premises), and self-hosted agents. It appears that the self-hosted agents don’t clean up fully after themselves, leaving residual artifacts.

I believe it is these residual artifacts that are causing the issue, as when executing Checkov it’s re-using local files versus creating new ones. I have an ask out to the Microsoft DevOps team(s) to clarify; and will attempt to re-test if/when a solution presents itself.

NOTE: I have not observed this behavior when using Azure DevOps (online).

0reactions

nimrodkorcommented, Dec 27, 2021

This issue is very old. Hopefully it has been resolved, if not - please open a new one according to the new templates 🙏

Top Results From Across the Web

CLI Command Reference - checkov

Runs checks but always returns a 0 exit code. Using either –soft-fail-on and / or –hard-fail-on overrides this option, except for the case...

Prioritize, skip, and fail with policy severities in Checkov

Policy severities are now included in Checkov to help prioritize findings and make CI/CD skip and fail flags more manageable.

How to use the checkov.terraform.models.enums.CheckResult ...

To help you get started, we've selected a few checkov.terraform.models.enums.CheckResult examples, based on popular ways it is used in public projects.

checkov custom policy working only with terraform code and ...

output has other scans but not the custom scan. cloudformation scan results: Passed checks: 1, Failed checks: 1, ...

Checkov shows no result during Helm chart scan

During my tests scanning Helm charts with Checkov I never received output nor error, although there are violations inside the chart. In this ......