camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christian Müller (Commented) (JIRA) <j...@apache.org>
Subject [jira] [Commented] (CAMEL-4435) Allow specifiying ACL on S3 producer
Date Sun, 20 Nov 2011 12:13:51 GMT

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

Christian Müller commented on CAMEL-4435:
-----------------------------------------

Hello Brendan!

For the SQS component, we already provide the option to set a policy for a queue. With the
last commit, I added this option also to the S3 and SNS component. You can do this of course
by hand in the AWS console, but if you create new buckets/topics on the fly with the Camel
AWS components, you may need the possibility to define the policy in the same time.

Feel free to test this new feature whether it works for you...

Best,
Christian
                
> Allow specifiying ACL on S3 producer
> ------------------------------------
>
>                 Key: CAMEL-4435
>                 URL: https://issues.apache.org/jira/browse/CAMEL-4435
>             Project: Camel
>          Issue Type: New Feature
>          Components: camel-aws
>            Reporter: Brendan Long
>            Assignee: Christian Müller
>            Priority: Minor
>
> With the S3 component, there's currently no way to specify ACLs on either the component
or message level.
> I'm proposing:
> 1. Add a URL parameter, "acl", which can be either:
>   * A canned ACL (private, public-read, public-read-write, authenticated-read). Ex: acl=private
>   * A reference to an ACL bean (com.amazonaws.services.s3.model.CannedAccessControlList):
acl=#myAcl
> 2. Add CamelAwsS3ACL header, which can contain a string ("private", "public-read", etc.),
a CannedAccessControlList object, or an AccessControlList object
> I'm working on a patch for this, but I want to make sure the way I'm going about it will
be accepted before getting too far.
> Some questions:
>   * Is "acl" a good URL parameter? Should it be "access"? Should ACL references be separate
("aclRef")?
>   * Should we accept a string for the canned ACL when it's a header, or just expect a
CannedAccessControlList object?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

Mime
View raw message