ref(integrations): Remove unused legacy extension configuration view#117338
Merged
evanpurkhiser merged 1 commit intoJun 10, 2026
Conversation
`IntegrationExtensionConfigurationView` (and its `ExternalIntegrationPipeline` helper) backed the legacy server-rendered `/extensions/<slug>/configure/` install flow. Every provider now installs through the API-driven pipeline, the configure URL no longer routes to this view, and nothing in sentry or getsentry references it.
github-actions
Bot
added
the
Scope: Backend
evanpurkhiser
commented
Jun 10, 2026
Member
Author
There was a problem hiding this comment.
It was a base view, so there were no URLs pointing at it
evanpurkhiser
deleted the
evanpurkhiser/ref-integrations-remove-unused-legacy-extension-configuration-view
branch
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.
IntegrationExtensionConfigurationView(and itsExternalIntegrationPipelinehelper) backed the legacy server-rendered/extensions/<slug>/configure/install flow. Every provider now installs through the API-driven pipeline, the configure URL no longer routes to this view, and nothing in sentry or getsentry references it — so it's dead code.Part of retiring the legacy install path now that all integration providers are API-driven. The broader legacy web-pipeline machinery is intentionally left in place for now (still shared with auth/SSO, and being retired provider-by-provider).
Part of VDY-32.