docs(snowflake): add Snowflake auth provider page - #1115
Open
avoguru wants to merge 4 commits into
Open
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
avoguru
force-pushed
the
docs/snowflake-auth-provider-and-toolkit
branch
from
August 6, 2026 16:52
9db5130 to
45a7274
Compare
Snowflake is configured as a custom OAuth 2.0 provider, since its OAuth endpoints are specific to each account. This documents that setup: creating the security integration in Snowflake, registering it in Arcade, setting the account subdomain secret, and giving each person a role. Each end user signs in to Snowflake themselves, so every query runs under that user's own role, with no shared service account. Adds the provider to the auth-providers catalog page. The sidebar title resolves from the page frontmatter and sorts alphabetically, so no _meta.tsx change is needed. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
avoguru
force-pushed
the
docs/snowflake-auth-provider-and-toolkit
branch
from
August 6, 2026 17:10
45a7274 to
fa526c2
Compare
avoguru
changed the title
evantahler
approved these changes
Aug 6, 2026
The index took `isComingSoon` from the design-system catalog, a hand-maintained constant in a published package. It goes stale the moment a toolkit ships, so a live toolkit keeps rendering as an unavailable card. Snowflake is in that state now: its docs generated and merged in #1114, but the tile still reads "Coming soon". Resolve the flag in `resolveIndexToolkits` from `hasPage` instead. The badge means "there is nothing to read yet", which is exactly what `hasPage` already answers, and the value no longer depends on a package release. This also makes the badge and the sort order agree. `use-toolkit-filters` sorted on the raw design-system flag while the card rendered on `isComingSoon || !hasPage`, so seven toolkits (CloseIO, Discord, GoogleForms, Notion, Obsidian, Twilio, Twitch) showed a "Coming soon" badge while sorting among the available ones. They now sort with the other unavailable toolkits. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
EricGustin
approved these changes
Aug 6, 2026
| // unavailable. Deriving it here also keeps the badge and the sort order | ||
| // (`use-toolkit-filters`) reading the same value, which they previously | ||
| // did not. | ||
| resolved.push({ ...toolkit, hasPage, isComingSoon: !hasPage }); |
The previous head was pushed by github-actions[bot] while regenerating llms.txt. Pushes made with the default GITHUB_TOKEN do not emit a workflow trigger, so the required test and validate_schemas checks never ran against that commit and the PR could not merge despite approval.
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
3 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.
Scoped to the auth provider docs only, now that the auto-generated toolkit docs have merged.
Snowflake is set up as a custom OAuth 2.0 provider, because its OAuth endpoints are specific to each account. This page covers that: creating the security integration in Snowflake, registering it in Arcade, setting the
SNOWFLAKE_ACCOUNT_SUBDOMAINsecret, and giving each person a role.Each end user signs in to Snowflake themselves, so every query runs under that user's own role.
Also adds the provider to the auth-providers catalog page.
🤖 Generated with Claude Code
Note
Low Risk
Documentation and integrations index display logic only; no auth runtime or API behavior changes.
Overview
Adds a Snowflake auth provider reference page and lists it on the auth-providers catalog with a card linking to
/references/auth-providers/snowflake.The new guide walks through per-user OAuth via a Snowflake security integration (provider ID
snowflake), Arcade custom OAuth endpoints (/oauth/token-request), theSNOWFLAKE_ACCOUNT_SUBDOMAINsecret, role grants, MCP gateway usage, and a sampleOAuth2(id="snowflake")tool.On the integrations index,
resolveIndexToolkitsnow setsisComingSoon: !hasPageso shipped toolkits with docs are not stuck behind a stale design-system flag;toolkits-clientpassesisComingSoonfrom that resolved value only.public/llms.txtis regenerated to include the Snowflake auth provider link.Reviewed by Cursor Bugbot for commit 52256e0. Bugbot is set up for automated code reviews on this repo. Configure here.