Chris Lu aa48658739 replication: use the side filer read key for manifest downloads and fall back per access level ...

Manifest chunk resolution still signed proxied downloads with the
process-wide read key, so a source filer requiring its own key 401'd on
manifest-bearing files. A side security file that set only one access
level also produced empty tokens for the other instead of inheriting the
process-wide key, and the side file loader ignored the WEED_ environment
overrides the filer itself honors.

ResolveChunkManifest/ResolveOneChunkManifest keep their signatures;
FilerJwt-aware variants thread the provider down to fetchWholeChunk,
which prefers it on proxy URLs. The side loader now applies the same
environment precedence and falls back to the process-wide signer per
missing access level.

2026-10-07 08:43:02 -07:00

..

azuresink

filer.backup, filer.sync: stop sharing resume checkpoints across destinations (#10934)

2026-08-24 19:30:20 -07:00

b2sink

filer.backup, filer.sync: stop sharing resume checkpoints across destinations (#10934)

2026-08-24 19:30:20 -07:00

filersink

replication: use the side filer read key for manifest downloads and fall back per access level

2026-10-07 08:43:02 -07:00

gcssink

filer.backup, filer.sync: stop sharing resume checkpoints across destinations (#10934)

2026-08-24 19:30:20 -07:00

localsink

filer.backup, filer.sync: stop sharing resume checkpoints across destinations (#10934)

2026-08-24 19:30:20 -07:00

s3sink

s3 sink: report the source read error the SDK hides (#11277)

2026-09-11 19:44:30 -07:00

replication_sink.go

filer.backup, filer.sync: stop sharing resume checkpoints across destinations (#10934)

2026-08-24 19:30:20 -07:00