refactor: use duty config change dedupe#2219
Conversation
Config change dedupe now lives in duty with the shared fingerprint cache and dedupe behavior. Delegate cache initialization and dedupe decisions to duty, keeping a temporary compatibility shim while config-db still uses its local ConfigChange model in the scrape pipeline.
|
Important Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
✨ Simplify code
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 |
BenchstatBase: 📊 2 minor regression(s) (all within 5% threshold)
✅ 1 improvement(s)
Full benchstat output |
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
Config change dedupe has moved to duty so the fingerprint cache and dedupe behavior can be shared.
Delegate cache initialization and dedupe decisions to duty, while keeping a temporary compatibility shim for config-db's local ConfigChange model.
Depends on flanksource/duty#1971.