search

Yelp / detect-secrets

An enterprise friendly way of detecting and preventing secrets in code.
Apache License 2.0
3.59k stars 449 forks source link

Getting detect-secrets: command not found error #792

Closed aakanshaverma1310 closed 1 month ago

aakanshaverma1310 commented 4 months ago

From past 15 days, we are getting below error while using detect secret scan tool. Earlier it was working fine for me.

command - detect-secrets scan --force-use-all-plugins --all-files $(System.DefaultWorkingDirectory)/repo-name > $(Pipeline.Workspace)/detect-secrets.json

Any leads who can help me here to fix the issue? Thanks in advance.

image

aakanshaverma1310 commented 4 months ago

@gpflaum @lorenzodb1 - Any suggestion on above?

gpflaum commented 4 months ago

It looks like detect-secrets is simply not on the path in your build environment. I don't know what build pipeline tools you are using. Did your build move from a machine that had detect-secrets installed to one that doesn't? I don't see any indication that detect-secrets is doing anything wrong, just that your build is failing to find it to run it.

lorenzodb1 commented 1 month ago

We're going to close this issue as it hasn't received any update in a very long time. Feel free to re-open it if you think it's still relevant.