Olivier Halligon

Yup 👍 Just some thoughts: * I’d prefer a `--print-context` option for example, i.e. sure a dedicated option but maybe not named like `--debug`, as I’m guessing it might also...

In case we chose the additive solution — i.e. that `-t/-p/-o` flags can be used in addition to `-c` (aka `--print-context`) and that `-c` takes the path to the file...

Re-reading that I think I more and more like the 2nd approach better. We could imagine implement a first version (option A) to have it quickly available (e.g. in 5.1)...

`jazzy` seem to fail while parsing the documentation for my pod [`Reusable`](https://github.com/AliSoftware/Reusable) locally when telling it to [use the podspec](https://github.com/AliSoftware/Reusable/blob/master/Reusable.podspec), because it seems to run `xcodebuild` twice and then finds...

On a side note, some flags of the CLI seems to lack documentation as well. E.g. the `--podspec` flag does not have any description in the help banner :wink:

We definitively should follow-up on that and finally finish up that work—I think that was the last piece of the puzzle before finally considering the whole Localization Tooling Project Thread...

!component =plugins/modules/homebrew.py

Ah, that explains it! Thanks for the quick answer. Could this information be added to the docs maybe? (Or is it already and I missed it?) Seems it'd be useful...

> `jq` is not always a valid solution, because long lines can also occur in other file types Ah, good point. Honestly, I was quite surprised that the check seemed...

From a quick look at the code, seems [we're supposed to log those cases](https://github.com/bridgecrewio/checkov/blob/main/checkov/secrets/plugins/custom_regex_detector.py#L72-L74)? Yet when running `checkov --file output/tfplan.json` on our unformatted, all-in-one-line state file (with `.checkov.yml` defining `output:...