ah, just found this comment. are there any roadmap plans to let user workers act as queue consumers?

JJason Barry ah, just found this comment. are there any roadmap plans to let user workers act...

A

Acе•9/19/24, 1:31 AM

There’s been no movement on this afaik. I’d suggest opening an issue on the workers-sdk git so the cloudflare team have more visibility of this being something we want

AAcе There’s been no movement on this afaik. I’d suggest opening an issue on the work...

J

Jason BarryOP•9/19/24, 2:00 AM

I filed https://github.com/cloudflare/workers-sdk/issues/6758, thanks!

C

cake•9/19/24, 5:26 PM

In order for me to link a customers domain, and provide traffic through workers for platforms, do I need to link the customers domain via cloudflare for saas, meaning I have to pay per month for each domain linked?
Does workers for platforms allow me to link a customers root domain (without www.)?

Ccake 1. In order for me to link a customers domain, and provide traffic through worke...

P

Payello•9/19/24, 5:32 PM

Yes. It costs $0.10 a month per hostname with 100 included for free. To hook them up to workers you need to set the fallback origin to a proxied DNS entry (See more details)
Yes you can do that too.

C

cake•9/19/24, 5:41 PM

thank you!

PPayello 1. Yes. It costs $0.10 a month per hostname with 100 included for free. To hook ...

E

Erisa•9/19/24, 8:34 PM

Its $0.10/hostname after 100 included, NOT $2 (cc @cake)

C

Chaika•9/19/24, 8:51 PM

$2 is the old pricing which was changed in 2022

D

dev•9/19/24, 9:08 PM

seks

EErisa Its $0.10/hostname after 100 included, NOT $2 (cc @cake)

P

Payello•9/19/24, 9:08 PM

Thanks for the correction!

CChaika $2 is the old pricing which was changed in 2022

E

Erisa•9/19/24, 9:10 PM

and that old pricing didnt have 100 included for free, so what was mentioned is a weird combination of both

EErisa and that old pricing didnt have 100 included for free, so what was mentioned is ...

P

Payello•9/19/24, 9:15 PM

First looked at the docs and saw 100 hostnames included. There's no Pricing page like other products, but I found the 2 dollar price point on one of the blog posts.
Perhaps this should be added to https://developers.cloudflare.com/cloudflare-for-platforms/cloudflare-for-saas/plans/ ?

E

Erisa•9/19/24, 9:16 PM

it should, but fwiw its on https://www.cloudflare.com/plans/

PPayello First looked at the docs and saw 100 hostnames included. There's no Pricing page...

W

Walshy•9/20/24, 12:10 AM

can you make a docs issue pls https://github.com/cloudflare/cloudflare-docs/issues

Original message was deleted

T

texan•9/26/24, 9:35 PM

We don't have a timeline for you, but it's on our list of fast follows for assets.

R

ryanmoziyi•9/27/24, 8:27 PM

hii

A

Advany•9/27/24, 9:16 PM

So all requests to a dispatch workers that call user and / or outbound workers count as one worker request?

UUnsmart If its about using workers as an origin I actually do agree that part is confusi...

T

tadhglewis•9/28/24, 9:35 AM

@Unsmart | Tech debt This is very confusing and the docs probably need updating.. Those 3 routers make sense though (or I guess you could add each vanity domain as a worker route?)!

Are the docs worded like this because it is recommended to just have a separate zone/domain for SaaS rather than providing SaaS off of your domain.com? E.g. customerdomain.com used for SaaS and domain.com used for the actual product

T

TurboJack•9/29/24, 8:53 PM

Hello. Can someone tell me what I'm doing wrong? I can't update the settings of a user worker.

const client = new Cloudflare({
    apiEmail: env['CLOUDFLARE_EMAIL'], // This is the default and can be omitted
    //apiKey: env['CLOUDFLARE_API_KEY'], // This is the default and can be omitted
    apiToken: env['CLOUDFLARE_API_TOKEN'],
  });

  const settings = await client.workersForPlatforms.dispatch.namespaces.scripts.settings.get(
    'dev',
    workerName,
    { account_id: env['CLOUDFLARE_ACCOUNT_ID'] },
  );
  
  console.log(settings);

  const response = await client.workersForPlatforms.dispatch.namespaces.scripts.settings.edit(
    'dev',
    workerName,
    { account_id: env['CLOUDFLARE_ACCOUNT_ID'], settings },
  );
  
  console.log(response.bindings);

const client = new Cloudflare({
    apiEmail: env['CLOUDFLARE_EMAIL'], // This is the default and can be omitted
    //apiKey: env['CLOUDFLARE_API_KEY'], // This is the default and can be omitted
    apiToken: env['CLOUDFLARE_API_TOKEN'],
  });

  const settings = await client.workersForPlatforms.dispatch.namespaces.scripts.settings.get(
    'dev',
    workerName,
    { account_id: env['CLOUDFLARE_ACCOUNT_ID'] },
  );
  
  console.log(settings);

  const response = await client.workersForPlatforms.dispatch.namespaces.scripts.settings.edit(
    'dev',
    workerName,
    { account_id: env['CLOUDFLARE_ACCOUNT_ID'], settings },
  );
  
  console.log(response.bindings);

const client = new Cloudflare({
    apiEmail: env['CLOUDFLARE_EMAIL'], // This is the default and can be omitted
    //apiKey: env['CLOUDFLARE_API_KEY'], // This is the default and can be omitted
    apiToken: env['CLOUDFLARE_API_TOKEN'],
  });

  const settings = await client.workersForPlatforms.dispatch.namespaces.scripts.settings.get(
    'dev',
    workerName,
    { account_id: env['CLOUDFLARE_ACCOUNT_ID'] },
  );
  
  console.log(settings);

  const response = await client.workersForPlatforms.dispatch.namespaces.scripts.settings.edit(
    'dev',
    workerName,
    { account_id: env['CLOUDFLARE_ACCOUNT_ID'], settings },
  );
  
  console.log(response.bindings);

const client = new Cloudflare({
    apiEmail: env['CLOUDFLARE_EMAIL'], // This is the default and can be omitted
    //apiKey: env['CLOUDFLARE_API_KEY'], // This is the default and can be omitted
    apiToken: env['CLOUDFLARE_API_TOKEN'],
  });

  const settings = await client.workersForPlatforms.dispatch.namespaces.scripts.settings.get(
    'dev',
    workerName,
    { account_id: env['CLOUDFLARE_ACCOUNT_ID'] },
  );
  
  console.log(settings);

  const response = await client.workersForPlatforms.dispatch.namespaces.scripts.settings.edit(
    'dev',
    workerName,
    { account_id: env['CLOUDFLARE_ACCOUNT_ID'], settings },
  );
  
  console.log(response.bindings);

The first request works but no matter what I put in the settings I'm always getting the same error -_-

{
  placement: {},
  compatibility_date: "2024-09-09",
  compatibility_flags: [ "nodejs_compat" ],
  usage_model: "standard",
  tags: [],
  tail_consumers: [],
  logpush: false,
  bindings: [
    { json: true, name: "DEBUG", type: "json" },
    { name: "ENVIRONMENT", text: "dev", type: "plain_text" },
    {
      database_id: "55e2e1a0-c8ea-4105-8547-a4eaf93fa4ef",
      id: "55e2e1a0-c8ea-4105-8547-a4eaf93fa4ef",
      name: "TASK",
      type: "d1"
    },
    {
      name: "task_queue",
      queue_name: "dev-task-queue-b9c9bed5-2f61-4f76-82cb-1b712aa8bd35",
      type: "queue"
    }
  ]
}

{
  placement: {},
  compatibility_date: "2024-09-09",
  compatibility_flags: [ "nodejs_compat" ],
  usage_model: "standard",
  tags: [],
  tail_consumers: [],
  logpush: false,
  bindings: [
    { json: true, name: "DEBUG", type: "json" },
    { name: "ENVIRONMENT", text: "dev", type: "plain_text" },
    {
      database_id: "55e2e1a0-c8ea-4105-8547-a4eaf93fa4ef",
      id: "55e2e1a0-c8ea-4105-8547-a4eaf93fa4ef",
      name: "TASK",
      type: "d1"
    },
    {
      name: "task_queue",
      queue_name: "dev-task-queue-b9c9bed5-2f61-4f76-82cb-1b712aa8bd35",
      type: "queue"
    }
  ]
}

{
  placement: {},
  compatibility_date: "2024-09-09",
  compatibility_flags: [ "nodejs_compat" ],
  usage_model: "standard",
  tags: [],
  tail_consumers: [],
  logpush: false,
  bindings: [
    { json: true, name: "DEBUG", type: "json" },
    { name: "ENVIRONMENT", text: "dev", type: "plain_text" },
    {
      database_id: "55e2e1a0-c8ea-4105-8547-a4eaf93fa4ef",
      id: "55e2e1a0-c8ea-4105-8547-a4eaf93fa4ef",
      name: "TASK",
      type: "d1"
    },
    {
      name: "task_queue",
      queue_name: "dev-task-queue-b9c9bed5-2f61-4f76-82cb-1b712aa8bd35",
      type: "queue"
    }
  ]
}

{
  placement: {},
  compatibility_date: "2024-09-09",
  compatibility_flags: [ "nodejs_compat" ],
  usage_model: "standard",
  tags: [],
  tail_consumers: [],
  logpush: false,
  bindings: [
    { json: true, name: "DEBUG", type: "json" },
    { name: "ENVIRONMENT", text: "dev", type: "plain_text" },
    {
      database_id: "55e2e1a0-c8ea-4105-8547-a4eaf93fa4ef",
      id: "55e2e1a0-c8ea-4105-8547-a4eaf93fa4ef",
      name: "TASK",
      type: "d1"
    },
    {
      name: "task_queue",
      queue_name: "dev-task-queue-b9c9bed5-2f61-4f76-82cb-1b712aa8bd35",
      type: "queue"
    }
  ]
}


Error: 400 {"result":null,"success":false,"errors":[{"code":10201,"message":"workers.api.error.missing_settings_part"}],"messages":[]}


Error: 400 {"result":null,"success":false,"errors":[{"code":10201,"message":"workers.api.error.missing_settings_part"}],"messages":[]}


Error: 400 {"result":null,"success":false,"errors":[{"code":10201,"message":"workers.api.error.missing_settings_part"}],"messages":[]}


Error: 400 {"result":null,"success":false,"errors":[{"code":10201,"message":"workers.api.error.missing_settings_part"}],"messages":[]}

Y

yonatan•9/30/24, 10:12 AM

I'm trying to understand why I was billed for 12,510 "Workers for Platforms Scripts" in the latest invoice I got.
We deploy our users' Workers by calling

cloudflare.workersForPlatforms.dispatch.namespaces.scripts.update

cloudflare.workersForPlatforms.dispatch.namespaces.scripts.update

using the SDK. So does this mean that we called this 12,510 times? Or are we charged per file that composes this user worker? (for each call me we make to

scripts.update

scripts.update

we include several files we create by calling

Cloudflare.toFile

Cloudflare.toFile

)

Yyonatan I'm trying to understand why I was billed for 12,510 "Workers for Platforms Scri...

W

Walshy•9/30/24, 10:19 AM

Should be each unique script, files aren't something we even really track or update calls

If you can give me your account ID I can take a look - you sure you aren't making a bunch of scripts?

What does the dash show for your namespace? https://dash.cloudflare.com/?to=/:account/workers-for-platforms

Original message was deleted

T

tanushree │ Workers PM•9/30/24, 8:20 PM

Want bring all of these to Workers for Platforms! DMing you - would love to learn more about what you're building

Ttanushree │ Workers PM Second argument hasn't been implemented (publicly) yet. It's a way to pass bindi...

T

TurboJack•10/1/24, 10:20 AM

I would like to give customers their own d1.
Currently I want to bind them on upload but if it's possible to do that on dispatch, than it would make me not reuploading the script on every binding change.

C

chronark•10/16/24, 10:21 AM

is it not possible to add environment variables or secrets to a platform script?
I see now way to do it in the UI and it seems to ignore my

env

env

settings in the wrangler config

Cchronark is it not possible to add environment variables or secrets to a platform script?...

P

Payello•10/21/24, 2:56 PM

Environment variables are just bindings so they will work with wrangler deploy. Perhaps your wrangler config is incorrect as it works on my end.
For secrets there is no command but you can use the API, see this post: workers-for-platforms

H

harminderthind•10/22/24, 5:31 PM

Has anyone setup a Apex proxy? as mentioned here - https://developers.cloudflare.com/cloudflare-for-platforms/cloudflare-for-saas/start/advanced-settings/apex-proxying/setup/

H

harminderthind•10/22/24, 5:32 PM

Where can i get of IPs assigned to my account as mentioned in docs

Hharminderthind Where can i get of IPs assigned to my account as mentioned in docs

H

Hello, I’m Allie!•10/22/24, 6:07 PM

Are you on Enterprise? If so, I would reach out to your CSM

H

harminderthind•10/23/24, 8:06 AM

No, I'm not on enterprise, so is this feature only for enterprise customers?

Mmethyl I assume the default way to handle workers routing on behalf of clients is to se...

A

Advany•10/23/24, 8:39 AM

I also do this. currently I ask clients to setup a worker in their account that sends all traffic to my worker and has some logic to fall back to original host/worker

Hharminderthind No, I'm not on enterprise, so is this feature only for enterprise customers?

H

Hello, I’m Allie!•10/23/24, 1:51 PM

H

harminderthind•10/23/24, 2:29 PM

@HardlyWorkin' Where is this pricing page

Hharminderthind @HardlyWorkin' Where is this pricing page

H

Hello, I’m Allie!•10/23/24, 2:29 PM

https://developers.cloudflare.com/cloudflare-for-platforms/cloudflare-for-saas/plans/

Cloudflare Docs

Plans | Cloudflare for Platforms docs

Learn what features and limits are part of various Cloudflare plans.

H

harminderthind•10/23/24, 2:31 PM

any idea what it costs ?

Hharminderthind any idea what it costs ?

H

Hello, I’m Allie!•10/23/24, 2:46 PM

A thousand or more usually, though exact pricing is up to your individual contract

H

harminderthind•10/23/24, 3:17 PM

Thanks @HardlyWorkin'

HHello, I’m Allie!A thousand or more usually, though exact pricing is up to your individual contra...

I

Isaac McFadyen•10/23/24, 4:51 PM

^ per month

A

Azeem•10/24/24, 8:03 PM

Hello, if I proxy requests to a shopify store using a worker, is that going to be considered an O2O proxy, as explained in the Cloudflare for platforms docs for Shopify?

My main concern is to use workers but avoid getting rate limited or blocked by Shopify's bot protection mechanisms.

C

clark•10/26/24, 6:57 AM

Hi everyone! I was wondering if the Workers for Platforms plan($25/month) is considered part of the Workers Paid plan. Specifically, when looking at the D1 pricing:
Plan Workers Free Workers Paid
Rows read 5 million / day First 25 billion / month included + $0.001 / million rows
Does the Workers for Platforms plan fall under the Workers Paid tier for D1 pricing, or would I need to pay an additional $5/month for the Workers Paid plan to get those benefits?Thanks for any clarification!

Cclark Hi everyone! I was wondering if the Workers for Platforms plan($25/month) is con...

B

boop•10/26/24, 11:37 AM

It’s separate

C

clark•10/26/24, 3:44 PM

@Deleted User thanks:blobyes:

N

nclevenger•10/29/24, 5:45 PM

Are Workflow bindings supported in Workers for Platforms?

Nnclevenger Are Workflow bindings supported in Workers for Platforms?

F

fry69•10/29/24, 5:54 PM

Not yet as far as I know.

A

Abdallah Abis•11/5/24, 2:38 PM

Hey folks,
How can I specify the

tags

tags

using this deploy command?

npx wrangler deploy --dispatch-namespace <NAMESPACE_NAME>

npx wrangler deploy --dispatch-namespace <NAMESPACE_NAME>

A

Abdallah Abis•11/5/24, 2:41 PM

Another question:
Do queues support user workers as consumers? if so, how can I configure a user worker to consumer from a queue?

P

Payello•11/9/24, 5:44 AM

Is there a way to replace just 1 file in a multipart worker? For example we want to update our platform_module.mjs while retaining the user_script.mjs

J

juanferreras•11/9/24, 9:55 PM

not seeing it in docs but mostly curious – do user workers expose RPC (like service bindings via RPC) or just

.fetch

.fetch

(like service bindings via HTTP)? I'm trying to build an abstraction where a worker would call another via service bindings mostly (RPC looks great here), but some power-users could write/upload their own (RPC isn't really mentioned anywhere here but was curious if anyone already tried)

W

Walshy•11/9/24, 10:10 PM

yep you can rpc to a user worker

ah, just found this comment. are there any roadmap plans to let user workers act as queue consumers?

Similar Threads