feat: added reference-chart 4.180 and deploy-chart 1.2.0 #3423
Conversation
|
| GitGuardian id | Secret | Commit | Filename | |
|---|---|---|---|---|
| - | Generic High Entropy Secret | 1fdcfbe | scripts/devtron-reference-helm-charts/deployment-chart_1-2-0/env-values.yaml | View secret |
| - | Generic High Entropy Secret | 1fdcfbe | scripts/devtron-reference-helm-charts/deployment-chart_1-2-0/secrets-test-values.yaml | View secret |
| - | Generic High Entropy Secret | 1fdcfbe | scripts/devtron-reference-helm-charts/deployment-chart_1-2-0/test-values.json | View secret |
| - | Generic High Entropy Secret | 1fdcfbe | scripts/devtron-reference-helm-charts/reference-chart_4-18-0/env-values.yaml | View secret |
| - | Generic High Entropy Secret | 1fdcfbe | scripts/devtron-reference-helm-charts/reference-chart_4-18-0/secrets-test-values.yaml | View secret |
| - | Generic High Entropy Secret | db1bbc1 | scripts/devtron-reference-helm-charts/cronjob-chart_1-5-0/env-values.yaml | View secret |
| - | Generic High Entropy Secret | db1bbc1 | scripts/devtron-reference-helm-charts/cronjob-chart_1-5-0/secrets-test-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.
Our GitHub checks need improvements? Share your feedbacks!
jatin-jangir
force-pushed
the
sealed-secret
branch
from
a404a15 to
b26da26
Compare
…_ref_4-18-0.up.sql
…rt_ref_4-18-0.down.sql
|
Kudos, SonarCloud Quality Gate passed!
|
…rt_ref_4-18-0.down.sql
…_ref_4-18-0.up.sql
jatin-jangir
force-pushed
the
sealed-secret
branch
from
a65ac03 to
db5b6ad
Compare
removed relabelings updated change in service monitor changed sourceLabels
jatin-jangir
force-pushed
the
sealed-secret
branch
from
db5b6ad to
7102a3e
Compare
|
SonarCloud Quality Gate failed.
|
4 participants
Description
Fixes #
How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration
Checklist:
Does this PR introduce a user-facing change?