fix: drop appId uppercasing in AppRoleAssignment.MarshalJSON (BED-9235) - #205
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
💤 Files with no reviewable changes (1)
WalkthroughThe change preserves ChangesApp role assignment serialization
Estimated code review effort: 1 (Trivial) | ~2 minutes Possibly related PRs
Suggested reviewers: Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Comment |
Description
BED-9100 (
c8fdff7) uppercasedappId, butappIdis a constant-match key, not a node endpoint. BHE compares it verbatim against the lowercase Microsoft Graph app id (00000003-0000-0000-c000-000000000000) via a case-sensitive==to build theAZMG*edges. Uppercasing broke that match and silently dropped ~2.29M edges. This revertsappIdto the casing every other producer already emits (v3.0.0, BARK, the Graph API).resourceId/tenantId/principalIdstay uppercased — those are real endpoints the raw-ingest path needs.Fixed in the collector (not BHE) because the regression is collector-side and this works against all existing BHE versions with no deploy.
Motivation and Context
Resolves: BED-9235
Changes
Impact
Testing
go build ./...andgo test ./...pass.use_raw_object_idis a no-op); allAZMG*kinds match the v3.0.0 baseline. Residual 115/10-edge diff vs v3.0.0 is collection-time tenant drift, not a code difference.Summary by CodeRabbit