Description

Fixes #

Checklist:

[ ] The title of the PR states what changed and the related issues number (used for the release note).
[ ] Does this PR requires documentation updates?
[ ] I've updated documentation as required by this PR.
[ ] I have performed a self-review of my own code.
[ ] I have commented my code, particularly in hard-to-understand areas.
[ ] I have tested it for all user roles.
[ ] I have added all the required unit/api test cases.

Does this PR introduce a user-facing change?

Apr 15 '24 07:04 kamal-devtron

⚠️ GitGuardian has uncovered 8 secrets following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

Since your pull request originates from a forked repository, GitGuardian is not able to associate the secrets uncovered with secret incidents on your GitGuardian dashboard. Skipping this check run and merging your pull request will create secret incidents on your GitGuardian dashboard.

🔎 Detected hardcoded secrets in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
10220829	Triggered	Generic High Entropy Secret	4753231eb08700414e2aacfa3db1d5a091fd0001	devtron-images.txt.source	View secret
9257608	Triggered	Base64 AWS keys	78febd9299324c6abf2d1cd4ddb8246c908178c4	scripts/devtron-reference-helm-charts/deployment-chart_4-20-0/test-values.json	View secret
2763127	Triggered	Generic High Entropy Secret	024d62a6b4f0c6142deac5f997b8eb325fe02a11	scripts/devtron-reference-helm-charts/reference-chart_4-19-0/secrets-test-values.yaml	View secret
2763127	Triggered	Generic High Entropy Secret	78febd9299324c6abf2d1cd4ddb8246c908178c4	scripts/devtron-reference-helm-charts/deployment-chart_4-20-0/secrets-test-values.yaml	View secret
2763127	Triggered	Generic High Entropy Secret	14d998f8311505531d13cdce8baca7f4feaa3472	scripts/devtron-reference-helm-charts/reference-chart_4-19-0/secrets-test-values.yaml	View secret
141558	Triggered	Generic High Entropy Secret	78febd9299324c6abf2d1cd4ddb8246c908178c4	scripts/devtron-reference-helm-charts/deployment-chart_4-20-0/env-values.yaml	View secret
141558	Triggered	Generic High Entropy Secret	14d998f8311505531d13cdce8baca7f4feaa3472	scripts/devtron-reference-helm-charts/reference-chart_4-19-0/env-values.yaml	View secret
141558	Triggered	Generic High Entropy Secret	024d62a6b4f0c6142deac5f997b8eb325fe02a11	scripts/devtron-reference-helm-charts/reference-chart_4-19-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.}