release: PR for v0.6.30-rc.0

[systemsdt]

Updates in hyperion micro-service and charts

[sonarqubecloud[bot]]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud

[gitguardian[bot]]

⚠️ GitGuardian has uncovered 10 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
10220829	Triggered	Generic High Entropy Secret	e31a1ef84771fb7b291c41fabc86b4a85eb48614	charts/devtron/values.yaml	View secret
10220829	Triggered	Generic High Entropy Secret	e31a1ef84771fb7b291c41fabc86b4a85eb48614	charts/devtron/devtron-bom.yaml	View secret
10220829	Triggered	Generic High Entropy Secret	35b1028edb485849e15cdfdf4ba85979a13bcf45	charts/devtron/devtron-bom.yaml	View secret
10220829	Triggered	Generic High Entropy Secret	35b1028edb485849e15cdfdf4ba85979a13bcf45	charts/devtron/values.yaml	View secret
10220829	Triggered	Generic High Entropy Secret	c886d570a3a47aebb3c55f7a46ceb467b229e78a	charts/devtron/devtron-bom.yaml	View secret
10220829	Triggered	Generic High Entropy Secret	b0af145d39bf9aa6f70a5b81e79044b41286bec5	charts/devtron/values.yaml	View secret
10220829	Triggered	Generic High Entropy Secret	ba7d45fc901ac8f4f99fc21b5a585a135c35c024	charts/devtron/values.yaml	View secret
10220829	Triggered	Generic High Entropy Secret	ba7d45fc901ac8f4f99fc21b5a585a135c35c024	charts/devtron/devtron-bom.yaml	View secret
10220829	Triggered	Generic High Entropy Secret	9652d0429285a24550b838c1725b7b05b4561cd0	charts/devtron/devtron-bom.yaml	View secret
10220829	Triggered	Generic High Entropy Secret	d1b5980c33421a9926457ca02b1633db05f0cdc8	charts/devtron/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

• 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.}

[sonarqubecloud[bot]]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud