fix(bucket-tenants): make tenant lifecycle and bucket import validation safer
This commit is contained in:
@@ -1,5 +1,20 @@
|
||||
# Changelog
|
||||
|
||||
## 2026-05-02 - 6.5.1 - fix(bucket-tenants)
|
||||
make tenant lifecycle and bucket import validation safer
|
||||
|
||||
- validate exported object size and MD5 before creating and importing target buckets
|
||||
- persist bucket-tenant credential changes with rollback when bucket creation or deletion fails
|
||||
- require auth-enabled access and matching tenant credentials for tenant list, descriptor, and recursive delete flows
|
||||
|
||||
## Next - fix(bucket-tenants)
|
||||
make tenant lifecycle and bucket import validation safer
|
||||
|
||||
- Validate bucket export object size and MD5 before creating/importing into target buckets.
|
||||
- Persist tenant credentials through snapshot-aware helpers and roll back credential changes if bucket create/delete fails.
|
||||
- Require matching tenant credentials before `deleteBucketTenant({ bucketName })` can recursively delete a bucket.
|
||||
- Enforce `auth.enabled` consistently on tenant list/descriptor APIs and document metadata-only credential listings.
|
||||
|
||||
## 2026-05-02 - 6.5.0 - feat(bucket-tenants)
|
||||
add persisted bucket-scoped tenant credentials with bucket export and import APIs
|
||||
|
||||
|
||||
Reference in New Issue
Block a user