docs(cloud): document the Vercel asset discovery integration - #240
Open
patrick-projectdiscovery wants to merge 3 commits into
Open
docs(cloud): document the Vercel asset discovery integration#240patrick-projectdiscovery wants to merge 3 commits into
patrick-projectdiscovery wants to merge 3 commits into
Conversation
The Vercel connector shipped in PDCP-67 and has been configurable in the UI since June, but was never documented. The integration wizard's own "Docs" button links to cloud/integrations#vercel, an anchor that did not exist, and its footer points at the Cloudlist providers page, which also had no Vercel entry. Adds a Vercel section to both, covering the two supported services (deployments, domains), how token scope interacts with the Team ID field, and what the integration does not enumerate. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Automations to automatically generate PRs for you. |
The configure flow this section links to renders vercelForm, which asks only for API Access Token, Team ID and Integration Name. The Services selector exists on the Integrations page wizard, not here, so the step telling users to pick services was wrong for the linked flow. With no services set, Cloudlist's ResolveServices defaults to every supported service, so both deployments and domains are enumerated. Say that, and point at the two places where the set can actually be narrowed. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Every other connector section carries one. Matches the existing convention: panel screenshot at 65% width, placed between the configure Card and the intro paragraph. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
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
1 participant
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.
The Vercel connector shipped with PDCP-67 and has been configurable in the platform since June, but it was never documented.
Two concrete symptoms:
cloud/integrations#vercel. That anchor did not exist, so it dropped users at the top of the page.What this adds
cloud/integrations.mdx: a### Vercelsection, which creates the#vercelanchor the wizard links to, plus a card in the topCardGroup.opensource/cloudlist/providers.mdx: a Vercel entry with the real config keys,vercel_api_tokenandvercel_team_id.Content is taken from
cloudlist/pkg/providers/verceland thevercelForm/vercelCloudlistWizardcomponents rather than inferred, and covers the two supported services (deployments,domains), the two things the integration deliberately does not enumerate, and how token scope interacts with the Team ID field.That last point is the one worth a reviewer's eye. A Team-scoped Vercel token already carries its team, so the Team ID field stays empty. A Full Account token needs it, or the integration silently enumerates only the personal account. This was not written down anywhere.
Not included here
Three things surfaced while writing this that look like product issues rather than documentation, so they are deliberately not described as intended behaviour:
GET /v8/projectsonce, never settinglimitand never followingpagination.next, while Vercel's list-projects endpoint is paginated. An account with many projects would be truncated silently.v8; Vercel currently documentsv10.Still needed
A screenshot. Every other connector section has one (
images/Fastly_Integration_Screen.pngand friends) and this section has no<img>yet. Happy to addimages/Vercel_integration_screen.pngif someone can grab one.Icon note:
icon="cloud", because Font Awesome's free set has no Vercel mark and this repo only uses free icons.coloris omitted since Vercel's black would disappear in dark mode.🤖 Generated with Claude Code