Mount authorized S3 blobs with bounded independent copies #2
Loading…
Reference in a new issue
No description provided.
Delete branch "perf/authorized-blob-mount"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Promotion falls back to downloading and reuploading a blob when the dedupe cache cannot resolve it. Add an optional explicit-source S3 copy for existing repositories, preserving complete independent blobs and dedupe=false. Require source read and destination creation authority; unsupported settings and saturated work retain ordinary uploads. Bound active copies to two and share only identical authorized requests.
Support complete explicit static credentials or the production AWS environment pair without mutating the logged configuration, combining sources, or invoking metadata/default-chain providers. Preserve optional session-token handling, S3 retry behavior and immutable storage representation.
Validation: pinned Go1.25 image vet/race gate; API/storage fault and credential precedence tests; disposable RustFS multipart copy, concurrent requests, full digest reads and source deletion. Twenty matched storage-component pairs measured 703 to197ms median, without a whole-publication claim. Initial imagev2 supports explicit credentials only and remains undeployed. Corrected source991a5a1f is published by builder PR329 as imagev3. Full runtime qualification, exact external image copy and GitOps rollout are separate gates.
Pull request closed