Skip to content

Commit 5ec2080

Browse files
authored
Update 2025-10-24-automatic-resource-provisioning.mdx
1 parent 8582d28 commit 5ec2080

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

src/content/changelog/workers/2025-10-24-automatic-resource-provisioning.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ import { Render, TypeScriptExample, WranglerConfig } from "~/components";
1010

1111
Previously, if you wanted to develop or deploy a worker with attached resources, you'd have to first manually create the desired resources. Now, if your Wrangler configuration file includes a KV namespace, D1 database, or R2 bucket that does not yet exist on your account, you can develop locally and deploy your application seamlessly, without having to run additional commands.
1212

13-
Automatic provisioning is still experimental, but we're turning it on by default to make it easier to try out and test. It currently works for KV, R2, and D1 bindings. You can disable the feature using the `--no-x-provision` flag.
13+
Automatic provisioning is launching as an open beta, and we'd love to hear your feedback to help us make improvements! It currently works for KV, R2, and D1 bindings. You can disable the feature using the `--no-x-provision` flag.
1414

1515
To use this feature, update to [email protected] and add bindings to your config file _without_ resource IDs e.g.:
1616

0 commit comments

Comments
 (0)