Hey @phatso are you able to confirm the ticket number you raised? Wondering if it's the one I was on
Hey @phatso are you able to confirm the ticket number you raised? Wondering if it's the one I was on just now, or another
Mis there any way to push a keyvalue out to all edge locations and not have them expire? trying to check api keys for incoming requests
PYep! That's me
EHey 
do you have a link to the message you were referring to, so I can understand the context?
do you have a link to the message you were referring to, so I can understand the context?
Dis there any way to get keys in bulk? googled but couldn't find anything
something like this:
something like this:
KNot with the Worker bindings, no
Dwhy is it available over http api but not worker bindings?
KI don't see it in the API either
KThere's bulk writes and deletes, but no gets.
Doh yeah i misread
Dthat's weird
Dwonder why
EI'm struggling with using kv, are there any good whole project examples. I see in the docs there is a tutorial for rust, but not ES. I'm just getting null when I call env.NS.get('whatever') and I'm sure it's got to be a setting so I'm looking for a whole working project to compare too. Thanks.
Khttps://developers.cloudflare.com/workers/runtime-apis/kv/#reading-key-value-pairs
will begetnullif that key doesn't exist.
EThanks @kian - thing is, I can get the correct value from the command line "wrangler kv:key get --namespace-id=### "{key}" but it just doesn't in the worker.js. My binding has the same preview_id as I used in the commandline call. so I'll keep trying.
KIs it a published Worker?
KWrangler dev defaults to local development, so it has no access to your real KV namespace.
E@Kian oh. I did not see that mentioned in the docs. I'm using local. So is there a local kv to setup and use?
PMetadata only
EI did get it to work a bit but I still don't understand. I deployed, my wrangler.toml file has workers_dev=true yet the key value doesn't come from the namespace specified by preview_id
ESOLVED: I just needed to add --remote to the end of 'wrangler dev --remote' now I can read KV from localhost.
MHey, this announcement - https://blog.cloudflare.com/faster-workers-kv-architecture/#:~:text=If%20these%20sound%20like%20the%20killer%20features%20you%20need%2C%20please%20reach%20out%20to%20us%20if%20you%E2%80%99re%20interested%20in%20trying%20them%20out about new exiting features says that one can reach out and try out them earlier then ga - how can I do it?
The Cloudflare Blog
With the new architecture powering Workers KV our service will become faster and more scalable than ever. We have significantly reduced cold read probability, and enabled KV to serve over a trillion requests a month
CWhat do you mean by updating KV? If you have an existing worker that has an existing KV binding then it should continue to function. With the maintenance, there might be issues with creating a new worker, kv namespace, or binding the namespace to a worker
CMy understanding is those operations should not be affected
0I'm trying to write something to a KV and it stays unaffected. :/
I tried on my localhost and in deployed production. Wrangler (3.1.2) does not issue any error/warning. What can be the cause?
I tried on my localhost and in deployed production. Wrangler (3.1.2) does not issue any error/warning. What can be the cause?
0Am I using outdated
toml?0Just tried
Doesn't work..
Doesn't work..
0I inserted some keys and values via the dashboard and
await env.HEADERS.get(..) returns null for them
CIf you're using wrangler 3.x, the default wrangler dev is local/all local data, have to use wrangler dev --remote to access real KV namespaces/data
0That works with the preview KV namespace! Thanks! How do I make it work for production deployment?
0I
npx wrangler deploy ed the same code. The binding IDs are correct and nothing shows up in the KV. The worker gets hit 155k/24hCIs your kv namespace id and preview id the same? dev --remote will use preview_id, and deployed worker will use normal id, might be the cause of some confusion.
0These are different IDs. I understand that preview has a different purpose to production. There was a warning about that when I tried to run
npx wrangler dev too.0I double checked the IDs and just redeployed the same code. No errors from workers
CRight, my line of thinking was "are you checking the right one"? If your worker simply puts that on every request, you should be able to see those values in the dashboard. Can you see them there? If so, it is just the worker itself not being able to get them later, or something else?
05 records appeared in the KV but the strange thing is that it only contains my 5
curl
0
0
CKV is global, that kinda sounds like to me you're looking at the preview and not the production namespace, or you have something with your code that is preventing writes. Workers are pretty quick to deploy globally, maybe 10-15s
0This is the worker code. It uses
export default { syntax. Every request should hit it.0Hmm...
0Is it safe to post namespace ids here?
0
0I'm cetain that this is the same
id[[kv_namespaces]] id = 0Maybe I'm doing something really silly.
0Could you tell if this might be the culprit? I'm using a custom domain "without custom domain". I created route and DNS record manually so the requests are possibly routed to the old worker instances and the new code is never executed. I've never actually used the
Connect your Worker to a custom domain. panel.