Conversation
github-actions
Bot
added
the
Scope: Backend
This was referenced Sep 17, 2026
shashjar
force-pushed
the
shashjar/iswf-3361-control-context-defaults
branch
from
September 17, 2026 22:23
1d43a7a to
cece4a6
Compare
shashjar
force-pushed
the
shashjar/iswf-3361-lightweight-access
branch
from
September 17, 2026 22:23
66dffbb to
1eb9129
Compare
Default control organization endpoints to lightweight RPC contexts, with independent opt-ins for endpoints that need projects or teams. Cover both organization route forms and preserve member access. Refs ISWF-3361
shashjar
force-pushed
the
shashjar/iswf-3361-lightweight-access
branch
from
September 17, 2026 23:02
1eb9129 to
ecc1d43
Compare
shashjar
force-pushed
the
shashjar/iswf-3361-control-context-defaults
branch
from
September 17, 2026 23:02
cece4a6 to
7789122
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Control organization endpoints now omit full project/team collections by default, removing the eager hydration that occurred before
determine_accessreceived an existing RPC context. Endpoints that consume either collection can explicitly opt in through their existing independent flags.Deploy after PR 2's lazy privileged-access lookups and PR 3's getsentry broadcast project opt-in. The general organization service keeps its existing defaults for integration/pipeline consumers that independently fetch full organizations. This is the final change in the scoped fix for ISWF-3361; the organization/member lookup itself remains in place.
Regression coverage verifies both organization-slug and organization-ID routes, authorization with omitted collections, and independent project/team opt-ins. Integration and broadcast tests validate the dependent consumers.
Requires https://github.com/getsentry/getsentry/pull/22065
Part 4 of 4. Fixes ISWF-3361. Review/deploy order: 1: ID RPCs → 2: access checks → 3: broadcasts → 4: control defaults. The Git base is PR 2 because PR 3 lives in getsentry.