optimise dockerfile #6226
Open
optimise dockerfile #6226
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
nishant-d
requested review from
vikramdevtron,
prakarsh-dt and
vivek-devtron
as code owners
* flushed messages and handled graceful shutdown * flushing removed * removed common lib chnages
misc: isProd in cluster
* merging connection manager and user service * removing user service * refactoring get connection with token * moving config with token func * removing unused method * review changes
* extracting out chart repository methods * moving repository creation to argocd client package and secret delete code for oci
…ystem and user does not have to delete cve multiple times
sync: Main sync develop 6jan
# Conflicts: # wire_gen.go
Co-authored-by: Badal Kumar Prusty <[email protected]>
* updated the argo workflows * added new sum * executed tidy and vendor for authenticator and common lib * took sync from develop * updated teh lib * updated from develop
…ble-metrics # Conflicts: # go.mod # go.sum # vendor/modules.txt
misc: pg enable metrics
fix: Img scan bug fixes
misc: Main sync develop 13jan
chore: Sync main develop
fix: remove unused variable causing double register in prometheus
* common client implementation * ea wire gix * removing imports * fixing comment * review changes
|
| GitGuardian id | GitGuardian status | Secret | Commit | Filename | |
|---|---|---|---|---|---|
| 14998970 | Triggered | Generic Password | de8652b | client/argocdServer/repoCredsK8sClient/repositoryCredsManager.go | View secret |
| 10220829 | Triggered | Generic High Entropy Secret | 2974559 | charts/devtron/values.yaml | View secret |
| 463396 | Triggered | Generic Password | 9672e0f | pkg/chartRepo/ChartRepositoryService.go | 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.
|
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 #
Checklist:
Does this PR introduce a user-facing change?