-
-
Notifications
You must be signed in to change notification settings - Fork 4.5k
chore(cells) Switch ReactView and GenericReactView to control silo #104552
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
base: master
Are you sure you want to change the base?
Conversation
We render the bulk of our HTML via ReactPage. Right now that endpoint is marked as `all_silo` to make integration with tests simpler. Switch these endpoints to control as we're trying to have a minimal number of endpoints marked as `all_silo` and I want to better understand the scope of test failures from this change. Refs INFRENG-238
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #104552 +/- ##
===========================================
+ Coverage 80.52% 80.54% +0.02%
===========================================
Files 9352 9354 +2
Lines 400460 400945 +485
Branches 25696 25696
===========================================
+ Hits 322477 322952 +475
- Misses 77533 77543 +10
Partials 450 450 |
- Change silo mode of UI endpoint tests to be control scoped as ReactPage is now control scoped. - Update a route name to not overlap with the non-customer domain path.
Subclasses of `sentry.web.frontend.base.BaseView` should not be part of the controlsilo URL map because the UI will not make requests to these paths.
|
🚨 Warning: This pull request contains Frontend and Backend changes! It's discouraged to make changes to Sentry's Frontend and Backend in a single pull request. The Frontend and Backend are not atomically deployed. If the changes are interdependent of each other, they must be separated into two pull requests and be made forward or backwards compatible, such that the Backend or Frontend can be safely deployed independently. Have questions? Please ask in the |
| r"^(?P<organization_slug>[^/]+)/projects/(?P<project_id_or_slug>[^/]+)/events/(?P<client_event_id>[^/]+)/$", | ||
| ProjectEventRedirect.as_view(), | ||
| name="sentry-project-event-redirect", | ||
| name="sentry-organization-project-event-redirect", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We had two routes with this name 🫠
In #104552 I want to make `ReactPage` control-only. This change *should* be a no-op for saas, but I want to make sure of that first by validating with real traffic. Refs INFRENG-238
In #104552 I want to make `ReactPage` control-only. This change *should* be a no-op for saas, but I want to make sure of that first by validating with real traffic. Refs INFRENG-238
We render the bulk of our HTML via ReactPage. Right now that endpoint is marked as
all_siloto make integration with tests simpler. Switch these endpoints to control as we're trying to have a minimal number of endpoints marked asall_siloand I want to better understand the scope of test failures from this change.Refs INFRENG-238