No command to enable/disable workers.dev and Preview URLs on an existing Worker
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 68/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- typescript
Research direction
Start with the existing cf workers list and cf workers triggers deploy command entry points, then compare their API handling with POST /accounts/{account_id}/workers/scripts/{script_name}/subdomain. Done means an existing Worker can enable or disable workers.dev and Preview URLs without a local project, using the requested settings.
Written by the indexing model from the issue text.
Description
cf version: 1.0.0-beta.12 (macOS)
What I'm trying to do
Turn off the workers.dev route and Preview URLs for an existing Worker that is deployed by Workers Builds from a Git repo. There's no local cf project for it, so editing config and running cf deploy isn't an option.
What I found
cf workers listshowssubdomain.enabledandsubdomain.previews_enabled, but no command changes them.cf cli searchfor "disable workers.dev subdomain for a worker", "workers.dev", "worker subdomain" and "update Worker settings" returns nothing relevant.cf workers triggers deployworks from a local project only.- The API supports it:
POST /accounts/{account_id}/workers/scripts/{script_name}/subdomainwith{"enabled": false, "previews_enabled": false}.
Why it matters
Turning off workers.dev is the quickest way to take a Worker off the public internet, for example one that should only be reachable behind Access. Right now the only options in cf are deleting the Worker or going to the dashboard.
Suggestion
Something like cf workers subdomain update <worker> --enabled false --previews-enabled false, or an update command on cf workers that covers subdomain. Related: cloudflare/workers-sdk#16125.
- Dominant language
- TypeScript
- Stars
- 853
- Forks
- 42
- Avg merge
- 17h 57m
- Merged PRs (30d)
- 146
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 5 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
-
Object parameters lose their structure when resources is enabledPossibly taken @asts-top claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 2 days
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
jaegertracing/jaeger-ui#4618 ·
Maintainers usually reply within 1 day
-
pending close triaging
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
anomalyco/opencode#56765 · 1 comment ·
Maintainers usually reply within 1 day
-
area:plugins enhancement platform:vscode
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
anthropics/claude-code#103166 ·
Maintainers usually reply within 1 day
-
Types: FlashListProps imports ViewabilityConfig from react-native, removed in RN 0.87+Possibly taken @efegokdemir claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Shopify/flash-list#2540 ·