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
* Enable provisioning
* Create thirty-walls-film.md
* remove .only
* Update thirty-walls-film.md
* Make experimental nature clearer
* Make sure we don't write redirected config bindings to the user config file
* remove only
Enable automatic resource provisioning by default in Wrangler. This is still an experimental feature, but we're turning on the flag by default to make it easier for people to test it and try it out. You can disable the feature using the `--no-x-provision` flag. It currently works for R2, D1, and KV bindings.
6
+
7
+
To use this feature, add a binding to your config file _without_ a resource ID:
8
+
9
+
```jsonc
10
+
{
11
+
"kv_namespaces": [{ "binding":"MY_KV" }],
12
+
"d1_databases": [{ "binding":"MY_DB" }],
13
+
"r2_buckets": [{ "binding":"MY_R2" }]
14
+
}
15
+
```
16
+
17
+
`wrangler dev` will automatically create these resources for you locally, and when you next run `wrangler deploy` Wrangler will call the Cloudflare API to create the requested resources and link them to your Worker. They'll stay linked across deploys, and you don't need to add the resource IDs to the config file for future deploys to work. This is especially good for shared templates, which now no longer need to include account-specific resource ID when adding a binding.
Worker Version ID: 00000000-0000-0000-0000-000000000000
222
-
To deploy this version to production traffic use the command wrangler versions deploy
223
-
Changes to non-versioned settings (config properties 'logpush' or 'tail_consumers') take effect after your next deployment using the command wrangler versions deploy
224
-
Changes to triggers (routes, custom domains, cron schedules, etc) must be applied with the command wrangler triggers deploy"
225
-
`);
203
+
"Total Upload: xx KiB / gzip: xx KiB
204
+
Experimental: The following bindings need to be provisioned:
205
+
Binding Resource
206
+
env.KV2 KV Namespace
207
+
Provisioning KV2 (KV Namespace)...
208
+
🌀 Creating new KV Namespace "tmp-e2e-worker-00000000-0000-0000-0000-000000000000-kv2"...
209
+
✨ KV2 provisioned 🎉
210
+
🎉 All resources provisioned, continuing with deployment...
Worker Version ID: 00000000-0000-0000-0000-000000000000
218
+
To deploy this version to production traffic use the command wrangler versions deploy
219
+
Changes to non-versioned settings (config properties 'logpush' or 'tail_consumers') take effect after your next deployment using the command wrangler versions deploy
220
+
Changes to triggers (routes, custom domains, cron schedules, etc) must be applied with the command wrangler triggers deploy"
0 commit comments