Check out https://github.com/cloudflare/wrangler-action - that'll probably give you everything you need 🙂

what do you think would be the best way to implement versioning in an api hosted on workers? - route-based, e.g.

/api/v3/...

- header-based, e.g. the

accept-language

header with the version as value () or a custom header

perfect, thank you ^^

Paths. Versions in the path are standardized, and so you'll get the broadest support across things that you might decide to do someday (OpenAPI, Swagger, etc).

It also allows for easier caching based on the version - i.e. with the header approach you'd need to add custom cache rules to make sure version 2's cache doesn't get served for version 1, but with path-based that's built-in by default.

please please don't do header routing

we just implemented header based routing because we had to to retain compatibility with AWS' API, and it's so ugly.

You won't be able to use OpenAPI schemas properly in many tools with header routing

@penalosa it was unbounded. But previous workers were not. Not sure what changed. I wasn’t able to change my default away from unbounded anywhere in the ui. Only paying the five dollars fixed it.

Hello. I’m trying to invite account for some other users, but how to set invite as editing for Workers Only? I set

Cloudflare Workers Admin

as new account, but it can check audit log also.

https://developers.cloudflare.com/workers/platform/limits/#worker-limits I'm curious whether CPU-intensive unbound workers from tenants will affect each other

They should not, no.

hello everyone, i am getting below error while executing my worker, any idea why ? Error: TypeError: _crypto.default.createHmac is not a function at worker.js:9100:43

is analytics engine free?

It is free during the beta, but eventually it will be paid. I'd expect the pricing to be announced in #981314061268578304

got it! also any docs on querying with graphql examples? i am having trouble interfacing with it via graphql -- regular sql queries over http work fine

i am logging users in the analytics engine but will be hard to analyze without some dashboard besides this

Hi, no need to post in multiple channels, answering in #846453104382836766

I believe the only docs of AE graphql is this right now https://developers.cloudflare.com/analytics/analytics-engine/get-started/#4-query-data-using-graphql-and-sql-api, but as the site says more stuff should be added soon

How? Workers run on different process?

There are some issues with the Cron trigger of my Workers. It should trigger every five minutes, but now it triggers twice every five minutes, doubling my request count. Has anyone experienced a similar situation?

yeah have the same issue https://discord.com/channels/595317990191398933/1108689633295999007

+ 1 to double cron triggering

We have seen an uptick in these reports and put up an escalation for them. They will look into it

Hey everyone, having a hard time finding much online with jest and workers. So I need to mock all of the types for fetch, request, response etc? Is there any docs on this

Hello everyone, I'm trying to restrict access to an API I build with Workers that I want to use in page. When I try to send a request to the API with the authorization from Postman or any other tool, it works perfectly, but from my Pages code, I get a CORS error. I tried many things, but no one seems to works. Here's the code of my endpoint: `export default { async fetch(request, env, ctx) { const { pathname } = new URL(request.url); const authHeader = request.headers.get('authorization'); const apiKey = env.authorization; if (authHeader !==

${apiKey}

) { return new Response('Error accessing this page', { status: 401 }); } else (pathname.startsWith("/id/")) { const id = pathname.substring("/id/".length); const { results } = await env.DB.prepare("SELECT * FROM products WHERE id= ?").bind(id).all(); return new Response(JSON.stringify(results), { headers: { "Content-Type": "application/json", "Access-Control-Allow-Origin": "*", "Access-Control-Allow-Methods": "GET, OPTIONS", "Access-Control-Allow-Headers": "authorization, Content-Type", "Access-Control-Allow-Credentials": "true" } }); } ...` And here's my call: `useEffect(() => { var myHeaders = new Headers(); myHeaders.append("authorization", "mykey"); var requestOptions = { method: 'GET', headers: myHeaders, redirect: 'follow' }; fetch(

myendpoint.com/id/${id}

, requestOptions) .then(response => response.json()) .then(data => { if (data.length > 0) { setArticle(data[0]); } }) .catch(error => setError(error)); }, [id]);`

@Linka @Neiki and/or @D3VL_Jack mind sharing your account ID (DM me) so that we can dig into logs?

DM'd

You need to properly respond to the OPTIONS preflight request

Thank you @sathoro for your answer. How I could do this 😅 ?