|
1 | 1 | --- |
2 | 2 | pcx_content_type: concept |
3 | | -title: Automatic Resource Creation |
| 3 | +title: Automatically provision Cloudflare resources when deploying a Worker with Wrangler (Beta) |
4 | 4 | description: When you deploy a Worker that binds to a Cloudflare resource, Wrangler will automatically detect and create any resources that do not exist on your account. |
5 | 5 | sidebar: |
6 | 6 | badge: |
|
9 | 9 |
|
10 | 10 | import { PackageManagers, WranglerConfig } from "~/components"; |
11 | 11 |
|
12 | | -You can now automatically provision Cloudflare resources as part of your deployment. You no longer need to manually create any resources that do not yet exist on your account prior to deploying. |
| 12 | +You can now automatically provision Cloudflare resources as part of your deployment. You no longer need to manually run separate commands to create resources that do not yet exist on your account prior to deploying. |
13 | 13 |
|
14 | | -With resource provisioning, if your Wrangler configuration file includes a [KV namespace](/kv/), [D1 database](/d1/), or [R2 bucket](/r2/) that does not yet exist, Wrangler will create these resources upon deployment. This is done by adding the experimental `-–x-provision` flag to your commands. |
| 14 | +With resource provisioning, if your Wrangler configuration file includes a [KV namespace](/kv/), [D1 database](/d1/), or [R2 bucket](/r2/) that does not yet exist, Wrangler will detect and create these resources upon deployment. This is done by adding the experimental `-–x-provision` flag to your commands. |
15 | 15 |
|
16 | 16 | ## Wrangler Configuration |
17 | 17 | You can set up your Wrangler configuration file like the following: |
@@ -57,7 +57,7 @@ When you're ready to deploy, run: |
57 | 57 | args={"deploy –-x-provision"} |
58 | 58 | /> |
59 | 59 |
|
60 | | -Upon deploy Wrangler will automatically create the resources that do not yet exist on your accound and bind them to your Worker. |
| 60 | +Upon deploy, Wrangler will automatically create the resources that do not yet exist on your account and bind them to your Worker. Each newly created resource will be named with the format `<worker-name>-<binding-name>` by default. |
61 | 61 |
|
62 | 62 | ```bash |
63 | 63 | $ wrangler deploy --x-provision |
@@ -91,7 +91,5 @@ Deployed my-worker triggers |
91 | 91 | Current Version ID: ... |
92 | 92 | ``` |
93 | 93 |
|
94 | | -The newly created resource will be named with the format `<worker-name>-<binding-name>` by default. |
95 | | - |
96 | 94 | ## Feedback |
97 | | -Resource provisiong is currently a beta feature. If you run into issues or would like to leave feedback for the team to help us improve, please send us a message in our [Cloudflare Developers Discord](https://discord.cloudflare.com/) in the [Wrangler channel](https://discord.com/channels/595317990191398933/799437470004412476). |
| 95 | +Resource provisiong is currently in beta. Drop us a note in the [Cloudflare Developers Discord](https://discord.cloudflare.com/) in the [Wrangler channel](https://discord.com/channels/595317990191398933/799437470004412476) and tell us what you think. |
0 commit comments