-
Notifications
You must be signed in to change notification settings - Fork 21
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
Add ZooKeeper Metrics Configurations #843
Conversation
e9bf563
to
58656be
Compare
9ccb413
to
53d9cce
Compare
58656be
to
60bbc56
Compare
60bbc56
to
9684807
Compare
|
GitGuardian id | GitGuardian status | Secret | Commit | Filename | |
---|---|---|---|---|---|
9771084 | Triggered | Grafana Token | f2040e4 | charts/kubedb-grafana-dashboards/README.md | View secret |
9771084 | Triggered | Grafana Token | 925eb64 | charts/kubedb-grafana-dashboards/README.md | 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!
2051253
to
37447dc
Compare
Signed-off-by: Shaad7 <[email protected]>
Signed-off-by: AbdullahAlShaad <[email protected]>
Signed-off-by: AbdullahAlShaad <[email protected]>
Signed-off-by: AbdullahAlShaad <[email protected]>
Signed-off-by: raihankhan <[email protected]>
Signed-off-by: raihankhan <[email protected]>
Signed-off-by: Arnob kumar saha <[email protected]>
Signed-off-by: AbdullahAlShaad <[email protected]>
Signed-off-by: Arnob kumar saha <[email protected]>
Signed-off-by: Arnob Kumar Saha <[email protected]>
No description provided.