Conversation
693996a to
da8b0c5
Compare
|
@cpetersen5 @ameijer Let me know if you need any assistance with the NGINX config! It looks like the main changes in this config file, are to remove all routing towards the |
|
| GitGuardian id | GitGuardian status | Secret | Commit | Filename | |
|---|---|---|---|---|---|
| 5478002 | Triggered | Microsoft Teams webhook | 1f1da34 | cost-analyzer/templates/cost-analyzer-frontend-config-map-template.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 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.
|
This pull request has been marked as stale because it has been open for 90 days with no activity. Please remove the stale label or comment or this pull request will be closed in 5 days. |
Release Notes Headline
Commentary for Reviewers
Links to Issues or Tickets
User Impact and Risks
Testing
Documentation Updates