release: PR for v0.7.2-rc.0

[systemsdt]

Updates in hyperion micro-service and charts

[gitguardian[bot]]

⚠️ GitGuardian has uncovered 11 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	bf35ec5157cf484844378940e1540540380ac667	devtron-images.txt.source	View secret
10220829	Triggered	Generic High Entropy Secret	77c3d3f63b387216f363ee35341ff2f9fc940d27	charts/devtron/values.yaml	View secret
10220829	Triggered	Generic High Entropy Secret	77c3d3f63b387216f363ee35341ff2f9fc940d27	charts/devtron/devtron-bom.yaml	View secret
10220829	Triggered	Generic High Entropy Secret	5439928b08018a6e82804dab19c66af7e1c0f0f7	charts/devtron/devtron-bom.yaml	View secret
10220829	Triggered	Generic High Entropy Secret	5439928b08018a6e82804dab19c66af7e1c0f0f7	charts/devtron/values.yaml	View secret
10220829	Triggered	Generic High Entropy Secret	c7976c9a835478c7ce62b0fd602b8df221495bdc	charts/devtron/devtron-bom.yaml	View secret
10220829	Triggered	Generic High Entropy Secret	c7976c9a835478c7ce62b0fd602b8df221495bdc	charts/devtron/values.yaml	View secret
10220829	Triggered	Generic High Entropy Secret	6a5aa4212e0e3d13326fdb732900eba09399067b	charts/devtron/devtron-bom.yaml	View secret
10220829	Triggered	Generic High Entropy Secret	6a5aa4212e0e3d13326fdb732900eba09399067b	charts/devtron/values.yaml	View secret
10220829	Triggered	Generic High Entropy Secret	4ac77e9aed755e8693eb7ca9f220fe321980018e	charts/devtron/values.yaml	View secret
10220829	Triggered	Generic High Entropy Secret	4ac77e9aed755e8693eb7ca9f220fe321980018e	charts/devtron/devtron-bom.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
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

[sonarqubecloud[bot]]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud