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

This commit is contained in:
overtrue
2026-09-06 02:20:59 +08:00
parent 29086ab7bc
commit 7b2563158b
2 changed files with 343 additions and 242 deletions
+5 -1
View File
@@ -50,8 +50,12 @@ 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 → 1580 on 2026-09-06: rustfs/backlog#2309 folded the ten per-config
# arms of ExportBucketMetadata into `export_config_bytes`, which reports an
# unreadable configuration as a plain string instead of raising an S3 error per
# arm (33 invocation lines removed from rustfs/src/admin/handlers/bucket_meta.rs).
S3S_IMPORT_FILES_BASELINE=213
S3_ERROR_LINES_BASELINE=1613
S3_ERROR_LINES_BASELINE=1580
# 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;