Platform deployment fails with generic API token error
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 56/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- typescript
Research direction
Start at the CLI code that prompts for and validates the Cloudflare management API token, then read how Cloudflare reports token permission and scope failures. The report should identify missing permissions or incorrect scopes when deployment is blocked; verify it using the deployment flow described in the issue.
Written by the indexing model from the issue text.
Description
Trying to deploy the platform to Cloudflare, I am brought to the prefilled API token generation page. I keep all the permissions and scope them to the specific domain per the CLI instructions. Upon pasting the token in.
Change the zone policy from All Domains to Specified Domains → customdomain.app.
◇ Paste management API token:
▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▲ Cloudflare rejected this token. Check its permissions and account/zone scope, then paste a replacement.
Creating a token with no scope limits generates the same generic error. I am unable to deploy the platform and there is no useful feedback on what the permission or scoping issue is. The CLI should report what permissions are missing or what scopes are incorrect.
- Dominant language
- TypeScript
- Stars
- 402
- Forks
- 32
- Avg merge
- 12h 1m
- Merged PRs (30d)
- 80
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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 voidzero-dev/void
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
voidzero-dev/void#484 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
voidzero-dev/void#463 ·
Maintainers usually reply within 1 day
-
Deploy after a secret change fails for Workers over ~750 KB: source read-back capped at 1 MiBPossibly taken @Brooooooklyn claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
voidzero-dev/void#459 · 1 assignee ·
Maintainers usually reply within 1 day
-
bug
Difficulty 1/5 1-3 hours Newbie friendliness 78/100
voidzero-dev/void#428 ·
Maintainers usually reply within 1 day
-
Allow `npm create void` and `void init` to run without promptsPossibly taken @ashunar0 claimed this today. Open
Difficulty 4/5 3-5 days Newbie friendliness 57/100
voidzero-dev/void#491 · 1 comment ·
Maintainers usually reply within 1 day
All issues in voidzero-dev/void
Similar issues
-
[测试] 等待仓库加载后再记录多仓库排序基线Possibly taken @myot233 claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
area:arcade p3-medium ready-for-agent testing type:docs
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
fderuiter/deruiter.dev#2369 ·
Maintainers usually reply within 1 day
-
area:devenv origin:agent type:bug
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
overengineeringstudio/effect-utils#1949 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
ccch1mneyyy/dsh-TUI#1631 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
MiniMax-AI/minimax-code#507 ·
Maintainers usually reply within 1 day