[wrangler] Add automatic queue provisioning to resource provisioning #11788

irvinebroque · 2026-01-04T03:17:28Z

Extends the existing resource provisioning feature to support Cloudflare Queues. When users deploy with queue bindings configured, missing queues are now automatically created, just like KV, D1, and R2.

Changes:

Add QueueHandler class following the R2Handler pattern (name-based, no ID)
Add queue provisioning helper functions using ComplianceConfig
Collect and de-duplicate queues from both producers and consumers
Skip ensureQueuesExistByConfig when provisioning is enabled
Include delivery_delay in queue binding transformation
Update deploy tests to use --x-provision=false for legacy behavior tests

The feature is controlled by the existing --x-provision flag (enabled by default) and --x-auto-create flag for interactive vs automatic creation.

I've tested this out locally and deployed successfully. And reviewed code, left comments. Written with opencode.

Questions

Comfortable rolling this out as part of existing behavior without customers needing to add additional flags?

Tests
- Tests included/updated
Public documentation
- Cloudflare docs PR(s): Changelog for automated Queue provisioning cloudflare-docs#27396

…system Extends the existing resource provisioning feature to support Cloudflare Queues. When users deploy with queue bindings configured, missing queues are now automatically created, providing the same seamless experience as KV, D1, and R2. Changes: - Add QueueHandler class following the R2Handler pattern (name-based, no ID) - Add queue provisioning helper functions using ComplianceConfig - Collect and de-duplicate queues from both producers and consumers - Skip ensureQueuesExistByConfig when provisioning is enabled - Include delivery_delay in queue binding transformation - Update deploy tests to use --x-provision=false for legacy behavior tests The feature is controlled by the existing --x-provision flag (enabled by default) and --x-auto-create flag for interactive vs automatic creation.

changeset-bot · 2026-01-04T03:17:32Z

🦋 Changeset detected

Latest commit: b0ac2a1

The changes in this PR will be included in the next version bump.

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

claude · 2026-01-04T03:17:54Z

Claude finished @irvinebroque's task —— View job

Changeset Review

Reviewing changeset files...

Tasks:

Read changeset guidelines
Review changeset file
Validate against criteria
Check for animal images

⚠️ Issues found

The changeset .changeset/queue-provisioning.md has the following issue:

Markdown Headers: The changeset uses code blocks with JSONC format which is good, but there's a comment in the review from petebacondarwin noting "We prefer JSONC config nowadays" on this file. Looking at the changeset, it already uses jsonc in the code block, so this appears to be addressed correctly.

However, the changeset has one minor formatting issue:

Line 11: The comment syntax in the example uses // wrangler.jsonc which suggests a JSONC file, but the actual Workers configuration files are typically named wrangler.toml (TOML format) or wrangler.json (JSON format). The comment should clarify this is showing JSONC format as an example, or use the more standard wrangler.toml TOML format that most users have.

Other validation results:
✅ Version Type: Correctly set to minor (new feature)
✅ Changelog Quality: Excellent description with clear examples and feature list
✅ Markdown Headers: No h1/h2/h3 headers used (correctly uses h4 if any)
✅ No forbidden major version for wrangler

The changeset is well-written overall with good examples and clear explanations. The only suggestion is to clarify the configuration format being shown or use the more standard TOML format.

pkg-pr-new · 2026-01-04T03:21:02Z

create-cloudflare

npm i https://pkg.pr.new/create-cloudflare@11788

@cloudflare/kv-asset-handler

npm i https://pkg.pr.new/@cloudflare/kv-asset-handler@11788

miniflare

npm i https://pkg.pr.new/miniflare@11788

@cloudflare/pages-shared

npm i https://pkg.pr.new/@cloudflare/pages-shared@11788

@cloudflare/unenv-preset

npm i https://pkg.pr.new/@cloudflare/unenv-preset@11788

@cloudflare/vite-plugin

npm i https://pkg.pr.new/@cloudflare/vite-plugin@11788

@cloudflare/vitest-pool-workers

npm i https://pkg.pr.new/@cloudflare/vitest-pool-workers@11788

@cloudflare/workers-editor-shared

npm i https://pkg.pr.new/@cloudflare/workers-editor-shared@11788

@cloudflare/workers-utils

npm i https://pkg.pr.new/@cloudflare/workers-utils@11788

wrangler

npm i https://pkg.pr.new/wrangler@11788

commit: b0ac2a1

petebacondarwin · 2026-01-05T15:15:10Z

@irvinebroque - was this PR generated by AI? If so, although you said you have reviewed it, can you mention this for transparency in the PR description?

.changeset/queue-provisioning.md

packages/wrangler/src/deployment-bundle/bindings.ts

irvinebroque · 2026-01-04T03:23:42Z

packages/wrangler/src/deployment-bundle/bindings.ts

+				// Skip queues - they use queue name from config, no ID write-back needed
+				if (resourceType === "queues") {
+					continue;
+				}


Not obvious to me why this ended up being necessary, given that Queues should behave like R2 and I don't see equivalent here for R2

I think these are noops since the binding will be identical and the patch function below will find no difference.
So I think you can remove this check and the one below to simplify this code.

packages/wrangler/src/triggers/deploy.ts

packages/wrangler/src/versions/upload.ts

packages/wrangler/src/__tests__/provision.test.ts

petebacondarwin

Exciting to see this implemented but I think we can be a bit cleaner with the approach.

petebacondarwin · 2026-01-06T11:05:47Z

packages/wrangler/src/__tests__/provision.test.ts

+	return mock;
+}
+
+// Legacy helpers for backwards compatibility


I am not sure this comment is accurate. These helpers are not legacy nor related to backward compatibility. I would just delete this comment.

packages/wrangler/src/deployment-bundle/bindings.ts

petebacondarwin · 2026-01-06T11:27:43Z

packages/wrangler/src/deployment-bundle/bindings.ts

+				// Skip queues - they use queue name from config, no ID write-back needed
+				if (resourceType === "queues") {
+					continue;
+				}


I think these are noops since the binding will be identical and the patch function below will find no difference.
So I think you can remove this check and the one below to simplify this code.

petebacondarwin · 2026-01-06T11:37:18Z

packages/wrangler/src/deployment-bundle/bindings.ts

 	bindings: CfWorkerInit["bindings"],
-	requireRemote: boolean
+	requireRemote: boolean,
+	config?: Config


Rather than add a new parameter, just repurpose the complianceConfig parameter above. The actual object that is passed in there is always a Config anyway...

async function collectPendingResources( config: Config, accountId: string, scriptName: string, bindings: CfWorkerInit["bindings"], requireRemote: boolean }

petebacondarwin · 2026-01-06T11:47:07Z

packages/wrangler/src/deployment-bundle/bindings.ts

+		const resources =
+			resourceType === "queues" && config
+				? collectUniqueQueueBindings(config)
+				: bindings[resourceType] ?? [];


Rather than special casing here, I would rather we use polymorphism by adding a new method to the ProvisionResourceHandler class that returns the binding:

getResourcesFromConfig(config: Config | undefined, bindings: B[]) { return bindings; }

and then in the QueueHandler class:

getResourcesFromConfig(config: Config | undefined, bindings: B[]) { assert(config); return collectUniqueQueueBindings(config); }

and the call site would look like:

const resources = HANDLERS[resourceType].getResourcesFromConfig(config, bindings[resourceType] ?? []);

Ensures queue producer bindings include the `remote` field, matching the pattern used by R2 and other bindings that support remote mode.

Rather than special-casing queues in collectPendingResources, add a getResourcesFromConfig method to each handler in HANDLERS that can be overridden per resource type. QueueHandler's method calls collectUniqueQueueBindings to collect both producers and consumers. Also simplifies the function signature by using Config directly instead of ComplianceConfig, since Config is always passed in practice.

Clarify that the queue skipping in config patching is required because: 1. config.queues has a different shape (producers/consumers) than other bindings which are flat arrays 2. Queues use name-based identification so no ID write-back is needed

The mockListQueues and mockCreateQueue helpers are standard test utilities, not legacy helpers for backwards compatibility.

petebacondarwin · 2026-01-07T12:02:20Z

packages/wrangler/src/deployment-bundle/bindings.ts

+		getResourcesFromConfig: (
+			_config: Config,
+			bindings: CfKvNamespace[]
+		): CfKvNamespace[] => bindings,


My suggestion was for this to be a method on the handler (e.g. here KVHandler. The "standard" implementation will be on ProvisionResourceHandler and only the QueueHandler needs the method to be overridden.

Moreover, I believe that this method can use a type parameter to avoid having to cast the return values.

workers-devprod added this to workers-sdk Jan 4, 2026

github-project-automation bot moved this to Untriaged in workers-sdk Jan 4, 2026

irvinebroque requested review from MattieTK, danlapid, jonesphillip, lrapoport-cf and mia303 January 4, 2026 03:18

irvinebroque mentioned this pull request Jan 4, 2026

Changelog for automated Queue provisioning cloudflare/cloudflare-docs#27396

Draft

1 task

irvinebroque marked this pull request as ready for review January 4, 2026 03:47

irvinebroque requested a review from a team as a code owner January 4, 2026 03:47

petebacondarwin reviewed Jan 5, 2026

View reviewed changes

.changeset/queue-provisioning.md Outdated Show resolved Hide resolved

wrangler.jsonc instead of .toml

3ef2e35

irvinebroque force-pushed the bib/provision-queues branch from c34bbe1 to 3ef2e35 Compare January 5, 2026 20:56

Merge branch 'main' into bib/provision-queues

ed51767

irvinebroque commented Jan 5, 2026

View reviewed changes

petebacondarwin reviewed Jan 5, 2026

View reviewed changes

packages/wrangler/src/__tests__/provision.test.ts Outdated Show resolved Hide resolved

use mockListQueues

69eb0ad

petebacondarwin requested changes Jan 6, 2026

View reviewed changes

github-project-automation bot moved this from Untriaged to In Review in workers-sdk Jan 6, 2026

irvinebroque added 4 commits January 6, 2026 12:03

fix(wrangler): include remote field in queue bindings

8a0e78c

Ensures queue producer bindings include the `remote` field, matching the pattern used by R2 and other bindings that support remote mode.

docs(wrangler): remove misleading comment in provision tests

b0ac2a1

The mockListQueues and mockCreateQueue helpers are standard test utilities, not legacy helpers for backwards compatibility.

petebacondarwin requested changes Jan 7, 2026

View reviewed changes

[wrangler] Add automatic queue provisioning to resource provisioning #11788

Are you sure you want to change the base?

[wrangler] Add automatic queue provisioning to resource provisioning #11788

Uh oh!

Conversation

irvinebroque commented Jan 4, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Changes:

Questions

Uh oh!

changeset-bot bot commented Jan 4, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

🦋 Changeset detected

Uh oh!

claude bot commented Jan 4, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Changeset Review

Uh oh!

pkg-pr-new bot commented Jan 4, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

petebacondarwin commented Jan 5, 2026

Uh oh!

Uh oh!

Uh oh!

irvinebroque Jan 4, 2026

Choose a reason for hiding this comment

Uh oh!

petebacondarwin Jan 6, 2026

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

petebacondarwin left a comment

Choose a reason for hiding this comment

Uh oh!

petebacondarwin Jan 6, 2026

Choose a reason for hiding this comment

Uh oh!

irvinebroque Jan 6, 2026

Choose a reason for hiding this comment

Uh oh!

Uh oh!

petebacondarwin Jan 6, 2026

Choose a reason for hiding this comment

Uh oh!

petebacondarwin Jan 6, 2026

Choose a reason for hiding this comment

Uh oh!

petebacondarwin Jan 6, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

petebacondarwin Jan 7, 2026

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

irvinebroque commented Jan 4, 2026 •

edited

Loading

changeset-bot bot commented Jan 4, 2026 •

edited

Loading

claude bot commented Jan 4, 2026 •

edited

Loading

pkg-pr-new bot commented Jan 4, 2026 •

edited

Loading

petebacondarwin Jan 6, 2026 •

edited

Loading