-
Notifications
You must be signed in to change notification settings - Fork 9
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
1023 develop -> release ( v3.1.0 ) #274
Conversation
git-flow start
S3support dev에서 테스트를 위해 임의 merge
s3support: change release name
release -> develop merge (230731)
main merge (20230816)
finish release v3.0.0 ( develop merge from main )
update lma-addson chart version
최소사항 클러스터 지원을 위한 여정
add tks-admin-tools group
Fix byoh chart version
fix typo
bugfix. change release name to tks-apis
Clone ingress nginx
change jaeger cassandra options
Minio의 버킷 생성 명 변경
|
GitGuardian id | Secret | Commit | Filename | |
---|---|---|---|---|
8178259 | Generic Database Assignment | bde3d03 | tks-admin-tools/base/resources.yaml | View secret |
8178259 | Generic Database Assignment | 9d487ae | tks-admin-tools/base/resources.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!
1023 develop -> release ( v3.1.0 )