Raúl MarínandClaude Opus 4.8 09dd198ae4 Force-anonymous all S3 prefixes on the disk metadata-load fallback ...

`forceAnonymousS3DiskConfig` (the pre-resolution fallback used when `load_anonymously` is set, instead of the
post-resolution per-prefix check) now rewrites every resolved S3 backend prefix -- the disk root and each
`locations.<name>` child -- not only the root. An `include` that resolves a `locations.<name>` S3 child with
server-managed auth no longer keeps its server identity (built with `for_disk_s3 = true`) when the disk is
loaded anonymous on restart.

Also add a regression that a persistent `ENGINE = S3(...)` table created with the opt-in refuses the first
restricted read: the create-time settings update establishes the client's restriction mode, so the restricted
read rebuilds an anonymous client and is refused rather than reusing the credentialed create-time client.

Co-Authored-By: Claude Opus 4.8 (1M context) <[email protected]>

2026-06-29 12:58:03 +00:00

..

configs

Clear SSE on explicit-key backups; reject NOSIGN+gcp_oauth disk child; fix 04325 backup case

2026-06-29 11:31:18 +00:00

__init__.py

…

test.py

Force-anonymous all S3 prefixes on the disk metadata-load fallback

2026-06-29 12:58:03 +00:00