chore: refactoring deployment template & GitOps #4584
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* removed unsued jira integration * removed test-suite-code * db migration conf removal * chore: removed unused injection * chore: removed dead code * added: migration script --------- Co-authored-by: Ash-exp <[email protected]>
* moved chart-group in seperate code * removed unused dependency * removed dead code * extracted resource tree * moved notes * resource movement * removed unused code * removed unused dependency * commit methods * extracted status update * chore: clean up unused dead code * updated: EA mode docker file * updated: migration number --------- Co-authored-by: Ash-exp <[email protected]>
…loyment-template-3
…loyment-template-2
…loyment-template-3
…loyment-template-2
…loyment-template-3
kartik-579
requested review from
prakarsh-dt,
pawan-mehta-dt,
nishant-d,
vikramdevtron and
kripanshdevtron
as code owners
|
| GitGuardian id | GitGuardian status | Secret | Commit | Filename | |
|---|---|---|---|---|---|
| 141558 | Triggered | Generic High Entropy Secret | bf86180 | scripts/devtron-reference-helm-charts/statefulset-chart_4-19-0/env-values.yaml | View secret |
| 141558 | Triggered | Generic High Entropy Secret | bf86180 | scripts/devtron-reference-helm-charts/deployment-chart_4-19-0/env-values.yaml | View secret |
| 141558 | Triggered | Generic High Entropy Secret | ece3419 | scripts/devtron-reference-helm-charts/statefulset-chart_4-19-0/env-values.yaml | View secret |
| 141558 | Triggered | Generic High Entropy Secret | ece3419 | scripts/devtron-reference-helm-charts/deployment-chart_4-19-0/env-values.yaml | View secret |
| 141558 | Triggered | Generic High Entropy Secret | fe0f272 | scripts/devtron-reference-helm-charts/statefulset-chart_4-19-0/env-values.yaml | View secret |
| 141558 | Triggered | Generic High Entropy Secret | fe0f272 | scripts/devtron-reference-helm-charts/deployment-chart_4-19-0/env-values.yaml | View secret |
| 2763127 | Triggered | Generic High Entropy Secret | bf86180 | scripts/devtron-reference-helm-charts/deployment-chart_4-19-0/secrets-test-values.yaml | View secret |
| 2763127 | Triggered | Generic High Entropy Secret | bf86180 | scripts/devtron-reference-helm-charts/statefulset-chart_4-19-0/secrets-test-values.yaml | View secret |
| 2763127 | Triggered | Generic High Entropy Secret | ece3419 | scripts/devtron-reference-helm-charts/statefulset-chart_4-19-0/secrets-test-values.yaml | View secret |
| 2763127 | Triggered | Generic High Entropy Secret | ece3419 | scripts/devtron-reference-helm-charts/deployment-chart_4-19-0/secrets-test-values.yaml | View secret |
| 2763127 | Triggered | Generic High Entropy Secret | fe0f272 | scripts/devtron-reference-helm-charts/deployment-chart_4-19-0/secrets-test-values.yaml | View secret |
| 2763127 | Triggered | Generic High Entropy Secret | fe0f272 | scripts/devtron-reference-helm-charts/statefulset-chart_4-19-0/secrets-test-values.yaml | View secret |
| 9257608 | Triggered | Base64 AWS keys | bf86180 | scripts/devtron-reference-helm-charts/deployment-chart_4-19-0/test-values.json | View secret |
| 9257608 | Triggered | Base64 AWS keys | ece3419 | scripts/devtron-reference-helm-charts/deployment-chart_4-19-0/test-values.json | View secret |
| 9257608 | Triggered | Base64 AWS keys | fe0f272 | scripts/devtron-reference-helm-charts/deployment-chart_4-19-0/test-values.json | 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!
kartik-579
changed the title
github-actions
bot
added
PR:Ready-to-Review
and removed
PR:Issue-verification-failed
labels
kartik-579
changed the base branch from
main
to
refactoring-deployment-template-2
kartik-579
changed the base branch from
refactoring-deployment-template-2
to
main
|
|
closing, will go live in main through #4615 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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?