-
Notifications
You must be signed in to change notification settings - Fork 374
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 #12994
Comments
This is not going to happen by the 2023-11 C++ release (due in the first few business days of the month). I also don't see this feature in the protos: Though I guess that could change in the next few days. We cannot add this to our CI until the protos are published. |
Punting for now. |
@scotthart @coryan : Can it be prioritized? Support for this API in Cpp library is important for us. |
@sourabh912 I am sorry you are blocked because this API was missing. After #14351 gets merged (probably within the next few days) all the functionality should be available 1 in the I will keep this bug open (and probably unassigned) until the gRPC-based implementation is unblocked. Footnotes |
@coryan : Thank you for the update ! |
Please implement the object retention feature. The following operations must be supported:
enableObjectRetention
bucket create boolean option at bucket create timeretention
object at object create time (retention object has the fieldsmode
which can be Unlocked or Locked, andretainUntilTime
which is a timestamp)overrideUnlockedRetention
boolean patch optionSupport for gRPC is blocked as the protos are not published.
BucketObjectRetention
EnableObjectRetention
for gRPC pluginObjectRetention
OverrideUnlockedRetention
for gRPC pluginDetails 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.
The text was updated successfully, but these errors were encountered: