Set a Worker's cron triggers by name without a local project build
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 65/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- typescript
Research direction
Start at the existing cf workers triggers deploy entry point and the PUT .../workers/scripts/{script_name}/schedules endpoint described in the issue. Trace how commands resolve project configuration, then define the schedules command and its dry-run behavior. Done means cron schedules can be replaced by worker name without a project manifest, and dry-run displays the request.
Written by the indexing model from the issue text.
Description
Version: cf 1.0.0-beta.10
Problem: cf workers triggers deploy only works inside a project that cf can build. In a Worker folder that ships with wrangler.toml but no @cloudflare/vite-plugin or wrangler dependency in its manifest, even --dry-run fails before calling the API:
No Cloudflare dev-server is installed in this project.
A project must declare exactly one of the following in its manifest: ...
There is no way to set a Worker's cron triggers by name without a local build.
Why it matters: Re-applying a cron (PUT .../workers/scripts/{script_name}/schedules) is a common recovery step when a trigger stops firing. Today that needs a full project setup or a hand-written curl call.
Request: something like
cf workers schedules set <worker> --cron "* * * * *" [--cron "*/5 * * * *"]
wrapping PUT .../schedules (replace the whole set), with --dry-run showing the request. It should not depend on a project manifest.
- 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
-
The inspector never shows the instances field, so scaling out is unreachablePossibly taken @Mrkewl claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
xevrion/breakscale#96 ·
Maintainers usually reply within 4 days
-
Object parameters lose their structure when resources is enabledPossibly taken @asts-top claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
rossant/awesome-math#199 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
jaegertracing/jaeger-ui#4618 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
mifi/lossless-cut#3125 ·
Maintainers usually reply within 1 day