Marco Ferrari

Hi! As a workaround, you could (relatively easily) change the entrypoint of the container image to point to your script, and then invoke entrypoint that we set. You're right in...

Hi @AkiKanellis ! In a couple of my projects, I went with your no.1+3 suggestions above, which would be a trivial addition to the default `ansible-lint` configuration we ship. Feel...

Hi! To troubleshoot this issue, we need to be able to reproduce it. Can you please provide an example of a source file that triggers this?

I suspect it's some kind of transient error. Given that we didn't enable `--show-error` but we did enable silent mode when using `cURL` to call the status API, we aren't...

@Zee2 now that we merged #3367, we're going to get more detailed output. I'm going to close this one, but please open a new issue once you're able to reproduce...

I'd be happy to review a PR for this. Feel free to contribute it if you think it would be valuable. Sounds like a nice feature to have.

@dependabot recreate

@hzz780 thanks for this PR. Can you also: 1. Update the `package-lock.json` 2. Update the `test/inspec/super-linter/controls/super_linter.rb` test suite to check for the existence of those two packages you want to...

Hi! Does the same version of terrascan produces the same output if you run it outside super-linter?

@jeremycarroll is correct. The linters are installed when we build the super-linter container image, so it's not feasible to customize the installed version at run time. You can see which...