Chris LuandDevin 78893d274a filer.sync: sign proxied chunk I/O from the per-side security file ...

The -a.security / -b.security files were used for gRPC TLS and the
HTTPS client but not for jwt.filer_signing, so filer-proxied chunk
reads and writes carried a token signed with the process-wide key and
failed authorization whenever the two clusters' keys differ.

LoadFilerJwtFromFile returns a FilerJwtProvider for each side's file,
which FilerSource and FilerSink now accept for proxied chunk reads and
writes. With no keys in the file or no flag, both fall back to the
process-wide jwt.filer_signing configuration as before.

Generated with [Devin](https://devin.ai)

Co-Authored-By: Devin <158243242+devin-ai-integration[bot]@users.noreply.github.com>

2026-10-07 07:28:17 -07:00

..

repl_util

filer: authorize the chunk proxy and the root listing like the rest of the filer port (#11152)

2026-09-04 16:39:36 -07:00

sink

filer.sync: sign proxied chunk I/O from the per-side security file

2026-10-07 07:28:17 -07:00

source

filer.sync: sign proxied chunk I/O from the per-side security file

2026-10-07 07:28:17 -07:00

sub

filer.replicate: acknowledge notifications after the sink write, not on receipt (#10427)

2026-07-24 10:43:48 -07:00

replicator_test.go

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

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

replicator.go

fix(filer.sync): replicate a rename as an atomic move, not a no-op update (#9895)

2026-06-09 12:54:28 -07:00