Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

git-secrets-scan:3.1.0 ignoring GITLEAKS_EXTRA_ARGS

John Alberts March 17, 2025

I'm trying to start using git-secrets-scan:3.1.0 pipe and the pipe appears to be ignoring the GITLEAKS_EXTRA_ARGS that is passed to it.

I have the following:

```yaml

- step: &SecurityScan
name: Security Scan
script:
- pipe: atlassian/git-secrets-scan:3.1.0
variables:
GITLEAKS_EXTRA_ARGS:
- "--baseline-path=gitleaks-baseline-report.json"
- "--platform=none"
```
When the step runs, none of the extra arguments appear to be passed to the gitleaks command, because the gitleaks run is ignoring my baseline file and still complains about unknown SCM platform.
If I run the following locally, it runs fine:
`gitleaks git --baseline-path=gitleaks-baseline-report.json --platform=none`

2 answers

0 votes
Igor Stoyanov
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
March 19, 2025

Hi @John Alberts . Here i provided configuration:

      - pipe: docker://bitbucketpipelines/git-secrets-scan:3.1.0
        variables:
          DEBUG: "true"
          GITLEAKS_EXTRA_ARGS:
              - "--verbose"
              - "--redact=100"
              - "--max-decode-depth=3"

 And here is the output:

Screenshot 2025-03-19 at 10.17.09.png

Try to add DEBUG to see gitleaks generated command.

 

Regards, Igor

0 votes
Ben
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
March 18, 2025

Hi John,

I've reached out to our pipes team for further assistance on this. They should respond shortly.

Cheers!

- Ben (Bitbucket Cloud Support)

 

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
PERMISSIONS LEVEL
Product Admin Site Admin
TAGS
AUG Leaders

Atlassian Community Events