Repository navigation
[wrangler] Use FedRAMP container registries - #15196
Conversation
🦋 Changeset detectedLatest commit: 59d1808 The changes in this PR will be included in the next version bump. This PR includes changesets to release 3 packages
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 |
|
Codeowners approval required for this PR:
Show detailed file reviewers |
|
The change is complete and consistent. All production call sites propagate the compliance config, the registry naming logic ( I verified the changes are for PR #15196 (branch LGTM |
@cloudflare/autoconfig
@cloudflare/build-output-utils
@cloudflare/config
create-cloudflare
@cloudflare/deploy-helpers
@cloudflare/kv-asset-handler
miniflare
@cloudflare/pages-functions
@cloudflare/pages-shared
@cloudflare/unenv-preset
@cloudflare/vite-plugin
@cloudflare/vitest-pool-workers
@cloudflare/workers-auth
@cloudflare/workers-editor-shared
@cloudflare/workers-utils
wrangler
commit: |
9f8ea9d to
0c64224
Compare
|
✅ All changesets look good |
workers-devprod
left a comment
There was a problem hiding this comment.
Codeowners reviews satisfied
Select the managed container registry from both the Wrangler compliance region and API environment, while preserving the explicit registry override. Propagate compliance config through deploy, build, image, registry, local dev, and Vite plugin paths.
0c64224 to
59d1808
Compare
Select the managed container registry from both the Wrangler compliance region and API environment, while preserving the explicit registry override. Propagate compliance config through deploy, build, image, registry, local dev, and Vite plugin paths.
Fix Wrangler's managed container registry selection when compliance_region or CLOUDFLARE_COMPLIANCE_REGION is set to fedramp_high.
Previously Wrangler selected the FedRAMP High API endpoint, but container workflows could continue using the public managed registry, resulting in registry lookup failures. The registry is now selected from both the compliance region and API environment:
Public production: registry.cloudflare.com
Public staging: staging.registry.cloudflare.com
FedRAMP High production: registry.fed.cloudflare.com
FedRAMP High staging: staging.registry.fed.cloudflare.com
The compliance config is propagated through container builds, pushes, deployments, image and registry commands, local development, and the Vite plugin. CLOUDFLARE_CONTAINER_REGISTRY remains the highest-priority override.
A picture of a cute animal (not mandatory, but encouraged)