feat(backend): add Redis distributed cache for plan metadata#643
feat(backend): add Redis distributed cache for plan metadata#643od-hunter wants to merge 1 commit into
Conversation
Introduce PlanCacheService with write-through caching, single-flight protection, Prometheus metrics, and cache warming on deploy. Wire into GraphQL loaders, REST plan endpoints, and a new backend server entry point with Redis/Postgres docker-compose support.
|
@od-hunter Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits. You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀 |
|
| GitGuardian id | GitGuardian status | Secret | Commit | Filename | |
|---|---|---|---|---|---|
| - | - | Generic Password | fbb20e6 | backend/config/tests/redis.test.ts | View secret |
| 15742864 | Triggered | Generic Password | fbb20e6 | docker-compose.yml | View secret |
| 15762030 | Triggered | Generic Password | fbb20e6 | docker-compose.yml | 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.
Closes #592