libcloud-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tomaz Muraus (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (LIBCLOUD-497) Cannot set ACLs on S3 objects
Date Thu, 16 Jan 2014 00:36:22 GMT

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

Tomaz Muraus commented on LIBCLOUD-497:
---------------------------------------

Yeah, adding support for ACL management to the Amazon S3 driver would be nice.

We could implement ACL management methods which work on the existing objects and containers
via the extension methods. 

And for new containers and object we could add "ex_acl" or a similar argument to the create_container,
upload_object and other methods. 

Reference: http://docs.aws.amazon.com/AmazonS3/latest/dev/ACLUsingRESTAPI.html

> Cannot set ACLs on S3 objects
> -----------------------------
>
>                 Key: LIBCLOUD-497
>                 URL: https://issues.apache.org/jira/browse/LIBCLOUD-497
>             Project: Libcloud
>          Issue Type: Bug
>          Components: Storage
>    Affects Versions: 0.13.3
>            Reporter: Noah Kantrowitz
>
> Would be nice if you could set extra={'acl': 'public-read'} and get that passed as the
x-amz-acl header.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Mime
View raw message