[S3] Configuration of default object lock settings

[aljoshare]

Is your feature request related to a problem?

Currently, the S3 operator only supports to enable/disable the object lock for new objects but it doesn't allow to customize the object lock configuration (e.g. the default retention or the default retention mode).

Describe the solution you'd like

As a user I would like to be able to customize the default object lock configuration (e.g. set the default retention or the default retention mode) similar to the AWS console:

The Terraform provider: https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/s3_bucket_object_lock_configuration#default_retention).

The AWS CLI: https://awscli.amazonaws.com/v2/documentation/api/latest/reference/s3api/put-object-lock-configuration.html

I would love to see something similar to this:

objectLock:
  enabled: true 
  default:
   retention: 1d // or e.g. 1y
   mode: governance // or compliance

I discussed the topic in Slack and @A-Hilaly suggested that it could be solved by using https://docs.aws.amazon.com/AmazonS3/latest/API/API_PutObjectLockConfiguration.html.

Describe alternatives you've considered None

Thank you very much! :heart:

[jaypipes]

I wonder why there is a "Disable" option in the AWS Console since it's pretty clear that once you enable Object Lock, you cannot disable it....

[jaypipes]

This is doable, but the whole "cannot disable once enabled" thing will need to be custom coded...

[ack-bot]

Issues go stale after 90d of inactivity. Mark the issue as fresh with /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close. If this issue is safe to close now please do so with /close. Provide feedback via https://github.com/aws-controllers-k8s/community. /lifecycle stale

[aljoshare]

/remove-lifecycle stale

[ack-bot]

Issues go stale after 90d of inactivity. Mark the issue as fresh with /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close. If this issue is safe to close now please do so with /close. Provide feedback via https://github.com/aws-controllers-k8s/community. /lifecycle stale

[ack-bot]

Stale issues rot after 30d of inactivity. Mark the issue as fresh with /remove-lifecycle rotten. Rotten issues close after an additional 30d of inactivity. If this issue is safe to close now please do so with /close. Provide feedback via https://github.com/aws-controllers-k8s/community. /lifecycle rotten

[ack-bot]

Issues go stale after 180d of inactivity. Mark the issue as fresh with /remove-lifecycle stale. Stale issues rot after an additional 60d of inactivity and eventually close. If this issue is safe to close now please do so with /close. Provide feedback via https://github.com/aws-controllers-k8s/community. /lifecycle stale

[ack-bot]

Stale issues rot after 60d of inactivity. Mark the issue as fresh with /remove-lifecycle rotten. Rotten issues close after an additional 60d of inactivity. If this issue is safe to close now please do so with /close. Provide feedback via https://github.com/aws-controllers-k8s/community. /lifecycle rotten

[gecube]

/remove-lifecycle rotten

[ack-bot]

Issues go stale after 180d of inactivity. Mark the issue as fresh with /remove-lifecycle stale. Stale issues rot after an additional 60d of inactivity and eventually close. If this issue is safe to close now please do so with /close. Provide feedback via https://github.com/aws-controllers-k8s/community. /lifecycle stale

[gecube]

/remove-lifecycle stale