From 678aaf3ab782db3e1f316eefab2caa513b90b7e3 Mon Sep 17 00:00:00 2001 From: Brendan Irvine-Broque Date: Sat, 3 Jan 2026 19:45:43 -0800 Subject: [PATCH 1/2] Changelog for automated Queue provisioning --- ...026-01-03-automatic-queue-provisioning.mdx | 40 +++++++++++++++++++ 1 file changed, 40 insertions(+) create mode 100644 src/content/changelog/queues/src2026-01-03-automatic-queue-provisioning.mdx diff --git a/src/content/changelog/queues/src2026-01-03-automatic-queue-provisioning.mdx b/src/content/changelog/queues/src2026-01-03-automatic-queue-provisioning.mdx new file mode 100644 index 000000000000000..a67ba39e37a6dfc --- /dev/null +++ b/src/content/changelog/queues/src2026-01-03-automatic-queue-provisioning.mdx @@ -0,0 +1,40 @@ +--- +title: Automatic queue provisioning +description: Wrangler now creates queues automatically when you deploy Workers with queue bindings. +products: + - queues + - workers +date: 2026-01-03 +--- + +import { WranglerConfig } from "~/components"; + +You no longer need to create queues manually before deploying. When you run `wrangler deploy` with queue bindings in your config, Wrangler creates any missing queues automatically. + +To add a queue to your Worker, just define the binding in your configuration file: + + + +```toml +[[queues.producers]] +binding = "MY_QUEUE" +queue = "my-queue" + +[[queues.consumers]] +queue = "my-queue" +max_batch_size = 10 +``` + + + +Then deploy: + +```sh +npx wrangler deploy +``` + +If no queue named `my-queue` exists, Wrangler will create one before deploying your Worker. This works for both producer and consumer bindings. When the same queue appears in both, Wrangler creates it once. + +This matches how [KV, D1, and R2 provisioning](/changelog/workers/2025-10-24-automatic-resource-provisioning/) works. To disable automatic provisioning, use the `--no-x-provision` flag. + +For more on queue configuration, refer to [Configure Queues](/queues/configuration/configure-queues/). \ No newline at end of file From 9ec7074981d0d00109e546126fab4a1d717debcc Mon Sep 17 00:00:00 2001 From: Brendan Irvine-Broque Date: Mon, 5 Jan 2026 13:19:14 -0800 Subject: [PATCH 2/2] Add Queues to auto provisioning supported resources list --- .../docs/workers/wrangler/configuration.mdx | 21 ++++++++++--------- 1 file changed, 11 insertions(+), 10 deletions(-) diff --git a/src/content/docs/workers/wrangler/configuration.mdx b/src/content/docs/workers/wrangler/configuration.mdx index 1668a638f99d191..64537cc486face8 100644 --- a/src/content/docs/workers/wrangler/configuration.mdx +++ b/src/content/docs/workers/wrangler/configuration.mdx @@ -78,11 +78,17 @@ Further, there are a few keys that can _only_ appear at the top-level. ## Automatic provisioning - + + + + Wrangler can automatically provision resources for you when you deploy your Worker without you having to create them ahead of time. -This currently works for KV, R2, and D1 bindings. +This currently works for KV, R2, D1, and Queues bindings. To use this feature, add bindings to your configuration file _without_ adding resource IDs, or in the case of R2, a bucket name. Resources will be created with the name of your worker as the prefix. @@ -1451,14 +1457,9 @@ A common example of using a redirected configuration is where a custom build too - `my-tool` generates a `dist` directory that contains both compiled code and a new generated deployment configuration file, containing only the settings for the given environment. It also creates a `.wrangler/deploy/config.json` file that redirects Wrangler to the new, generated deployment configuration file: - - - dist - - index.js - - wrangler.jsonc - - .wrangler - - deploy - - config.json - + + - dist - index.js - wrangler.jsonc - .wrangler - deploy - config.json + The generated `dist/wrangler.jsonc` might contain: