Add expiration lifecycle support #60
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
The PR extends
Buckettype to allow specifyingLifecycleRulesfor the bucket. Currently it only supports the basic of expiration (removal).It is a minor feature that would allow basic lifecycle management, but in future it can be extended to also allow tiering option. But it would make sense to add that after tiering is supported from the provider - for example, if a new type for that would be made to manage tiering, then it would be easy to link the lifecycle rule to it.
This is related to #59.
Checklist
bug,enhancement,documentation,change,breaking,dependencyas they show up in the changelog