Repository navigation
Conversation
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-control-context-defaults
branch
from
September 17, 2026 23:02
cece4a6 to
7789122
Compare
shashjar
added this pull request to stack #125109
September 21, 2026 19:50
Contributor
|
This pull request has gone three weeks without activity. In another week, I will close it. But! If you comment or otherwise update it, I will reset the clock, and if you add the label "A weed is but an unloved flower." ― Ella Wheeler Wilcox 🥀 |
Member
Author
|
WIP |
shashjar
force-pushed
the
shashjar/iswf-3361-control-context-defaults
branch
from
October 21, 2026 21:25
7789122 to
68a43d3
Compare
Contributor
Sentry Snapshot Testing
|
Default control organization endpoints to lightweight RPC contexts with explicit resource opt-ins. Validate service-account grants using active project IDs and inherit the new integration defaults. Refs ISWF-3361
shashjar
force-pushed
the
shashjar/iswf-3361-control-context-defaults
branch
from
October 21, 2026 22:11
68a43d3 to
4c385d8
Compare
shashjar
marked this pull request as ready for review
October 21, 2026 22:16
Christinarlong
approved these changes
Oct 22, 2026
Christinarlong
left a comment
Contributor
There was a problem hiding this comment.
claude do we need all these tests
shashjar
marked this pull request as draft
October 23, 2026 20:04
Use access contexts for control organization endpoints and remaining Sentry App and organization-user callers. Validate only submitted active service-account project IDs, and remove collection hydration flags. Refs ISWF-3361
Carry the provider simplification through the stack and keep the no-hydration guard on the helper. Refs ISWF-3361
Adapt lightweight access to persisted service accounts, bound submitted grants, and migrate the remaining user integration lookup. Refs ISWF-3361
Refs ISWF-3361
Refs ISWF-3361
This branch was successfully deployed
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
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.
Refs https://linear.app/getsentry/issue/ISWF-3361/determine-access-hydrates-every-project-and-team-on-31percent-of-all.
Control organization endpoints now use the dedicated access context, removing eager project/team hydration and collection opt-in flags. Migrate remaining Sentry App, organization-user, and user-integration lookups that need only access metadata. Privileged integration requests now receive the correct resource IDs instead of empty collections.
Service-account create/update validation checks only submitted, accessible IDs against active projects in the organization. Cap requests at 1,000 entries and deduplicate before the RPC; GET, empty grants, and feature-disabled requests skip validation.