feat(vercel): Add API-driven pipeline backend for Vercel integration setup#113094
Open
evanpurkhiser wants to merge 1 commit intomasterfrom
Open
Conversation
github-actions
bot
added
the
Scope: Backend
![sentry[bot]](https://avatars.githubusercontent.com/in/12637?s=60&v=4){kind=small}
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 070a285. Configure here.
evanpurkhiser
force-pushed
the
evanpurkhiser/feat-vercel-add-api-driven-pipeline-backend-for-vercel-integration-setup
branch
from
070a285 to
a4d513a
Compare
wedamija
reviewed
Apr 16, 2026
Member
wedamija
left a comment
wedamija
left a comment
There was a problem hiding this comment.
Does this need any tests? probably it'd be good to have a test to valdiate that the user id is present?
…setup Implement `get_pipeline_api_steps()` on `VercelIntegrationProvider` using a single OAuth2 step, mirroring the Slack pattern. Adds the `oauth_authorize_url` to `VercelIdentityProvider` (previously unset since the legacy flow is initiated externally). Updates `build_integration()` to handle both legacy `state["identity"]["data"]` and new `state["oauth_data"]` paths, and falls back to `state["uid"]` for `user_id` in the API flow. Note: Vercel currently has `can_add = False` so the API pipeline cannot be initialized from the frontend yet. This wiring prepares for the upcoming external install UI flow. Ref [VDY-44](https://linear.app/getsentry/issue/VDY-44/vercel-api-driven-integration-setup)
evanpurkhiser
force-pushed
the
evanpurkhiser/feat-vercel-add-api-driven-pipeline-backend-for-vercel-integration-setup
branch
from
a4d513a to
e3dda6a
Compare
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.
Implement
get_pipeline_api_steps()onVercelIntegrationProviderusinga single OAuth2 step, mirroring the Slack pattern. Adds the
oauth_authorize_urltoVercelIdentityProvider(previously unset sincethe legacy flow is initiated externally). Updates
build_integration()tohandle both legacy
state["identity"]["data"]and newstate["oauth_data"]paths.
Note: Vercel currently has
can_add = Falseso the API pipeline cannotbe initialized from the frontend yet. This wiring prepares for the
upcoming external install UI flow.
Ref VDY-44