Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(hybridcloud) Fix cross-silo query in project rule details #61435

Merged
merged 1 commit into from
Dec 11, 2023

Conversation

markstory
Copy link
Member

In project rule details we hydrate a detached SentryAppInstallation record to shim up ui component behavior. Preparing ui components requires going from the install to sentryapp which emits a cross silo query in test silos. We haven't been able to catch this in tests before because we don't patch association properties.

To get this working I've hydrated a detached SentryApp record. The entire prepare_ui component flow needs to be rebuilt with Rpc models to remove this cruft and that is a bigger undertaking than we have time for today. I've ticketed the follow up work for us to complete later.

Fixes HC-1023

In project rule details we hydrate a detached SentryAppInstallation
record to shim up ui component behavior. Preparing ui components
requires going from the install to sentryapp which emits a cross silo
query in test silos. We haven't been able to catch this in tests before
because we don't patch association properties.

To get this working I've hydrated a detached SentryApp record. The
entire prepare_ui component flow needs to be rebuilt with Rpc models to
remove this cruft and that is a bigger undertaking than we have time for
today.

Fixes HC-1023
@markstory markstory requested a review from a team December 8, 2023 17:18
@markstory markstory requested a review from a team as a code owner December 8, 2023 17:18
@github-actions github-actions bot added the Scope: Backend Automatically applied to PRs that change backend components label Dec 8, 2023
markstory added a commit that referenced this pull request Dec 8, 2023
There are two sentryapp API endpoints (requests/interactions) that store
data in the creating org's region. These endpoints need to be proxied to
the region where the sentryapp was created for now. I found this while
working on #61435

Refs HC-1023
Copy link
Contributor

@corps corps left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Alternatively, we did discuss refactoring the modeling of SentryApps, with region replicated "summary" models that put the relevant stuff together, too.

Honestly, I favor thinking refactoring SentryApp modeling because there are many, problems with its current design that mostly just require aggregating the modeling into a simpler design.

But I agree that's not your work for now.

@markstory
Copy link
Member Author

Honestly, I favor thinking refactoring SentryApp modeling because there are many, problems with its current design that mostly just require aggregating the modeling into a simpler design.

This is the path I want to take as well, but it requires building new RPC model based code paths first.

markstory added a commit that referenced this pull request Dec 8, 2023
There are two sentryapp API endpoints (requests/interactions) that store
data in the creating org's region. These endpoints need to be proxied to
the region where the sentryapp was created for now. I found this while
working on #61435

Refs HC-1023
@markstory markstory merged commit 83c9e95 into master Dec 11, 2023
@markstory markstory deleted the fix-projectrule-silo branch December 11, 2023 15:09
@github-actions github-actions bot locked and limited conversation to collaborators Dec 27, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Scope: Backend Automatically applied to PRs that change backend components
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants