-
Notifications
You must be signed in to change notification settings - Fork 82
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: add object retention feature #2277
Merged
+548
−21
Merged
Changes from 1 commit
Commits
Show all changes
16 commits
Select commit
Hold shift + click to select a range
dcc0ca4
feat: add object retention feature
JesseLovelace 7b4a2a7
🦉 Updates from OwlBot post-processor
gcf-owl-bot[bot] 876c293
Merge branch 'main' into objlock
JesseLovelace b620c67
address review comments
JesseLovelace 862a564
🦉 Updates from OwlBot post-processor
gcf-owl-bot[bot] dc6d226
Add a workaround to avoid a testbench failure
JesseLovelace 7ca2178
Merge branch 'objlock' of github.com:googleapis/java-storage into obj…
JesseLovelace 40ae1f8
chore: some fixes from pairing with jesse
BenWhitehead 5fd0937
chore: put a `!` :don't program while sleepy:
BenWhitehead 9159db3
chore: mvn-fmt
BenWhitehead 70c9c5e
add a way to avoid using the objectRetentionField in bucket tests
JesseLovelace 52eecf7
add retention to blobfield tests
JesseLovelace e16abae
clirr and fmt
JesseLovelace 3bc56f6
add todos
JesseLovelace abd314c
fmt
JesseLovelace 2f9f38b
Merge branch 'main' into objlock
JesseLovelace File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
chore: mvn-fmt
commit 9159db3fb3eae2a7b10b2658e8145cb5f29d61b5
There are no files selected for viewing
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What was the conclusion on detecting if a user set retention to null vs. it not being modified?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It doesn't work, due to the modified fields not being passed along to the final patch call. I talked to ben and we agreed to just do it this way, there's precedent for it in the logging encoding
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for clarifying, is this value mutable once set?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Only certain cases work (i.e. going from Unlocked to Locked, reducing the retainUntilTime on an unlocked policy, and setting to null), and you have to pass in
overrideUnlockedRetention
for any of those cases to work, but yes