InseeFrLab / InseeFrLab/s3-operator
Support for Lifecycle rules
Open
- Dominant language
- Go
- Stars
- 66
- Forks
- 16
- PR merge metrics
- No merged PRs in 30d
Description
There is currently no built-in support for Lifecycle Rules configuration.
I would love being able to configure a expiry rule to delete all objects that passes 30 days of life, as code, within the Bucket CRD or within a new one.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by locating the Bucket CRD and the operator's existing bucket configuration handling. Determine whether lifecycle rules should be added to the Bucket CRD or represented by a new CRD, using the requested 30-day object expiry as the initial case. Done means lifecycle expiry can be configured declaratively and is applied to the S3 bucket.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, go, kubernetes
- Domain
- cloud, devops
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100