Replacement of Google search to googlesearch-python and integration of Proxy. #743
Conversation
|
| GitGuardian id | GitGuardian status | Secret | Commit | Filename | |
|---|---|---|---|---|---|
| - | - | Basic Auth String | e828c70 | notebook.ipynb | View secret |
| - | - | Basic Auth String | 46195d6 | notebook.ipynb | View secret |
| - | - | Username Password | 46195d6 | notebook.ipynb | View secret |
| - | - | Username Password | e828c70 | notebook.ipynb | 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.
|
🎉 This PR is included in version 1.26.0-beta.16 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
|
🎉 This PR is included in version 1.26.0 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
With Google Search, the issue was of too many request if the google search was hit frequently. In the google package, don't have proxy, so replace that with googlesearch-python, and integrated the proxy.