Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

No command to view or edit an existing Worker's script settings (vars, observability, logpush, tail consumers)

Open
  • Is something wrong?
#347 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
58/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Tech stack
typescript
Domain
api, cli

Research direction

Start with the cf workers command tree and the existing workers-for-platforms ... scripts settings get/edit implementation, then trace how cf calls the Workers API script-settings endpoints. Add command wiring and tests for retrieving and editing plain-text vars, observability, logpush, tail consumers, and compatibility settings. Done means the new commands expose these operations without requiring a project redeploy and have coverage for successful and invalid requests.

Written by the indexing model from the issue text.

Description

Summary of the issue

There's no command to read or change an existing Worker's settings without redeploying it from a project. The Workers API has script-settings endpoints (/accounts/{account_id}/workers/scripts/{script_name}/settings and /script-settings) for things like plain-text bindings, observability, logpush, tail consumers and compatibility settings. cf calls these internally during deploy, but exposes no command for them:

  • cf cli search for "edit worker script settings", "enable observability logs on an existing worker", or "update compatibility date of deployed worker script settings" only finds the Workers for Platforms equivalents (cf workers-for-platforms dispatch-namespaces scripts settings get / edit).
  • cf workers --help lists check, delete, deployments, get, list, scripts (search only), secrets, triggers, types, versions.

So you can't set or remove a plain-text var, turn on observability, or add a tail consumer on a Worker from the CLI without its source and a full cf deploy. That also makes #197 (deploy deleting vars set outside the config) harder to work around, and there's no CLI way to inspect what a deploy would overwrite.

Expected behaviour

cf workers settings get --worker <name> and cf workers settings edit --worker <name> … (or similar), mirroring the existing workers-for-platforms … scripts settings commands.

Version of cf used

1.0.0-beta.16 (no settings commands in the beta.18 package either)

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
Relevant error logs (optional)

Related: #196 (toggle workers.dev / Preview URLs), #197 (keep_vars).

Dominant language
TypeScript
Stars
853
Forks
42
Avg merge
16h 43m
Merged PRs (30d)
160

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from cloudflare/cf

All issues in cloudflare/cf

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.