[
https://issues.apache.org/jira/browse/JCLOUDS-660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14323738#comment-14323738
]
Andrew Gaul commented on JCLOUDS-660:
-------------------------------------
Surveying the major object stores, only Azure does not support publicly
readable and writable containers:
* Atmos:
https://community.emc.com/servlet/JiveServlet/previewBody/10508-102-1-41134/Atmos%20Programmer's%20Guide%201.4.1A.pdf
(page 29)
* Azure: https://msdn.microsoft.com/en-us/library/azure/dd179391.aspx
* GCS: https://cloud.google.com/storage/docs/access-control#permissions
* S3:
http://docs.aws.amazon.com/AmazonS3/latest/dev/acl-overview.html#permissions
* Swift https://www.swiftstack.com/docs/cookbooks/swift_usage/container_acl.html
> Improve portable container ACL support
> --------------------------------------
>
> Key: JCLOUDS-660
> URL: https://issues.apache.org/jira/browse/JCLOUDS-660
> Project: jclouds
> Issue Type: New Feature
> Components: jclouds-blobstore
> Affects Versions: 1.8.0
> Reporter: Andrew Gaul
> Assignee: Andrew Gaul
>
> Presently jclouds only allows creation of private (default) or public-read
> containers. It should also support setting this policy after creation and
> possibly some other variants, such as public-read-write. Amazon S3 reference:
> http://docs.aws.amazon.com/AmazonS3/latest/API/RESTBucketPUT.html
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
