Denis Loginov
Denis Loginov
@Elias-Graf have you heard from support on when it'll be released, by any chance?
Unfortunately, it doesn't work even when specifying both id and secret: ```bash trufflehog git https://github.com/dinvlad/test-secrets-detection --branch test2 ``` (this is a real but deactivated/deleted pair of credentials btw)
FWIW, when I run this latest example with a filesystem scan locally, it does detect them. But not so with Git: https://gist.github.com/dinvlad/892fa1e435f38fbcc58a936084e1d7ca#file-filesystem_vs_git_local-txt
Any updates on this?
They have actually been added in a single diff, please take a look here: https://github.com/dinvlad/test-secrets-detection/commit/c3c247d10eef0bef6a28c981bd4da64529ed816a Please note this is on branch **test2**, which is why maybe it wasn't showing up...
@bill-rich awesome, thanks so much for troubleshooting it!
Same here, in our application it's the `volumes:host:sourcePath` that needs to be set for each individual task, and currently we have to register a new task definition just for that...
Hi @grant - I'm referring to automatic logging of all requests by this library, as opposed to only the errors. For sure, we could add logging in our own code,...
Makes sense, thanks for clarifying it! I was thinking to add only general logging however, like the response status and possibly request latency, possibly only for local development indeed. Exactly...