You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are multiple WORKER entry points in my project. (I do not intend to monorepo...)
I deployed the command option in cloudflare/wrangler-action@v3 with --name and entry points. (I did not write name and main to share wrangler.toml).
However, I got an error where name was not specified in the part where wrangler secret put is executed.
✘ [ERROR] Required Worker name missing. Please specify the Worker name in wrangler.toml, or pass it as an argument with `--name <worker-name>`
I would like to see nameoption formally supported instead of writing it in command.
The text was updated successfully, but these errors were encountered:
Ran into this issue as well. We use --name on our deploys to support feature branch deployments without requiring the addition of an environment to the toml file. When we started using secrets it resulted in the wrong function being updated. To workaround this we now dynamically add the environment as a preCommand step. Would like a cleaner solution.
There are multiple WORKER entry points in my project. (I do not intend to monorepo...)
I deployed the
command
option incloudflare/wrangler-action@v3
with--name
and entry points. (I did not writename
andmain
to sharewrangler.toml
).However, I got an error where
name
was not specified in the part where wrangler secret put is executed.I would like to see
name
option formally supported instead of writing it incommand
.The text was updated successfully, but these errors were encountered: