-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Remove image registry validation for containers on deploy #11559
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
🦋 Changeset detectedLatest commit: eb35fe9 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 |
|
Failed to automatically backport this PR's changes to Wrangler v3. Please manually create a PR targeting the Depending on your changes, running Notes:
|
create-cloudflare
@cloudflare/kv-asset-handler
miniflare
@cloudflare/pages-shared
@cloudflare/unenv-preset
@cloudflare/vite-plugin
@cloudflare/vitest-pool-workers
@cloudflare/workers-editor-shared
@cloudflare/workers-utils
wrangler
commit: |
emily-shen
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
and thank you for the otters
Fixes CC-6542
Some users have a capability which allows them to have more image registries then just the managed registry + supported external registries. The current validation in wrangler is too strict and breaks this workflow. The correct way to validate would be to compare against the valid registries returned from
GET /registries. However, since the point of wrangler validation is quick feedback, this validation is skipped and left to be handled by the API.A picture of a cute animal (not mandatory, but encouraged)
:)