You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Say, I want to do integration tests in our ci env which internet access is limited. my worker has dependency on worker kv, but i don't want it to connect to any remote place given the limit.
and started with this command npx wrangler dev -e ci got the following errors
✘ [ERROR] In development, you should use a separate kv namespace than the one you'd use in production. Please create a new kv namespace with "wrangler kv:namespace create <name> --preview" and add its id as preview_id to the kv_namespace "SOME_THING" in your wrangler.toml
I can't run this command because no internet access, and it also asked for opening an url with browser, which is not possible in an automated ci env.
from the official doc, it mentioned
Resources such as KV, Durable Objects, D1, and R2 will be stored and persisted locally and not affect live production or preview data. Wrangler will automatically create local versions of bindings found in wrangler.toml. These will not have data in them initially, so you will need to add data manually.
so what does it really mean by Wrangler will automatically create local versions of bindings found in wrangler.toml. ? how can I setup test this from my ci env?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Say, I want to do integration tests in our ci env which internet access is limited. my worker has dependency on worker kv, but i don't want it to connect to any remote place given the limit.
I had tried the following in the toml file:
and started with this command
npx wrangler dev -e ci
got the following errorsI can't run this command because no internet access, and it also asked for opening an url with browser, which is not possible in an automated ci env.
from the official doc, it mentioned
so what does it really mean by
Wrangler will automatically create local versions of bindings found in wrangler.toml.
? how can I setup test this from my ci env?Beta Was this translation helpful? Give feedback.
All reactions