Worker identifier is spelled three ways across `cf workers` commands (`<worker-id>`, `--worker-id`, `--worker`)
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 72/100
- Issue type
- Feature
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- node.js, typescript
- Domain
- cli
Research direction
Start by running the cf workers secrets update, cf workers versions list, and cf workers deployments create examples to compare their accepted worker arguments. Locate the generated command definitions for the 7 commands using --worker-id and 14 using --worker, then check the command-generation and CLI tests. Done means every cf workers command accepts one consistent worker option, with existing options continuing to work as aliases for either a name or ID where supported.
Written by the indexing model from the issue text.
Description
Summary of the issue
Commands under cf workers take the Worker in three different ways:
| Command | How the Worker is passed |
|---|---|
cf workers get, cf workers delete |
positional <worker-id> |
cf workers versions list / get / delete |
--worker-id (required flag) |
cf workers deployments list / create, cf workers secrets list / update / … |
--worker (alias --script-name) |
So the obvious sequence of rolling back after setting a secret uses three spellings:
cf workers secrets update API_KEY --worker my-worker --text …
cf workers versions list --worker-id my-worker
cf workers deployments create --worker my-worker --versions '[…]'
cf workers versions list --worker my-worker fails with Missing required argument: worker-id, and cf workers versions list my-worker fails the same way. The spelling follows each API's path parameter (worker_id vs script_name), which leaks into the CLI. The cf launch post names consistency across commands as a goal, mainly for agents.
In the beta.16 bundle, 7 generated commands define --worker-id and 14 define --worker. beta.18 is the same.
Expected behaviour
One spelling for "which Worker" across cf workers … (e.g. --worker everywhere, accepting a name or ID), with the others kept as aliases.
Version of cf used
1.0.0-beta.16
System information and package versions
cf 1.0.0-beta.16 (also checked in the beta.18 package source)
macOS 27.0 arm64, Node 26.8.2, npm 11.19.1
- 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
-
bug priority: P2
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
mattermost/compass-design#106 ·
Maintainers usually reply within 1 day
-
clawsweeper:needs-maintainer-review clawsweeper:needs-product-decision clawsweeper:no-new-fix-pr clawsweeper:source-repro impact:other issue-rating: 🦞 diamond lobster P2
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
openclaw/openclaw#176671 · 1 comment · 1 reaction ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
nordcraftengine/nordcraft#1400 ·
Maintainers usually reply within 1 day