feat(storage): add named S3-compatible backends via s3+<name>:// URIs#1
Merged
Conversation
- storage.s3.named.<name> config map for arbitrary S3-compatible endpoints (separate creds, region, endpoint, checksum, flags per entry). - URIs of the form s3+<name>://bucket/path route to the named backend; plain s3:// continues to use the primary endpoint. - Preserve the s3+<name> qualifier through Uri::parse_str normalization so the resolver can recover the backend name on deserialization (previously the qualifier was stripped and named URIs silently resolved to the primary endpoint). - Tests: URI parse/serde roundtrip, NamedS3StorageConfig serde + redact + as_s3_config projection, parse_named_key. - Docs: list s3+<name>:// in the URI protocols and add a Named S3 backends section with a YAML example. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
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
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
Why
The PoC needed A/B comparisons across Civo S3, SeaweedFS S3 (in-cluster), and OVH Object Storage on the same Quickwit cluster. Upstream Quickwit supports a single S3-compatible endpoint per cluster. This change makes multi-backend addressable per-index without forking the storage layer.
Changes
Tests
Test plan
🤖 Generated with Claude Code