Mailing-List: contact issues-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@camel.apache.org
Date: Sun, 20 Nov 2011 12:13:51 +0000 (UTC)
From: =?utf-8?Q?Christian_M=C3=BCller_=28Commented=29_=28JIRA=29?=
 <jira@apache.org>
To: issues@camel.apache.org
Message-ID: 
 <1167472756.48797.1321791231596.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (CAMEL-4435) Allow specifiying ACL on S3
 producer
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


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

Christian M=C3=BCller 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 com=
ponent. You can do this of course by hand in the AWS console, but if you cr=
eate new buckets/topics on the fly with the Camel AWS components, you may n=
eed the possibility to define the policy in the same time.

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

Best,
Christian
               =20
> 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=C3=BCller
>            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=3Dprivate
>   * A reference to an ACL bean (com.amazonaws.services.s3.model.CannedAcc=
essControlList): acl=3D#myAcl
> 2. Add CamelAwsS3ACL header, which can contain a string ("private", "publ=
ic-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 goin=
g about it will be accepted before getting too far.
> Some questions:
>   * Is "acl" a good URL parameter? Should it be "access"? Should ACL refe=
rences be separate ("aclRef")?
>   * Should we accept a string for the canned ACL when it's a header, or j=
ust expect a CannedAccessControlList object?

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