-
Notifications
You must be signed in to change notification settings - Fork 55
Add ProxySQL MariaDB doc & Update ProxySQL MySQL doc #749
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
base: master
Are you sure you want to change the base?
Conversation
Visit the preview URL for this PR (updated for commit bf72a74): https://kubedb-v2-hugo--pr749-proxy-1f2u7q4b.web.app (expires Wed, 23 Apr 2025 07:02:14 GMT) 🔥 via Firebase Hosting GitHub Action 🌎 Sign: 0f29ae8ae0bd54a99bf2b223b6833be47acd5943 |
7623e2e
to
f2185be
Compare
2f9ee61
to
cec6574
Compare
|
GitGuardian id | GitGuardian status | Secret | Commit | Filename | |
---|---|---|---|---|---|
5161057 | Triggered | RSA Private Key | e02a6d5 | docs/guides/proxysql/backends/xtradb-galera/external/index.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 secret safely. Learn here the best practices.
- Revoke and rotate this secret.
- 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.
Signed-off-by: Neaj Morshad <[email protected]>
Signed-off-by: Neaj Morshad <[email protected]>
Signed-off-by: Neaj Morshad <[email protected]>
Signed-off-by: Neaj Morshad <[email protected]>
Signed-off-by: Neaj Morshad <[email protected]>
Signed-off-by: Neaj Morshad <[email protected]>
Signed-off-by: Neaj Morshad <[email protected]>
Signed-off-by: Neaj Morshad <[email protected]>
Signed-off-by: Neaj Morshad <[email protected]>
Signed-off-by: Neaj Morshad <[email protected]>
No description provided.