ref(msteams): Replace legacy configure view with the pipeline redirect#116520
Open
evanpurkhiser wants to merge 2 commits into
Open
Conversation
Now that the API-driven pipeline is in place and the frontend can drive the install modal, route `/extensions/msteams/configure/` through a small `RedirectView` that forwards `signed_params` to `/extensions/msteams/link/`, where the modal takes over. The URL has to keep resolving because the Sentry-Teams bot card has it baked in as the install link. - Adds `MsTeamsConfigureRedirectView` and points the configure route at it. - Drops the legacy `MsTeamsExtensionConfigurationView`, the no-op `MsTeamsPipelineView`, and the legacy-flow tests. `get_pipeline_views()` now returns an empty list; the API step is the only setup path. - `build_integration` reads top-level pipeline state directly now that the legacy view (which bound state under `state["msteams"]`) is gone. Fixes [VDY-101: Microsoft Teams: API-driven integration setup](https://linear.app/getsentry/issue/VDY-101/microsoft-teams-api-driven-integration-setup)
evanpurkhiser
requested review from
Christinarlong and
thetruecpaul
and removed request for
a team
github-actions
Bot
added
the
Scope: Backend
github-actions
Bot
added
the
Scope: Frontend
Contributor
|
🚨 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 |
Contributor
📊 Type Coverage Diff✅ No new type safety issues introduced. Coverage: 93.59% |
wedamija
approved these changes
May 29, 2026
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
2 participants
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.
Now that the API-driven pipeline is in place (#116490) and the frontend can drive the install modal (#116488), route
/extensions/msteams/configure/through a smallRedirectViewthat forwardssigned_paramsto/extensions/msteams/link/, where the modal takes over. The URL has to keep resolving because the Sentry-Teams bot card has it baked in as the install link.MsTeamsConfigureRedirectViewand points the configure route at it.MsTeamsExtensionConfigurationView, the no-opMsTeamsPipelineView, and the legacy-flow tests.get_pipeline_views()now returns an empty list; the API step is the only setup path.build_integrationreads top-level pipeline state directly now that the legacy view (which bound state understate["msteams"]) is gone.Fixes VDY-101: Microsoft Teams: API-driven integration setup