Skip to content

Add gitleaks allowlist for secret-detection

What does this MR do and why?

Describe in detail what your merge request does and why.

Add gitleaks allowlist for secret-detection

We have recurring secrets being reported by Secret Detection. These secrets are only used for tests, and are not real tokens, but they keep appearing in Vulnerability Reports.

This MR is introducing a gitleaks config with an allowlist so these secrets are not reported anymore, once for all.

Using #gitleaks:allow comments could work too, but sometimes secrets are in the docs, and adding a comment there on the same line isn't possible.

Screenshots or screen recordings

Screenshots are required for UI changes, and strongly recommended for all other merge requests.

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

Merge request reports

Loading