Conversation
- Complete notification microservice implementation - Email notification service with SMTP configuration - Push notification support - Subscription management - Template system for notifications - Data seeder with sample notifications - OpenAPI/Swagger documentation - Comprehensive DTOs and entities - Full CRUD operations for notifications - Email configuration with SendGrid/SMTP support
feat: Enhance role handling in GatewayHeaderFilter to include SUPER_ADMIN as ADMIN
…ying Notification Service to Kubernetes
feat: Add GitHub Actions workflows for building, packaging, and deploying Notification Service to Kubernetes
|
| GitGuardian id | GitGuardian status | Secret | Commit | Filename | |
|---|---|---|---|---|---|
| 22222399 | Triggered | SMTP credentials | 3e6908b | notification-service/src/main/resources/application.properties | View secret |
| 22222401 | Triggered | SMTP credentials | 3e6908b | notification-service/src/main/resources/application-dev.properties | 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.
|
Warning Rate limit exceeded@RandithaK has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 25 minutes and 52 seconds before requesting another review. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. 📒 Files selected for processing (39)
✨ Finishing touches
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
No description provided.