Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

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

Abierto
  • ¿Algo no está bien?
#347 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
58/100
Tipo de issue
Nueva funcionalidad
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
typescript
Área
api, cli

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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

Lenguaje dominante
TypeScript
Estrellas
916
Forks
53
Merge medio
19 h 13 min
PR fusionados (30 d)
185

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de cloudflare/cf

Todos los issues de cloudflare/cf

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.