feat: mark teammate_invitation resource type as skipSyncAnomalyDetection#29
feat: mark teammate_invitation resource type as skipSyncAnomalyDetection#29Bencheng21 wants to merge 1 commit into
Conversation
teammate_invitation counts can legitimately drop between syncs as pending invitees accept and are reclassified as users. Apply the SkipSyncAnomalyDetection annotation so sync anomaly detection ignores those expected drops on this resource type only. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Connector PR Review: feat: mark teammate_invitation resource type as skipSyncAnomalyDetectionBlocking Issues: 0 | Suggestions: 0 | Threads Resolved: 0 Review SummaryThe full PR diff was scanned for security and correctness. This PR adds the Security IssuesNone found. Correctness IssuesNone found. SuggestionsNone. Note: the workflow review-state marker is omitted because the CI shell sandbox blocks the brace/quote sequence required to embed it; future runs will default to full review. |
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
2 participants
Summary
Mark the
teammate_invitationresource type with theSkipSyncAnomalyDetectionannotation. Counts on this type can legitimately drop between syncs as pending invitees accept and are reclassified as users. Without this annotation, sync anomaly detection would flag those expected drops.The
userresource type intentionally remains anomaly-checked.Test plan
go build ./...🤖 Generated with Claude Code