gitguardian[bot]
commented
2 weeks ago ⚠️ GitGuardian has uncovered 2 secrets following the scan of your pull request.
Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.
Since your pull request originates from a forked repository, GitGuardian is not able to associate the secrets uncovered with secret incidents on your GitGuardian dashboard. Skipping this check run and merging your pull request will create secret incidents on your GitGuardian dashboard.
🔎 Detected hardcoded secrets in your pull request
| GitGuardian id | GitGuardian status | Secret | Commit | Filename | | | -------------- | ------------------ | ------------------------------ | ---------------- | --------------- | -------------------- | | [-](https://dashboard.gitguardian.com/workspace/581432/incidents/secrets) | - | Google API Key | 48533a0f669410b6c0f0710d2d53187b92b7eed2 | Dockerfile | [View secret](https://github.com/mahaveergurjar/Chatbot/commit/48533a0f669410b6c0f0710d2d53187b92b7eed2#diff-dd2c0eb6ea5cfc6c4bd4eac30934e2d5746747af48fef6da689e85b752f39557R38) | | [-](https://dashboard.gitguardian.com/workspace/581432/incidents/secrets) | - | Google API Key | ed770e2e30aa930ec824ae3c51d8ac1f555a76c5 | Dockerfile | [View secret](https://github.com/mahaveergurjar/Chatbot/commit/ed770e2e30aa930ec824ae3c51d8ac1f555a76c5#diff-dd2c0eb6ea5cfc6c4bd4eac30934e2d5746747af48fef6da689e85b752f39557L38) |
🛠 Guidelines to remediate hardcoded secrets
1. Understand the implications of revoking this secret by investigating where it is used in your code. 2. Replace and store your secrets safely. [Learn here](https://blog.gitguardian.com/secrets-api-management?utm_source=product&utm_medium=GitHub_checks&utm_campaign=check_run_comment) the best practices. 3. Revoke and [rotate these secrets](https://docs.gitguardian.com/secrets-detection/secrets-detection-engine/detectors/specifics/googleaiza#revoke-the-secret?utm_source=product&utm_medium=GitHub_checks&utm_campaign=check_run_comment). 4. If possible, [rewrite git history](https://blog.gitguardian.com/rewriting-git-history-cheatsheet?utm_source=product&utm_medium=GitHub_checks&utm_campaign=check_run_comment). 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](https://blog.gitguardian.com/secrets-api-management/?utm_source=product&utm_medium=GitHub_checks&utm_campaign=check_run_comment) for managing and storing secrets including API keys and other credentials - install [secret detection on pre-commit](https://docs.gitguardian.com/ggshield-docs/integrations/git-hooks/pre-commit?utm_source=product&utm_medium=GitHub_checks&utm_campaign=check_run_comment) 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.
mahaveergurjar
vigneshs-dev
Hi @mahaveergurjar ,
After researching and spending so much time on this issue, I come through a way to Dockerize Chatbot. But there are some issues during running Docker image. As I have Windows system, I experience some errors. I found that the Docker image may run perfectly on Linux / MacOS systems. If you are able to test it on such systems, please do further.
I am experiencing above error mainly due to WSL running in my Windows system.
Please do the necessary. I added the steps to build and run docker file in the README. Thankyou for giving me this opportunity.