Any chance to access a beta/early version of worker-for-platforms without being enterprise?

Ccosbgn Any chance to access a beta/early version of worker-for-platforms without being ...

H

I would recommend writing a bit about your usecase. No guarantees, but it would help the team if they do decide to give access

C

cosbgnOP•1/22/24, 9:30 PM

I'm building unfetch.com - we combine large language models with APIs. Pretty much you can use chatgpt to access data on Stripe, Shopify or any external service you have.

This is working great, but for more complex use cases (e.g. fetch all my stripe past due users and add them to a spreadsheet) only endpoints are not enough, so I'm experimenting with letting GPT-4 write some code and I need a secure environment where to run it (i.e. cloudflare for platforms)

C

cosbgnOP•1/22/24, 9:32 PM

My main issue currently is with deploy limits. Since the code is generated, say my app receive 20K messages a day, I would need to deploy 20K different workers.

I'm not sure if it can be done.

C

cosbgnOP•1/22/24, 9:33 PM

Usual use cases have something like 10 deploys per customers and 10K request, I could have 10K deploys and 10K request (i.e. the code runs once and then in most cases will never run again)

C

cosbgnOP•1/22/24, 9:34 PM

I wouldn't need custom domains or anything like that

Ccosbgn I'm building unfetch.com - we combine large language models with APIs. Pretty mu...

V

Vero•1/25/24, 2:59 PM

Hi, just gave you access. Let me know if you have any feedback

C

cosbgnOP•1/26/24, 7:01 AM

Amazing, thanks!

C

cosbgnOP•1/26/24, 7:01 AM

Will check it out right away

C

cosbgnOP•1/26/24, 7:10 AM

@Vero

actually I do have a quick question, I can't seem to find any example which uses an external library from

npm

npm

Are external libraries allowed?

K

kian•1/26/24, 7:14 AM

Workers itself doesn't handle dependencies, you bundle the dependencies with something like esbuild (which Wrangler uses)

C

cosbgnOP•1/26/24, 7:25 AM

Would something like this work:

import { someFunction } from 'https://esm.sh/some-library';

import { someFunction } from 'https://esm.sh/some-library';

K

kian•1/26/24, 7:30 AM

Nope

K

kian•1/26/24, 7:31 AM

Code must be bundled at deploy time, you can't use URL imports/eval/new Function

C

cosbgnOP•1/26/24, 7:36 AM

Ok

R

rob•1/28/24, 4:56 PM

So if we want users to be able to add their own custom domaisn to point to our tracker worker, what would our process be>

https://developers.cloudflare.com/cloudflare-for-platforms/cloudflare-for-saas/start/getting-started/

Is Following this the right way to go? We arent an enterprise customer but we do have cloudflare for SaaS enabled

Configuring Cloudflare for SaaS · Cloudflare for Platforms docs

Get started with Cloudflare for SaaS

U

Unsmart•1/28/24, 5:00 PM

Yes, as step 1 says in the doc it works on the free plan

R

rob•1/28/24, 5:00 PM

@tony So I think we gotta do this:

R

rob•1/28/24, 5:01 PM

or do we use the API to add a route to the worker? its just a little convuluted for me to understand right now

R

rob•1/28/24, 5:03 PM

this is where i need to be right, but doing it via API when a user adds a domain on our frontend.

U

Unsmart•1/28/24, 5:05 PM

The API creates the custom hostname which will make it routable to your cloudflare zone and generate SSL certs.

Routing the custom hostnames to a worker is a different step and depends on how you want to do it.

If you want all custom hostnames to go to a single worker you would do the following:

In your zone go to workers routes and create 3 routes:

yourdomain.com/*

yourdomain.com/*

->

None

None

*.yourdomain.com/*

*.yourdomain.com/*

->

None

None

*/*

*/*

->

The Worker To Route Custom Hostnames

The Worker To Route Custom Hostnames

See image for example setup of workers routes:

T

tonytheonly•1/28/24, 5:07 PM

Thank you

UUnsmart The API creates the custom hostname which will make it routable to your cloudfla...

T

tonytheonly•1/30/24, 2:04 PM

when using the api for the custom hostname I am using the global api key in the X-Auth-Email and X-Auth-Key but I am getting an authentication error:

{
  method: 'POST',
  headers: {
    'X-Auth-Email': <GLOBAL_API_KEY>,
    'X-Auth-Key': <GLOBAL_API_KEY>,
    'Content-Type': 'application/json'
  },
  body: '{"hostname":"app.example.com","ssl":{"bundle_method":"ubiquitous","certificate_authority":"google","method":"txt","settings":{"ciphers":["ECDHE-RSA-AES128-GCM-SHA256","AES128-SHA"],"early_hints":"on","http2":"on","min_tls_version":"1.2","tls_1_3":"on"},"type":"dv","wildcard":true}}'
}
https://api.cloudflare.com/client/v4/zones/<MY_ZONE_ID>/custom_hostnames
{
  success: false,
  errors: [ { code: 10000, message: 'Authentication error' } ]
}

{
  method: 'POST',
  headers: {
    'X-Auth-Email': <GLOBAL_API_KEY>,
    'X-Auth-Key': <GLOBAL_API_KEY>,
    'Content-Type': 'application/json'
  },
  body: '{"hostname":"app.example.com","ssl":{"bundle_method":"ubiquitous","certificate_authority":"google","method":"txt","settings":{"ciphers":["ECDHE-RSA-AES128-GCM-SHA256","AES128-SHA"],"early_hints":"on","http2":"on","min_tls_version":"1.2","tls_1_3":"on"},"type":"dv","wildcard":true}}'
}
https://api.cloudflare.com/client/v4/zones/<MY_ZONE_ID>/custom_hostnames
{
  success: false,
  errors: [ { code: 10000, message: 'Authentication error' } ]
}

{
  method: 'POST',
  headers: {
    'X-Auth-Email': <GLOBAL_API_KEY>,
    'X-Auth-Key': <GLOBAL_API_KEY>,
    'Content-Type': 'application/json'
  },
  body: '{"hostname":"app.example.com","ssl":{"bundle_method":"ubiquitous","certificate_authority":"google","method":"txt","settings":{"ciphers":["ECDHE-RSA-AES128-GCM-SHA256","AES128-SHA"],"early_hints":"on","http2":"on","min_tls_version":"1.2","tls_1_3":"on"},"type":"dv","wildcard":true}}'
}
https://api.cloudflare.com/client/v4/zones/<MY_ZONE_ID>/custom_hostnames
{
  success: false,
  errors: [ { code: 10000, message: 'Authentication error' } ]
}

{
  method: 'POST',
  headers: {
    'X-Auth-Email': <GLOBAL_API_KEY>,
    'X-Auth-Key': <GLOBAL_API_KEY>,
    'Content-Type': 'application/json'
  },
  body: '{"hostname":"app.example.com","ssl":{"bundle_method":"ubiquitous","certificate_authority":"google","method":"txt","settings":{"ciphers":["ECDHE-RSA-AES128-GCM-SHA256","AES128-SHA"],"early_hints":"on","http2":"on","min_tls_version":"1.2","tls_1_3":"on"},"type":"dv","wildcard":true}}'
}
https://api.cloudflare.com/client/v4/zones/<MY_ZONE_ID>/custom_hostnames
{
  success: false,
  errors: [ { code: 10000, message: 'Authentication error' } ]
}

custom_certificate is optional when adding a hostname via the api correct? i was able to add a custom hostname in the dashboard that is proxying our services correctly.
https://developers.cloudflare.com/api/operations/custom-hostname-for-a-zone-create-custom-hostname

and the <MY_ZONE_ID> and <GLOBAL_API_KEY> are logging locally correctly just made them variables in this message for security.

Cloudflare API Documentation

Interact with Cloudflare's products and services via the Cloudflare API

T

tonytheonly•1/30/24, 8:49 PM

So the documentation for the fetch api is misleading. I was not able to properly authenticate with the api_email / api_key but instead with Authorization headers

async function createCustomHostname(c: Context) {
  const { CF_API_KEY, CF_ZONE_ID } = env<{ CF_API_KEY: string, CF_ZONE_ID: string }>(c)
  const content = await c.req.json<any>();
  const headers = {
    'Authorization': `Bearer ${CF_API_KEY}`,
     'Content-Type': 'application/json',
   };

  try {
    const options = {
      method: 'POST',
      headers: headers,
      body: JSON.stringify({ 
        "hostname": content.url, 
        "ssl": { 
          "bundle_method": "ubiquitous", 
          "method": "txt", 
          "settings": { 
            "ciphers": ["ECDHE-RSA-AES128-GCM-SHA256", "AES128-SHA"], 
            "early_hints": "on", 
            "http2": "on", 
            "min_tls_version": "1.2", 
            "tls_1_3": "on" 
          }, 
          "type": "dv", 
          "wildcard": false 
        } 
      })
    };
    const response = await fetch(`${BASE_URL}/zones/${CF_ZONE_ID}/custom_hostnames`, options)
    const json = await response.json()
    return json
  } catch (error) {
    console.error(`Error creating custom hostname: ${error}`);
    throw error;
  }
}

async function createCustomHostname(c: Context) {
  const { CF_API_KEY, CF_ZONE_ID } = env<{ CF_API_KEY: string, CF_ZONE_ID: string }>(c)
  const content = await c.req.json<any>();
  const headers = {
    'Authorization': `Bearer ${CF_API_KEY}`,
     'Content-Type': 'application/json',
   };

  try {
    const options = {
      method: 'POST',
      headers: headers,
      body: JSON.stringify({ 
        "hostname": content.url, 
        "ssl": { 
          "bundle_method": "ubiquitous", 
          "method": "txt", 
          "settings": { 
            "ciphers": ["ECDHE-RSA-AES128-GCM-SHA256", "AES128-SHA"], 
            "early_hints": "on", 
            "http2": "on", 
            "min_tls_version": "1.2", 
            "tls_1_3": "on" 
          }, 
          "type": "dv", 
          "wildcard": false 
        } 
      })
    };
    const response = await fetch(`${BASE_URL}/zones/${CF_ZONE_ID}/custom_hostnames`, options)
    const json = await response.json()
    return json
  } catch (error) {
    console.error(`Error creating custom hostname: ${error}`);
    throw error;
  }
}

async function createCustomHostname(c: Context) {
  const { CF_API_KEY, CF_ZONE_ID } = env<{ CF_API_KEY: string, CF_ZONE_ID: string }>(c)
  const content = await c.req.json<any>();
  const headers = {
    'Authorization': `Bearer ${CF_API_KEY}`,
     'Content-Type': 'application/json',
   };

  try {
    const options = {
      method: 'POST',
      headers: headers,
      body: JSON.stringify({ 
        "hostname": content.url, 
        "ssl": { 
          "bundle_method": "ubiquitous", 
          "method": "txt", 
          "settings": { 
            "ciphers": ["ECDHE-RSA-AES128-GCM-SHA256", "AES128-SHA"], 
            "early_hints": "on", 
            "http2": "on", 
            "min_tls_version": "1.2", 
            "tls_1_3": "on" 
          }, 
          "type": "dv", 
          "wildcard": false 
        } 
      })
    };
    const response = await fetch(`${BASE_URL}/zones/${CF_ZONE_ID}/custom_hostnames`, options)
    const json = await response.json()
    return json
  } catch (error) {
    console.error(`Error creating custom hostname: ${error}`);
    throw error;
  }
}

async function createCustomHostname(c: Context) {
  const { CF_API_KEY, CF_ZONE_ID } = env<{ CF_API_KEY: string, CF_ZONE_ID: string }>(c)
  const content = await c.req.json<any>();
  const headers = {
    'Authorization': `Bearer ${CF_API_KEY}`,
     'Content-Type': 'application/json',
   };

  try {
    const options = {
      method: 'POST',
      headers: headers,
      body: JSON.stringify({ 
        "hostname": content.url, 
        "ssl": { 
          "bundle_method": "ubiquitous", 
          "method": "txt", 
          "settings": { 
            "ciphers": ["ECDHE-RSA-AES128-GCM-SHA256", "AES128-SHA"], 
            "early_hints": "on", 
            "http2": "on", 
            "min_tls_version": "1.2", 
            "tls_1_3": "on" 
          }, 
          "type": "dv", 
          "wildcard": false 
        } 
      })
    };
    const response = await fetch(`${BASE_URL}/zones/${CF_ZONE_ID}/custom_hostnames`, options)
    const json = await response.json()
    return json
  } catch (error) {
    console.error(`Error creating custom hostname: ${error}`);
    throw error;
  }
}

U

Unsmart•1/30/24, 8:51 PM

Its generally not recommended to use the global api key and to instead use user api keys which use bearer auth. Is interesting that it doesnt work with the global api key but thats probably for the better anyways

T

tonytheonly•1/30/24, 8:51 PM

Yes I have created a token for the dns changes and it seems to work

T

tonytheonly•1/31/24, 7:58 PM

A quick follow up question, it seems like the validation cert is not being returned in the response for the post hostname api. I would expect response.data.ssl.validation_records

But the response is:

result: {
    id: '85efa926-8179-4c81-926e-eced6009ad63',
    hostname: 'test.exampleDomain.com',
    ssl: {
      id: 'de9b5334-8757-4b5f-85a9-5bcf3a4f0919',
      type: 'dv',
      method: 'txt',
      status: 'initializing',
      settings: [Object],
      wildcard: false,
      certificate_authority: 'google'
    },
    status: 'pending',
    ownership_verification: {
      type: 'txt',
      name: '_cf-custom-hostname.test.exampleDomain.com',
      value: '7bd6536e-dc3d-46ba-974a-9e608090a3aa'
    },
    ownership_verification_http: {
      http_url: 'http://test.exampleDomain.com/.well-known/cf-custom-hostname-challenge/85efa926-8179-4c81-926e-eced6009ad63',
      http_body: '7bd6536e-dc3d-46ba-974a-9e608090a3aa'
    },
    created_at: '2024-01-31T19:55:43.182431Z'
  },
  success: true,
  errors: [],
  messages: []
}

result: {
    id: '85efa926-8179-4c81-926e-eced6009ad63',
    hostname: 'test.exampleDomain.com',
    ssl: {
      id: 'de9b5334-8757-4b5f-85a9-5bcf3a4f0919',
      type: 'dv',
      method: 'txt',
      status: 'initializing',
      settings: [Object],
      wildcard: false,
      certificate_authority: 'google'
    },
    status: 'pending',
    ownership_verification: {
      type: 'txt',
      name: '_cf-custom-hostname.test.exampleDomain.com',
      value: '7bd6536e-dc3d-46ba-974a-9e608090a3aa'
    },
    ownership_verification_http: {
      http_url: 'http://test.exampleDomain.com/.well-known/cf-custom-hostname-challenge/85efa926-8179-4c81-926e-eced6009ad63',
      http_body: '7bd6536e-dc3d-46ba-974a-9e608090a3aa'
    },
    created_at: '2024-01-31T19:55:43.182431Z'
  },
  success: true,
  errors: [],
  messages: []
}

result: {
    id: '85efa926-8179-4c81-926e-eced6009ad63',
    hostname: 'test.exampleDomain.com',
    ssl: {
      id: 'de9b5334-8757-4b5f-85a9-5bcf3a4f0919',
      type: 'dv',
      method: 'txt',
      status: 'initializing',
      settings: [Object],
      wildcard: false,
      certificate_authority: 'google'
    },
    status: 'pending',
    ownership_verification: {
      type: 'txt',
      name: '_cf-custom-hostname.test.exampleDomain.com',
      value: '7bd6536e-dc3d-46ba-974a-9e608090a3aa'
    },
    ownership_verification_http: {
      http_url: 'http://test.exampleDomain.com/.well-known/cf-custom-hostname-challenge/85efa926-8179-4c81-926e-eced6009ad63',
      http_body: '7bd6536e-dc3d-46ba-974a-9e608090a3aa'
    },
    created_at: '2024-01-31T19:55:43.182431Z'
  },
  success: true,
  errors: [],
  messages: []
}

result: {
    id: '85efa926-8179-4c81-926e-eced6009ad63',
    hostname: 'test.exampleDomain.com',
    ssl: {
      id: 'de9b5334-8757-4b5f-85a9-5bcf3a4f0919',
      type: 'dv',
      method: 'txt',
      status: 'initializing',
      settings: [Object],
      wildcard: false,
      certificate_authority: 'google'
    },
    status: 'pending',
    ownership_verification: {
      type: 'txt',
      name: '_cf-custom-hostname.test.exampleDomain.com',
      value: '7bd6536e-dc3d-46ba-974a-9e608090a3aa'
    },
    ownership_verification_http: {
      http_url: 'http://test.exampleDomain.com/.well-known/cf-custom-hostname-challenge/85efa926-8179-4c81-926e-eced6009ad63',
      http_body: '7bd6536e-dc3d-46ba-974a-9e608090a3aa'
    },
    created_at: '2024-01-31T19:55:43.182431Z'
  },
  success: true,
  errors: [],
  messages: []
}

T

tonytheonly•1/31/24, 7:58 PM

@Unsmart | Tech debt

S

Sunil Kumar•2/1/24, 6:40 AM

I'm working on a small project i.e.., A user can install there subdomain path form main domain

ex :- hashnode.com //main domain
sunilkumar.hashnode.dev //sub domain like that

we have personal access token to access particular details of a user and later we need to check like what are available domains on the user and we need to take which domain you need to install like that

by using workers how can i achieve this problem .

can anyone help me out the best way to achieve and also some insights and resources
@unsmart

SSunil Kumar I'm working on a small project i.e.., A user can install there subdomain path f...

S

Sunil Kumar•2/1/24, 6:41 AM

@john.spurlock can you share some insights and resources to continue with my project

R

rob•2/2/24, 9:44 PM

so what if a client is hosting their domain on cloudflar managing their dns, will it create an issue if they add a cname to our SaaS worker?

R

rob•2/2/24, 9:48 PM

Do i want it proxied or not ? if i was a hypothetical customer ?

R

rob•2/2/24, 9:53 PM

trackflow.cosmic.marketing redirected you too many times.
Try deleting your cookies.
ERR_TOO_MANY_REDIRECTS

trackflow.cosmic.marketing redirected you too many times.
Try deleting your cookies.
ERR_TOO_MANY_REDIRECTS

R

rob•2/2/24, 9:53 PM

It's in our custom hostnames so it should be working

R

rob•2/3/24, 5:06 AM

@tony

Rrob so what if a client is hosting their domain on cloudflar managing their dns, wil...

P

Payello•2/3/24, 5:42 PM

It should not be proxied on the customer's DNS settings, but the hostname they point to should be proxied in your platform's DNS settings.
You should also add a suitable route to your worker. When Cloudflare for SaaS is enabled on a zone you are allowed to use the wildcard

for the worker route which catches all custom hostnames.

Original message was deleted

A

arfath_linklet•2/11/24, 2:25 PM

Hey all! A followup query - The 5000 limit for max hostname - can the limit be increased by support for non-enterprise accounts?

O

Oleg Isonen•2/14/24, 3:10 PM

Hey, is tiered cache on workers for platforms still not workig with R2? Anybody knows the reason?

We just figured out that our site LITERALLY fails core web vitals because the blocking CSS resource is globally super slow, which we serve from R2.

https://webstudio.is/

Looks great on lighthouse score https://pagespeed.web.dev/analysis?url=https%3A%2F%2Fwebstudio.is%2F

But completely fails core web vitals.

My tests have shown 300-500ms loading times specifically for the static ressources and in particular important one the blocking CSS resource https://webstudio.is/build/_assets/index-6JJ5GLFW.css

Webstudio

Open visual development for the open web

Similar to Webflow, Webstudio visually translates CSS without obscuring it, giving designers superpowers that were exclusive to developers in the past.

OOleg Isonen Hey, is tiered cache on workers for platforms still not workig with R2? Anybody ...

U

Unsmart•2/14/24, 5:06 PM

R2 doesnt support tiered cache doesnt have anything to do with workers for platforms. I imagine they will eventually work on getting tiered cache support but might be a while

L

ldp•2/24/24, 8:55 PM

TLDR:

new ReadableStream()

new ReadableStream()

is working for me in normal workers, but not workers for platforms

Hi guys! I'm implementing a feature using Prisma's Pulse product, which streams database change events to listening clients.

I'm able to connect and listen to events perfectly on a traditional worker, but the same code on Workers for Platforms as a customer worker has issues when instantiating a ReadableStream.

Error: To use the new ReadableStream() constructor, enable the streams_enable_constructors compatibility flag. Refer to the docs for more information: https://developers.cloudflare.com/workers/platform/compatibility-dates/#compatibility-flags

I was hoping it would be as simple as:

compatibility_flags = ['streams_enable_constructors']

compatibility_flags = ['streams_enable_constructors']

When attempting to add this to my WFP

wrangler.toml

wrangler.toml

, I get the following error:

The compatibility flag streams_enable_constructors became the default as of 2022-11-30 so does not need to be specified anymore. [code: 10021]

Current compatibility date (for both platform code, and customer workers):

compatibility_date = "2024-02-21"

compatibility_date = "2024-02-21"

I'm guessing maybe I need to set this in my customer code somehow?

Is there potentially some sort of binding I can set to enable this for my customers?

My other suspicion is that it may be a different error, but cloudflare potentially catches it and throws this generic error instead.

Zzeb Yes, either by using the secrets endpoint similar to whats available to other ty...

A

Abdallah Abis•2/27/24, 10:02 PM

Thanks for this!!
How can I delete a secret? what's the endpoint?

U

Unsmart•2/27/24, 10:06 PM

a DELETE to /secrets/:name

UUnsmart a DELETE to /secrets/:name

A

Abdallah Abis•2/27/24, 10:20 PM

I have added

{
  "name": "Example",
  "text":  "example",
  "type": "secret_text"
}

{
  "name": "Example",
  "text":  "example",
  "type": "secret_text"
}

{
  "name": "Example",
  "text":  "example",
  "type": "secret_text"
}

{
  "name": "Example",
  "text":  "example",
  "type": "secret_text"
}

I tried

DELETE

DELETE

to

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

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

I get

{
    "result": null,
    "success": false,
    "errors": [
        {
            "code": 10013,
            "message": "workers.api.error.unknown"
        }
    ],
    "messages": []
}

{
    "result": null,
    "success": false,
    "errors": [
        {
            "code": 10013,
            "message": "workers.api.error.unknown"
        }
    ],
    "messages": []
}

{
    "result": null,
    "success": false,
    "errors": [
        {
            "code": 10013,
            "message": "workers.api.error.unknown"
        }
    ],
    "messages": []
}

{
    "result": null,
    "success": false,
    "errors": [
        {
            "code": 10013,
            "message": "workers.api.error.unknown"
        }
    ],
    "messages": []
}

but trying with a secret key that doesn't exist like

ExampleX

ExampleX

returns

{
  "code": 10056,
  "message": "workers.api.error.binding_not_found"
}

{
  "code": 10056,
  "message": "workers.api.error.binding_not_found"
}

{
  "code": 10056,
  "message": "workers.api.error.binding_not_found"
}

{
  "code": 10056,
  "message": "workers.api.error.binding_not_found"
}

So the endpoint is there I guess but doesn't work for some reason

T

tanushree │ Workers PM•3/1/24, 5:20 PM

Here's a sample curl for deleting secrets:

curl --location --request DELETE 'https://api.cloudflare.com/client/v4/accounts/<ACCOUNT>/workers/scripts/worker-restless-wave-3410/secrets/my-secret' \
--header 'Content-Type: application/json' \
--header 'Authorization: Bearer <TOKEN>'

curl --location --request DELETE 'https://api.cloudflare.com/client/v4/accounts/<ACCOUNT>/workers/scripts/worker-restless-wave-3410/secrets/my-secret' \
--header 'Content-Type: application/json' \
--header 'Authorization: Bearer <TOKEN>'

curl --location --request DELETE 'https://api.cloudflare.com/client/v4/accounts/<ACCOUNT>/workers/scripts/worker-restless-wave-3410/secrets/my-secret' \
--header 'Content-Type: application/json' \
--header 'Authorization: Bearer <TOKEN>'

curl --location --request DELETE 'https://api.cloudflare.com/client/v4/accounts/<ACCOUNT>/workers/scripts/worker-restless-wave-3410/secrets/my-secret' \
--header 'Content-Type: application/json' \
--header 'Authorization: Bearer <TOKEN>'

MMaddy | Technical Writer Hey everybody! My name's Maddy and I'm the tech writer for Workers for Platforms...

U

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

Not workers for platforms directly but its pretty common for people to want to use custom domains + workers for platforms and the documentation for how to use workers as an origin is not correct/clear. Put in an issue about this on github a little over a year ago: https://github.com/cloudflare/cloudflare-docs/issues/5584

Also seems the link changed its here now: https://developers.cloudflare.com/cloudflare-for-platforms/cloudflare-for-saas/start/advanced-settings/worker-as-origin/

M

Matt Linkous•3/5/24, 10:04 PM

Am I mistaken that even with workers-for-platforms there's not a way to get Durable Object storage by tenant/namespace?

A

Abdallah Abis•3/6/24, 9:37 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>"
}

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

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

MMatt Linkous Am I mistaken that even with workers-for-platforms there's not a way to get Dura...

T

tanushree │ Workers PM•3/7/24, 6:17 PM

What do you mean by tenant in this case? Do you mean per-user worker?

U

Unsmart•3/7/24, 6:25 PM

My assumption was he wants users to be able to create their own DOs in a workers for platform script. Thats really the only thing you cant do with them per tenant. Would be pretty neat to be able to do

T

tanushree │ Workers PM•3/7/24, 6:29 PM

https://docs.google.com/document/d/1fxuUbZLFlkrDyfM2VTTFZFwDaBtodjCAR1neM3UL714/edit?usp=sharing

Google Docs

[EXTERNAL] Durable Objects in namespaced scripts

Any chance to access a beta/early version of worker-for-platforms without being enterprise?

Similar Threads

Similar Threads

Similar Threads