fix(admin): keep exporting past unreadable configs and allow explicit target repair (#7247)

* test(ecstore): pin MinIO array-shaped targets blob as unreadable

* fix(admin): mark unreadable configs instead of aborting export

* feat(admin): opt-in replacement of unreadable bucket targets
This commit is contained in:
Zhengchao An
2026-09-06 10:03:32 +08:00
committed by GitHub
parent b59dea826f
commit 03fa62cc7d
8 changed files with 502 additions and 54 deletions
+6 -1
View File
@@ -50,8 +50,13 @@ cd "$(dirname "$0")/.."
# s3_error! stays flat at 1616.
# 1616 → 1613 on 2026-09-02: dependency refresh verified the current tree has
# already shed three s3_error! invocation lines; retighten the line counter.
# 1613 → 1589 on 2026-09-06: rustfs/backlog#2309 and rustfs/rustfs#7225 both
# folded the ten per-config arms of ExportBucketMetadata into one helper, which
# now reports an unreadable configuration as a plain string instead of raising
# an S3 error per arm (24 invocation lines removed from
# rustfs/src/admin/handlers/bucket_meta.rs; measured after merging the two).
S3S_IMPORT_FILES_BASELINE=213
S3_ERROR_LINES_BASELINE=1613
S3_ERROR_LINES_BASELINE=1589
# ecstore-scoped ratchet (rustfs/backlog#1842): the storage engine must not
# know S3 wire/DTO types (ARCHITECTURE.md invariant 4). The S3-*consuming*
# client was extracted to crates/s3-client, where s3s usage is legitimate;