You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@libcloud.apache.org by "Michael Joseph Rosenthal (JIRA)" <ji...@apache.org> on 2019/02/02 22:16:00 UTC

[jira] [Commented] (LIBCLOUD-1036) Object versioning for S3 and GCS

    [ https://issues.apache.org/jira/browse/LIBCLOUD-1036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16759220#comment-16759220 ] 

Michael Joseph Rosenthal commented on LIBCLOUD-1036:
----------------------------------------------------

more specifically, I think their respective `Object` implementations should have a `version` attribute. In GCS even unversioned objects have version numbers (generations). I believe this is true of s3 objects as well, so managing whether a bucket has versioning enabled shouldn't be necessary for basic functionality.

> Object versioning for S3 and GCS
> --------------------------------
>
>                 Key: LIBCLOUD-1036
>                 URL: https://issues.apache.org/jira/browse/LIBCLOUD-1036
>             Project: Libcloud
>          Issue Type: New Feature
>          Components: Storage
>    Affects Versions: 2.4.0
>            Reporter: Michael Joseph Rosenthal
>            Priority: Major
>              Labels: gcs, s3
>
> There is object versioning for both [s3|https://docs.aws.amazon.com/AmazonS3/latest/dev/ObjectVersioning.html] and [gcs|https://cloud.google.com/storage/docs/object-versioning], which don't appear to be usable via the libcloud drivers.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)