Support hostname-specific fallbacks - #150
Open
ting-hong-shieh wants to merge 1 commit into
Open
Conversation
ting-hong-shieh
marked this pull request as ready for review
August 13, 2026 10:58
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds optional
hostnamesto fallback registry configurations and selects fallbacks using the incoming request hostname. Multiple configurations can match the same hostname, preserving the existing ordered fallback behavior.Configurations without
hostnamesremain default fallbacks. Existing configurations therefore keep their current behavior, while deployments with multiple registry domains can route each domain to its corresponding backend.The README includes JSONC and TOML configuration examples.
Fixes #81
Validation
pnpm test(58 tests)pnpm run typecheckpnpm run lintpnpm run format:check