Chris LuandGitHub e696c2585e s3 remote: honor s3.support_tagging in UpdateFileMetadata (#10532) ...

* s3 remote: honor s3.support_tagging in UpdateFileMetadata

The write path already skips tagging when the remote is configured
without tagging support, but the metadata-update path sent
PutObjectTagging or DeleteObjectTagging unconditionally. On remotes
that reject tagging requests, any metadata update failed -- including
updates with no tags at all, which land on the DeleteObjectTagging
branch.

* s3 remote: drop the never-read supportTagging field

Every maker set it, nothing read it: the tagging decision is made from
conf.S3SupportTagging. Keeping a field that looks like the switch but
is not invites exactly the inconsistency the previous commit fixed.

2026-08-01 20:18:59 -07:00

..

azure

remote storage: actually delete objects when a directory is removed (#10531)

2026-08-01 20:11:41 -07:00

gcs

remote storage: actually delete objects when a directory is removed (#10531)

2026-08-01 20:11:41 -07:00

s3

s3 remote: honor s3.support_tagging in UpdateFileMetadata (#10532)

2026-08-01 20:18:59 -07:00

remote_storage.go

preserve Content-Encoding for remote-mounted objects (#10340)

2026-07-15 19:20:00 -07:00

track_sync_offset.go

chore: execute goimports to format the code (#7983)

2026-01-07 13:06:08 -08:00