Skip to content

Commit b628009

Browse files
Update src/content/changelog/workers/2025-10-24-automatic-resource-provisioning.mdx
Co-authored-by: lrapoport-cf <[email protected]>
1 parent b4a007a commit b628009

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
@@ -8,7 +8,7 @@ date: 2025-10-24
88

99
import { Render, TypeScriptExample, WranglerConfig } from "~/components";
1010

11-
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 to create resources.
11+
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

1313
This is still an experimental feature, but we're turning it on 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 KV, R2, and D1 bindings.
1414

0 commit comments

Comments
 (0)