Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

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

Aperta
  • Qualcosa non va?
#347 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
58/100
Tipo di issue
Funzionalità
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
typescript
Ambito
api, cli

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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).

Lingua principale
TypeScript
Stelle
853
Fork
42
Merge medio
17h 57m
PR unite (30g)
146

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di cloudflare/cf

Tutte le issue di cloudflare/cf

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.