yup! `--remote` will work fine, but you'll be dispatching to live user workers at the edge. we have

yup!

--remote

--remote

will work fine, but you'll be dispatching to live user workers at the edge. we have complete local support incoming, where you dispatch to other locally running user workers

Mmrod yup! `--remote` will work fine, but you'll be dispatching to live user workers a...

rob•4/17/24, 8:40 PM

Yes my next question was how we should test users workers before deploying

Walshy•4/17/24, 9:01 PM

My recommendation for user Worker logs is enable logpush and send them to Baselime

Walshy•4/17/24, 9:02 PM

or you can attach a Tail Worker and send them anywhere/manage them as you want

mrodOP•4/17/24, 9:52 PM

here's some docs for local development https://developers.cloudflare.com/cloudflare-for-platforms/workers-for-platforms/get-started/developing-with-wrangler/
this wrangler prerelease branch is experimental, but we're looking to solidify this and get it in soon

Cloudflare Docs

Local development · Cloudflare for Platforms docs

To test your Dispatch Worker, user Worker and Outbound Worker before deploying to production, you can use Wrangler for development and testing.

Mmrod here's some docs for local development https://developers.cloudflare.com/cloudfl...

rob•4/17/24, 9:54 PM

Thanks .. next I'm looking for a good API or to build one for esbuild so I can build customer workers w imports etc.

Rrob Thanks .. next I'm looking for a good API or to build one for esbuild so I can ...

nclevenger•4/17/24, 10:17 PM

Check out https://esb.denoflare.dev

esbuild as an edge service

We run esbuild so you don't have to.

rob•4/17/24, 10:17 PM

oh wow ! Is this reliable ?

nclevenger•4/17/24, 10:17 PM

in my experience it is ... it's run by @John Spurlock

rob•4/17/24, 10:29 PM

Beny•4/18/24, 1:40 AM

Seems like old scripts cant be deleted with error

workers.api.error.unknown

workers.api.error.unknown

.
I tried deleting one which was uploaded a few months ago but it fails, however when I tried (the same way) deleting one that was uploaded this week it worked fine. I tried with the force flag too.

BBeny Seems like old scripts cant be deleted with error `workers.api.error.unknown`. I...

Unsmart•4/18/24, 5:02 AM

Are you on enterprise or did you get it on pay-go before the plan released? Either way sending an account id can probably help an employee look at it when they see it

UUnsmart Are you on enterprise or did you get it on pay-go before the plan released? Eith...

Beny•4/18/24, 5:47 AM

Enterprise & access through tanushree. I was able to resolve it by uploading a new script with the same name then deleting it.

rob•4/19/24, 3:08 PM

wheres the link for buying WfP ? or upgrading from paid workers to that

Rrob wheres the link for buying WfP ? or upgrading from paid workers to that

Acе•4/19/24, 3:17 PM

Click it in navigation on the dashboard and then the button to sign up..

rob•4/19/24, 3:18 PM

yah im not seeing it on my other account hm

Baya•4/19/24, 11:21 PM

I don't see the option to delete secrets in Workers for Platforms API docs. How do you delete secrets using the API?

BBaya I don't see the option to delete secrets in Workers for Platforms API docs. How ...

Beny•4/20/24, 7:53 AM

This should work

DELETE https://api.cloudflare.com/client/v4/accounts/{account_id}/workers/dispatch/namespaces/{namespace}/scripts/{script_name}/secrets/{secret_name}

DELETE https://api.cloudflare.com/client/v4/accounts/{account_id}/workers/dispatch/namespaces/{namespace}/scripts/{script_name}/secrets/{secret_name}

Beny•4/20/24, 7:57 AM

Well it's meant to work but it has an

workers.api.error.unknown

workers.api.error.unknown

error

BBeny Well it's meant to work but it has an `workers.api.error.unknown` error

Baya•4/21/24, 11:36 PM

Thanks. Yes, I tried this before; I got the same error. Another issue I noticed is I can't access the "cf" request object in user workers.

rob•4/22/24, 1:00 AM

really? So their workers don't image access to the cf request object from the context ?

rob•4/22/24, 1:00 AM

Is that by design

BBaya Thanks. Yes, I tried this before; I got the same error. Another issue I noticed ...

Beny•4/22/24, 2:47 AM

Yeah the API seems to have a few issues unfortunately.
As for the cf props, something similar happens on DOs too - see the explanation of why here: durable-objects
If your project doesn't have a strict requirement of using the "fetch" entry point you might be able to use RPC to pass it down to the user worker (I've not tested this though)

BBeny Yeah the API seems to have a few issues unfortunately. As for the cf props, some...

Baya•4/22/24, 3:20 AM

I will check this. I have passed "cf" fields as request headers - as a quick fix.

BBaya Thanks. Yes, I tried this before; I got the same error. Another issue I noticed ...

Beny•4/22/24, 4:22 AM

There's a workaround I just figured out for deleting secrets, you can use the 'Patch Script Settings' API with a new array of bindings and it'll replace all the existing bindings with the ones specified. If you have other secrets you'd have to define them again which is a bit annoying

BBeny There's a workaround I just figured out for deleting secrets, you can use the 'P...

Baya•4/22/24, 4:32 AM

I think patching does not have effect on secrets that are not included in the bindings array.

BBaya I think patching does not have effect on secrets that are not included in the bi...

Beny•4/22/24, 4:40 AM

It did when I just tried it

Beny•4/22/24, 4:43 AM

Ah yeah you are right, it's actually still there but doesn't show as there in the API, strange

Beny•4/22/24, 5:09 AM

They even remain if you delete the script & upload it again, so I guess they're impossible to remove for now

Abdallah Abis•4/23/24, 3:16 PM

Hey Folks,
Can a user worker be a consumer of a queue? if so how can I configure it?
using this configures the user worker as a producer, but not a consumer.

{
  "type": "queue",
  "name": "<TEST_QUEUE>",
  "queue_name": "<TEST_QUEUE_NAME>"
}

{
  "type": "queue",
  "name": "<TEST_QUEUE>",
  "queue_name": "<TEST_QUEUE_NAME>"
}

Should I use the dispatcher as the consumer and then route those messages to the user worker from there?
The issue there would be they will change to be fetch events instead of queue events as there's only

userWorker.fetch

userWorker.fetch

method.

AAbdallah Abis Hey Folks, Can a user worker be a consumer of a queue? if so how can I configure...

Beny•4/23/24, 6:45 PM

You asked this one before, and the answer is still the same unfortunately.
The issue is that the API to create a consumer on a queue doesn't support referencing to dispatch namespace workers. Consumers are configured on the queue rather than the worker.
The only way for now is to create a regular worker that dispatches it to the user worker. You can use RPC to pass it to a handler other than fetch

Murmeltier•4/24/24, 10:53 PM

complete noob question, but I wasn't getting smart out of the docs: do user workers support scheduling?

MMurmeltier complete noob question, but I wasn't getting smart out of the docs: do user work...

Unsmart•4/24/24, 11:31 PM

I assume you mean cron triggers? I would assume they do but have not tested myself.

Unsmart•4/24/24, 11:32 PM

And if by scheduling you meant very specific time instead then you can use durable objects to make alarms to support invoking at a specific time

DORSHT•4/26/24, 8:20 AM

Hey, beginner question that maybe someone here can help me out with.
I'm going through the basic "Getting Started" docs of WFP, got a namespace, a user worker and a dispatcher.
So far everything works. Now, i've updated my dispatcher to be a dynamic dispatcher which by the docs is supposed to receive calls to

<USER_WORKER_NAME>.<MY-DOMAIN>.com/*

<USER_WORKER_NAME>.<MY-DOMAIN>.com/*

and from there extract the user worker name and call it. But, calls i'm making to

*.<MY-DOMAIN>.com

*.<MY-DOMAIN>.com

are not getting to my dispatcher worker (only calls to

<MY-DOMAIN>.com

<MY-DOMAIN>.com

do).

It doesn't say in this part of the docs how i should have configured my dispatcher's domains / routes for this to work, can someone help me understand what i'm missing?
Thanks.

DDORSHT Hey, beginner question that maybe someone here can help me out with. I'm going t...

Beny•4/26/24, 2:25 PM

Which route did you put on the dispatch worker? Should be something like

*.mydomain.com/*

*.mydomain.com/*

BBeny Well it's meant to work but it has an `workers.api.error.unknown` error

mrodOP•4/26/24, 3:12 PM

howdy folks, sorry for the delay, but this error when deleting secrets from namespaced workers should be fixed

Beny•5/4/24, 6:39 PM

When using #rate-limiting-beta with Workers for Platforms is there anything special implemented for the

namespace_id

namespace_id

or is that ID still shared among all scripts?

Unsmart•5/5/24, 2:31 AM

if you use the same id it would use the same namespace if thats what you mean

UUnsmart if you use the same id it would use the same namespace if thats what you mean

Beny•5/5/24, 6:47 PM

Yeah, that's how I imagine it works. Was just wondering if there had been any considerations for Workers for Platforms, such as them being scoped to each dispatch namespace.
It might become a challenge to maintain a database of namespace ids assigned to each user (to prevent them affecting each other) when there are a lot of workers across various dispatch namespaces and deployment systems.
I'm sure it wouldn't be an issue at the moment with the maximum rate limit period being 60 seconds, but that's sure to increase in the future and might affect other workers if they both end up using the same namespace id.
Perhaps an option that disables it being scoped across all workers would be useful in situations like this, where that behaviour becomes an obstacle rather than something useful.

Unsmart•5/5/24, 7:09 PM

Not sure why it would be hard to maintain a db?

UUnsmart Not sure why it would be hard to maintain a db?

Beny•5/5/24, 7:14 PM

Well in my situation that would involve creating a central database among 3 different deployment systems, with clashing user ids & script names. Of couse it is achievable, but not an easy task.

Beny•5/5/24, 7:18 PM

All that work could be avoided by a single additional option in the binding

Unsmart•5/5/24, 7:26 PM

I highly doubt they would do that as it completely defeats the point of namespaces

yup! `--remote` will work fine, but you'll be dispatching to live user workers at the edge. we have

Similar Threads

Similar Threads

Similar Threads