Repository navigation
Worker identifier is spelled three ways across cf workers commands (<worker-id>, --worker-id, --worker) #345
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
Activity