Add regional and jurisdictional placement constraints

[must108]

Fixes #13570

This merge request adds support for constraints.regions and constraints.jurisdiction in the container configuration, allowing users to control where their containers run.

• Tests
  • Tests included/updated
  • Automated tests not possible - manual testing has been completed as follows:
  • Additional testing not necessary because:
• Public documentation
  • Cloudflare docs PR(s): Add placement docs for containers cloudflare-docs#29936
  • Documentation not necessary because:

---

[changeset-bot]

🦋 Changeset detected

Latest commit: 609a434

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

[workers-devprod]

Codeowners approval required for this PR:

• ✅ @cloudflare/cloudchamber
• ✅ @cloudflare/wrangler

Show detailed file reviewers

[devin-ai-integration]

✅ Devin Review: No Issues Found

Devin Review analyzed this PR and found no potential bugs to report.

View in Devin Review to see 3 additional findings.

[pkg-pr-new]

create-cloudflare

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

@cloudflare/kv-asset-handler

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

miniflare

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

@cloudflare/pages-shared

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

@cloudflare/unenv-preset

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

@cloudflare/vite-plugin

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

@cloudflare/vitest-pool-workers

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

@cloudflare/workers-editor-shared

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

wrangler

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

commit: 5032f38

[emily-shen]

would you be able to add a test to containers/deploy.test.ts as well?

[must108]

would you be able to add a test to containers/deploy.test.ts as well?

I added tests in validation.ts and normalize-and-validate-config.test.ts. Are these sufficient? With these tests, adding to deploy.test.ts would be redundant. I could remove the tests I wrote and add to deploy.test.ts if it is better.

[devin-ai-integration]

Devin Review found 1 new potential issue.

🐛 1 issue in files not directly in the diff

🐛 Jurisdiction validation is case-sensitive, rejecting valid uppercase input that normalization would handle (packages/workers-utils/src/config/validation.ts:3527-3528)

The jurisdiction validation in packages/workers-utils/src/config/validation.ts:3527-3528 checks !['eu', 'fedramp'].includes(constraints.jurisdiction) without lowercasing the input first. This means a user who writes jurisdiction = "EU" or jurisdiction = "FedRAMP" in their config will get a validation error. This is inconsistent with how regions is validated just below (validRegions.includes(region.toUpperCase()) at line 3549), which does case-insensitive comparison. The normalization code in packages/wrangler/src/containers/config.ts:118 calls .toLowerCase(), confirming case-insensitive input was intended. Since validation runs before normalization, any non-lowercase jurisdiction value will be rejected before it can be normalized. The test at packages/wrangler/src/__tests__/containers/config.test.ts:462 uses jurisdiction: "EU" and expects "eu" as output, but this only passes because the test bypasses validation via as Partial<Config> as Config.

View 5 additional findings in Devin Review.

[emily-shen]

would you be able to add a test to containers/deploy.test.ts as well?

I added tests in validation.ts and normalize-and-validate-config.test.ts. Are these sufficient? With these tests, adding to deploy.test.ts would be redundant. I could remove the tests I wrote and add to deploy.test.ts if it is better.

It's not entirely redundant (there is some overlap though) because deploy also tests these values get passed to the API as expected. you could probably just set some jurisdiction/region values in an existing test in deploy.test.ts and update a snapshot.

[workers-devprod]

Codeowners reviews satisfied

[must108]

would you be able to add a test to containers/deploy.test.ts as well?

I added tests in validation.ts and normalize-and-validate-config.test.ts. Are these sufficient? With these tests, adding to deploy.test.ts would be redundant. I could remove the tests I wrote and add to deploy.test.ts if it is better.

It's not entirely redundant (there is some overlap though) because deploy also tests these values get passed to the API as expected. you could probably just set some jurisdiction/region values in an existing test in deploy.test.ts and update a snapshot.

@emily-shen done!