Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: removed additionalBackends from app-values.yaml #3807

Merged
merged 19 commits into from
Aug 22, 2023
Merged

feat: removed additionalBackends from app-values.yaml #3807

merged 19 commits into from
Aug 22, 2023

Conversation

badal773
Copy link
Contributor

removed additionalBackends from app-values.yaml of the following charts

  1. statefulset-chart_4-18-0
  2. deployment-chart_4-18-0
  3. reference-chart_4-18-0
  4. reference-chart_5-0-0

@gitguardian
Copy link

gitguardian bot commented Aug 22, 2023

⚠️ GitGuardian has uncovered 6 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 Secret Commit Filename
- Generic High Entropy Secret 46c262d scripts/devtron-reference-helm-charts/reference-chart_4-17-0/env-values.yaml View secret
- Generic High Entropy Secret 46c262d scripts/devtron-reference-helm-charts/reference-chart_4-17-0/secrets-test-values.yaml View secret
- Generic High Entropy Secret e084b22 scripts/devtron-reference-helm-charts/deployment-chart_4-18-0/env-values.yaml View secret
- Generic High Entropy Secret e084b22 scripts/devtron-reference-helm-charts/deployment-chart_4-18-0/secrets-test-values.yaml View secret
- Generic High Entropy Secret ea8f596 scripts/devtron-reference-helm-charts/reference-chart_4-17-0/env-values.yaml View secret
- Generic High Entropy Secret ea8f596 scripts/devtron-reference-helm-charts/reference-chart_4-17-0/secrets-test-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


🦉 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!

@sonarqubecloud
Copy link

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
No Duplication information No Duplication information

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants