chore: when a cluster event occurs, create config map instead of secret #6607
GitGuardian / GitGuardian Security Checks
completed
Jun 9, 2025 in 12s
3 secrets uncovered!
3 secrets were uncovered from the scan of 28 commits in your pull request. ❌
Please have a look to GitGuardian findings and remediate in order to secure your code.
Details
🔎 Detected hardcoded secrets in your pull request
- Pull request #6607:
create-cm-on-cluster-action-oss👉develop
| GitGuardian id | GitGuardian status | Secret | Commit | Filename | |
|---|---|---|---|---|---|
| 9257608 | Triggered | Base64 AWS keys | a61bf2f | scripts/devtron-reference-helm-charts/gpu-workload-4-21-0/test-values.json | View secret |
| 2763127 | Triggered | Generic High Entropy Secret | 6e196cb | scripts/devtron-reference-helm-charts/cronjob-chart_1-6-0/secrets-test-values.yaml | View secret |
| 141558 | Triggered | Generic High Entropy Secret | a61bf2f | scripts/devtron-reference-helm-charts/gpu-workload-4-21-0/env-values.yaml | View secret |
🛠 Guidelines to remediate hardcoded secrets
- Understand the implications of revoking this secret by investigating where it is used in your code.
- Replace and store your secrets safely. Learn here the best practices.
- Revoke and rotate these secrets.
- If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.
To avoid such incidents in the future consider
- following these best practices for managing and storing secrets including API keys and other credentials
- install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.
🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.
Loading