feat: add hot CVE topic constants (SUB-7201)#101
Conversation
- HotCVEDefinitionsTopic: hot-cve-definitions-v1 (admin API → ingester) - HotCVEOnFinishPulsarTopic: hot-cve-on-finish-v1 (ingester → UNS) Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
|
Caution Review failedPull request was closed or merged during review No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughTwo new exported string constants were added to the Pulsar topics configuration file: Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Possibly related PRs
Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
🧪 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 |
|
Summary:
|
Summary
Add shared Pulsar topic constants for hot CVE feature:
HotCVEDefinitionsTopic(hot-cve-definitions-v1) — admin API publishes hot CVE definitions, k8s-object ingester consumesHotCVEOnFinishPulsarTopic(hot-cve-on-finish-v1) — ingester publishes after processing, UNS consumes for notificationsThese replace hardcoded string literals in cadashboardbe and event-ingester-service.
SUB-7201
Summary by CodeRabbit