Skip to content
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

storage: add support for object retention #6741

Closed
JesseLovelace opened this issue Oct 27, 2023 · 0 comments · Fixed by #6829
Closed

storage: add support for object retention #6741

JesseLovelace opened this issue Oct 27, 2023 · 0 comments · Fixed by #6829
Assignees
Labels
api: storage Issues related to the Cloud Storage API.

Comments

@JesseLovelace
Copy link

Please implement the object retention feature. The following operations must be supported:

  • Create a bucket with object retention enabled by using the enableObjectRetention bucket create boolean option at bucket create time
  • Get the object retention enabled status of a bucket
  • Create an object with retention enabled (on an retention enabled bucket) by populating the retention object at object create time (retention object has the fields mode which can be Unlocked or Locked, and retainUntilTime which is a timestamp)
  • Update retention for an existing object with a patch operation, by passing the overrideUnlockedRetention boolean patch option
  • Get the retention policy of an object
  • Remove retention for an existing object the same way as above

Details in go/gcs-object-retention-client-request

You can use the java implementation as a reference.

The kokoro test project should be allowlisted shortly, let me know if you need access to an allowlisted project for your own testing.

We're aiming to get this in by the November code freeze, let me know if you need any help.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
api: storage Issues related to the Cloud Storage API.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants