Skip to content

feat(cloudflare/containers): expose placement jurisdiction constraints - #1340

Open
yovanoc wants to merge 2 commits into
alchemy-run:mainfrom
yovanoc:fix/container-constraints-jurisdiction
Open

feat(cloudflare/containers): expose placement jurisdiction constraints#1340
yovanoc wants to merge 2 commits into
alchemy-run:mainfrom
yovanoc:fix/container-constraints-jurisdiction

Conversation

@yovanoc

@yovanoc yovanoc commented Aug 24, 2026

Copy link
Copy Markdown
Contributor

Summary

  • expose typed regional placement constraints on Cloudflare.Container applications
  • expose the Cloudflare Containers jurisdiction placement boundary (eu/fedramp)
  • document the placement fields without changing defaults or runtime behavior

Context

A downstream application needs a typed, fail-closed way to request an EU-resident native Container. The current Alchemy surface leaves constraints as an untyped object, while the Containers API accepts placement constraints. This keeps the change at the Alchemy API boundary; it does not claim that every account/plan has EU Container capacity.

The async binding collision is separately fixed by #1271.

Validation

  • git diff --check
  • bunx oxfmt --check packages/alchemy/src/Cloudflare/Containers/ContainerApplication.ts
  • Container integration tests require the repository's full alchemy-test/distilled workspace and were not runnable from this cached checkout.

@sam-goodwin

Copy link
Copy Markdown
Contributor

update PR description to show DX, not bullet point text

@sam-goodwin

Copy link
Copy Markdown
Contributor

Missing a test fixture

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants