Support on-demand OAuth authorization for PlanetScale signature creation
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 15/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- typescript
- Domain
- authentication, cli
Research direction
The work centers on the cf hyperdrive integration planetscale signature command and the OAuth scope hyperdrive-planetscale:setup, which should be requested only when that command runs. Before writing code, check whether the upstream workers-auth PR #16184 has landed and whether a maintainer accepts the roadmap fit; the closed PR #247 is the earlier attempt. Done means the command requests the scope on demand and existing login and API-token behavior is unchanged.
Written by the indexing model from the issue text.
Description
Hi cf team. Hyperdrive is introducing a dedicated sensitive OAuth scope, hyperdrive-planetscale:setup, for cf hyperdrive integration planetscale signature. This is to support the Hyperdrive x PlanetScale partnership, where customers can create databases that are billed to their Cloudflare account.
Currently, customers cannot use the signature command in cf due to missing the billing scope we enforce on the backend.
The internal Cloudflare changes are in review, and workers-auth PR #16184 makes the scope explicitly requestable without adding it to default login grants.
cf PR #247 requests the scope only when this command needs it, while preserving existing OAuth scopes and API-token behavior. It was automatically closed by the contribution-policy workflow before review.
Does this fit the cf GA roadmap? If so, could someone sponsor/vouch for the change and advise when I should reopen the PR?
- Dominant language
- TypeScript
- Stars
- 853
- Forks
- 42
- Avg merge
- 16h 43m
- Merged PRs (30d)
- 160
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from cloudflare/cf
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
cloudflare/cf#344 ·
Maintainers usually reply within 1 day
-
upstream
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
cloudflare/cf#262 ·
Maintainers usually reply within 1 day
-
`cf dev` rejects `--port` and `--host` for Vite projects, including the `cf init` templatePossibly taken @jamesopstad claimed this 7 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
cloudflare/cf#223 · 2 assignees ·
Maintainers usually reply within 1 day
-
upstream
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
cloudflare/cf#179 ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 58/100
cloudflare/cf#347 ·
Maintainers usually reply within 1 day
Similar issues
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
equinor/prisma-decision-web#919 ·
Maintainers usually reply within 1 day
-
[DC] OneLogin sync imports a partial user list when an API request failsPossibly taken @RaphaelFakhri claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
bitwarden/directory-connector#1276 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
home-assistant/installer#324 ·
Maintainers usually reply within 1 day
-
Mondriaan
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
knaw-huc/textannoviz#733 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day