feat: add octolensKeywordMappings table (CM-1833) - #4888
Conversation
Signed-off-by: Uroš Marolt <uros@marolt.me>
PR SummaryLow Risk Overview Rows store Reviewed by Cursor Bugbot for commit 352ceb0. Bugbot is set up for automated code reviews on this repo. Configure here. |
There was a problem hiding this comment.
Copilot review overview
🟡 Changes recommended
The integration foreign key prevents deleting integrations that have mappings unless cascading deletion is added.
Review effort: Balanced
Findings: 1
Open (1)
What changed in this PR
Adds persistence for routing Octolens keyword mentions to CDP segments.
Changes:
- Adds keyword-to-segment mappings scoped by integration.
- Enforces unique integration/keyword pairs.
| File | Description |
|---|---|
V1790929179__octolens-keyword-mappings.sql |
Creates the Octolens keyword mapping table. |
💡 Configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
…M-1833) Signed-off-by: Uroš Marolt <uros@marolt.me>
Signed-off-by: Uroš Marolt <uros@marolt.me>


Summary
Adds the table that maps an Octolens keyword to the CDP segment it should route mentions
into, so a single global Octolens poll can fan out across thousands of projects.
Changes
octolensKeywordMappings(integrationId,segmentId,keywordId,keyword, timestamps; unique on(integrationId, keywordId))Type of change
JIRA ticket
https://linuxfoundation.atlassian.net/browse/CM-1833