Use well-known expiration attribute for SGs #205
Merged
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
cthulhu-rider
approved these changes
Mar 10, 2022
|
carpawell
approved these changes
Mar 10, 2022
cthulhu-rider
previously approved these changes
Mar 16, 2022
fyrchik
previously approved these changes
Mar 17, 2022
To avoid ambiguity, let's use the common well-known attribute to control both Object and Storage Group expirations. Signed-off-by: Stanislav Bogatyrev <stanislav@nspcc.ru>
carpawell
approved these changes
Mar 29, 2022
cthulhu-rider
approved these changes
May 25, 2022
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.
To avoid ambiguity, let's use the common well-known attribute to control both Object and Storage Group expirations.
This change affects the whole stack, including Storage and Inner Ring nodes logic. Should be merged only when we are ready to change implementation.