Actions
Cleanup #64658
closedmgr/dashboard: Locking improvements in bucket create form
% Done:
100%
Tags:
backport_processed
Backport:
Reviewed:
Affected Versions:
Pull request ID:
Description
Summary of Improvements:
- Rename to 'Object Locking'
- If locking is enabled the versioning needs to be default enabled. We need to show info message to let user know.
- Add info texts
- Meaning of modes(GOVERNANCE or COMPLIANCE) and what each one does.
- Improve form alignment
Detailed changes:
- Rename to 'Object Locking'
- If locking is enabled the versioning needs to be default enabled. We need to show info message to let user know.
- Add info texts
- Meaning of modes({*}GOVERNANCE{*} or {*}COMPLIANCE{*}) and what each one does.
Info texts
Meaning: Store objects using a write-once-read-many (WORM) model to help you prevent objects from being deleted or overwritten for a fixed amount of time or indefinitely. Object Lock works only in versioned buckets.
Warning: Enabling Object Lock will allow the configuration of GOVERNANCE, COMPLIANCE or LEGAL HODE modes, which will help ensure that an object version cannot be overwritten or deleted for the specified period.
- In GOVERNANCE mode, users cannot overwrite or delete an object version or alter its lock settings unless they have special permissions.
- In COMPLIANCE mode, a protected object version cannot be overwritten or deleted by any user, including the root user in your AWS account. When an object is locked in COMPLIANCE mode, its RETENTION_MODE cannot be changed, and its retention period cannot be shortened. COMPLIANCE mode helps ensure that an object version cannot be overwritten or deleted for the duration of the period.
- Set default value for RETENTION to 10 days(maybe) rather than 0
Bucket Versioning can't be disabled when Object Lock is enabled.
Updated by Afreen Misbah about 2 months ago
- Description updated (diff)
- Status changed from In Progress to Fix Under Review
- % Done changed from 0 to 80
Updated by Pedro González Gómez about 2 months ago
- Tracker changed from Tasks to Cleanup
- Backport set to reef, squid
- Pull request ID set to 55866
moved tracker to cleanup to include backports
Updated by Pedro González Gómez about 2 months ago
- Status changed from Fix Under Review to Pending Backport
Updated by Backport Bot about 2 months ago
- Copied to Backport #64829: squid: mgr/dashboard: Locking improvements in bucket create form added
Updated by Backport Bot about 2 months ago
- Copied to Backport #64830: reef: mgr/dashboard: Locking improvements in bucket create form added
Updated by Afreen Misbah about 1 month ago
- Status changed from Pending Backport to Resolved
- Tags deleted (
backport_processed)
Updated by Afreen Misbah about 1 month ago
- Status changed from Resolved to Pending Backport
- Tags set to backport_processed
Updated by Nizamudeen A about 1 month ago
- Status changed from Pending Backport to Resolved
Actions