fix: smarter fallback team selection for scope inference#120
fix: smarter fallback team selection for scope inference#120
Conversation
… is part of as a fallback
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Instead of always falling back to the username, prefer the user's configured default team (defaultTeamId). Falls back to username when defaultTeamId is not set. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
gr2m
changed the title
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
gr2m
changed the title
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
![vercel[bot]](https://avatars.githubusercontent.com/in/8329?s=60&v=4){kind=small}
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
marc-vercel
left a comment
marc-vercel
left a comment
There was a problem hiding this comment.
Overall LGTM, left 3 comments (two of them are optional).
I see that the tests mock the API response, but given that we are changing API requests/responses, have we manually tested all the flows? If possible I would love to have some integration tests, but because we are dealing with auth I do not think it will be easy.
|
|
||
| throw new NotOk({ | ||
| statusCode: 403, | ||
| responseText: `Authenticated as "${username}" but none of the available teams allow sandbox creation. Specify a team explicitly with --scope <team-id-or-slug>.`, |
There was a problem hiding this comment.
Not a blocker: it would be nice to know which teams have we tried.
| ): Promise<{ candidateTeamIds: string[]; username: string }> { | ||
| const [userData, teamsData] = await Promise.all([ | ||
| fetchApi({ token, endpoint: "/v2/user" }).then(UserSchema.parse), | ||
| fetchApi({ token, endpoint: "/v2/teams?limit=100" }).then( |
There was a problem hiding this comment.
What happens if the user has more than 100 teams? I understand we are just covering the first 100 teams.
This is unlikely, but we should iterate on that. Not a blocker.
| token: opts.token, | ||
| endpoint: `/v11/projects?slug=${encodeURIComponent(teamId)}`, | ||
| token, | ||
| endpoint: `/v11/projects?${teamParam}`, |
There was a problem hiding this comment.
Does this API endpoint ensures that the user can read sandboxes? Afaik it just checks that the user can read the project no?
For example, we require the Resource.VercelSandbox scope at the API level to read a sandbox.
2 participants
Summary
/v2/userand/v2/teamsin parallel to build an ordered list of candidate teams for scope inferenceuser.defaultTeamIdfirst, then falls back to the best hobby-plan OWNER team (personal team matching username, or most recently updated)billing.plan === 'hobby'andmembership.role === 'OWNER'to avoid selecting pro/enterprise teams