Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: added new statefulset-5-0-0 chart in reference chart #3909

Merged
merged 13 commits into from
Sep 14, 2023

edit the old 4-18 chart hpa.yaml file

2fc5dd3
Select commit
Failed to load commit list.
Merged

feat: added new statefulset-5-0-0 chart in reference chart #3909

edit the old 4-18 chart hpa.yaml file
2fc5dd3
Select commit
Failed to load commit list.
GitGuardian / GitGuardian Security Checks completed Sep 14, 2023 in 1s

2 secrets uncovered!

2 secrets were uncovered from the scan of 13 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 #3909: feat-sts-5-0-0 👉 main
GitGuardian id Secret Commit Filename
141558 Generic High Entropy Secret 93942fb scripts/devtron-reference-helm-charts/statefulset-chart_5-0-0/env-values.yaml View secret
2763127 Generic High Entropy Secret 93942fb scripts/devtron-reference-helm-charts/statefulset-chart_5-0-0/secrets-test-values.yaml View secret

🛠 Guidelines to remediate hardcoded secrets

  1. Understand the implications of revoking this secret by investigating where it is used in your code.
  2. Replace and store your secrets safely. Learn here the best practices.
  3. Revoke and rotate these secrets.
  4. 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


🦉 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.

Our GitHub checks need improvements? Share your feedbacks!