Skip to content

Seed Linear and Spotify OAuth creds in local dev - #90

Open
sizukutamago wants to merge 1 commit into
cloudflare:mainfrom
sizukutamago:fix/run-local-linear-spotify-creds
Open

Seed Linear and Spotify OAuth creds in local dev#90
sizukutamago wants to merge 1 commit into
cloudflare:mainfrom
sizukutamago:fix/run-local-linear-spotify-creds

Conversation

@sizukutamago

@sizukutamago sizukutamago commented Aug 8, 2026

Copy link
Copy Markdown

Problem

run-dev-server.js injects CLIENT_ID / CLIENT_SECRET into each OAuth gatekeeper's generated wrangler.dev.jsonc via the SHARED_GATEKEEPER_CREDS table, but the table covers only 8 of the 10 gatekeepers that read env.CLIENT_IDLinear and Spotify are missing.

So in a local run (pnpm run-local), putting LINEAR_CLIENT_ID / LINEAR_CLIENT_SECRET (or the SPOTIFY_* equivalents) in the root .dev.vars silently does nothing, and connecting either service always lands on the "Configuration Required" page — while the identical setup works for the other eight gatekeepers.

Fix

Add the two missing rows. Verified locally: after this change the generated packages/gatekeeper-linear/wrangler.dev.jsonc contains the injected CLIENT_ID, and the Linear connect flow proceeds past the configuration check exactly like the already-covered gatekeepers.

run-dev-server.js injects CLIENT_ID / CLIENT_SECRET into each OAuth
gatekeeper's generated wrangler.dev.jsonc via SHARED_GATEKEEPER_CREDS,
but the table covers only 8 of the 10 gatekeepers that read
env.CLIENT_ID: Linear and Spotify are missing.

As a result, setting LINEAR_CLIENT_ID / LINEAR_CLIENT_SECRET (or the
SPOTIFY_* equivalents) in the root .dev.vars has no effect, and
connecting either service in a local run always fails with the
"Configuration Required" page, while the same setup works for the
other eight gatekeepers.

Every other OAuth gatekeeper added its own row in the same commit
that introduced the package (e.g. Notion in b15cf33); the Linear and
Spotify commits (d25d250, 24331ce) landed back-to-back the same day
and both skipped that step, so this looks like an oversight rather
than a deliberate exclusion.

Verified locally: with this change the generated
packages/gatekeeper-linear/wrangler.dev.jsonc contains the injected
CLIENT_ID and the connect flow proceeds past the configuration check.
@github-actions

github-actions Bot commented Aug 8, 2026

Copy link
Copy Markdown

All contributors have signed the CLA ✍️ ✅
Posted by the CLA Assistant Lite bot.

@sizukutamago

Copy link
Copy Markdown
Author

I have read the CLA Document and I hereby sign the CLA

github-actions Bot added a commit that referenced this pull request Aug 8, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant