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?

Sep 23 '24 11:09 iamayushm

⚠️ 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.

🔎 Detected hardcoded secrets in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
13816532	Triggered	Generic Private Key	246c8cf34a46093adb53b1907fef8757d1bfd5d8	vendor/github.com/google/s2a-go/testdata/mds_client_key.pem	View secret
10220829	Triggered	Generic High Entropy Secret	1f7995ee1f6610b4680b1c5835ee0555e4b7bb00	charts/devtron/devtron-bom.yaml	View secret
10220829	Triggered	Generic High Entropy Secret	1f7995ee1f6610b4680b1c5835ee0555e4b7bb00	charts/devtron/values.yaml	View secret
10220829	Triggered	Generic High Entropy Secret	af5f36db4367721ed5e7d2058adc948914c979fb	devtron-images.txt.source	View secret
10220829	Triggered	Generic High Entropy Secret	508a70b0d1c52d9a998dcc9fe0e0a8cbf37801c4	charts/devtron/devtron-bom.yaml	View secret
10220829	Triggered	Generic High Entropy Secret	508a70b0d1c52d9a998dcc9fe0e0a8cbf37801c4	charts/devtron/values.yaml	View secret
10220829	Triggered	Generic High Entropy Secret	9eabc1215369b9bf0778774df7924762497d6e4b	charts/devtron/values.yaml	View secret
10220829	Triggered	Generic High Entropy Secret	9eabc1215369b9bf0778774df7924762497d6e4b	charts/devtron/devtron-bom.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.}