BED-9520: Make source_kind optional and remove it from the OG metadata - #75
Conversation
…it to the node's list of kinds instead
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (10)
Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review. Walkthrough
ChangesSource kind flow
Estimated code review effort: 2 (Simple) | ~10 minutes Merge Risk: ⚪ Minimal · up to The change is merge-ready after normal checks and review; no actionable merge-blocking risk remains. Poem
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✨ Finishing Touches 💡 1📝 Generate docstrings 💡
🧪 Generate unit tests (beta)
Comment |
Summary
When a
source_kindis present in the OpenGraph (metadata) output, edges directing to existing BloodHound nodes will overwrite the target node’s base kind. Ie. if the Github collector creates an edge to an Azure/AD node, the Azure/AD node will automatically inherit Github’ssource_kind.Motivation
Resolves: BED-9520
Changes
This change makes
source_kindoptional, and when defined, thesource_kindis appended it to each node during conversion instead of adding it to the metadata. This still allows developers to add a base kind while fixing the overwriting issue.Summary by CodeRabbit
New Features
Changes