5 Commits (7cedc5369d7a4bbe91ccb92a9d0b706ce0252138)

Author	SHA1	Message	Date
Harshavardhana	60d415bb8a	deprecate/remove global WORM mode (#9436) ... global WORM mode is a complex piece for which the time has passed, with the advent of S3 compatible object locking and retention implementation global WORM is sort of deprecated, this has been mentioned in our documentation for some time, now the time has come for this to go.	5 years ago
poornas	60e60f68dd	Add support for object locking with legal hold. (#8634)	5 years ago
poornas	f931fc7bfb	Fix retention enforcement in Compliance mode (#8556) ... In compliance mode, the retention date can be extended with governance bypass permissions	5 years ago
poornas	ca96560d56	Add object retention at the per object (#8528) ... level - this PR builds on #8120 which added PutBucketObjectLockConfiguration and GetBucketObjectLockConfiguration APIS This PR implements PutObjectRetention, GetObjectRetention API and enhances PUT and GET API operations to display governance metadata if permissions allow.	5 years ago
Bala FA	fb48ca5020	Add Get/Put Bucket Lock Configuration API support (#8120) ... This feature implements [PUT Bucket object lock configuration][1] and [GET Bucket object lock configuration][2]. After object lock configuration is set, existing and new objects are set to WORM for specified duration. Currently Governance mode works exactly like Compliance mode. Fixes #8101 [1] https://docs.aws.amazon.com/AmazonS3/latest/API/RESTBucketPUTObjectLockConfiguration.html [2] https://docs.aws.amazon.com/AmazonS3/latest/API/RESTBucketGETObjectLockConfiguration.html	5 years ago