Mailing-List: contact issues-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@camel.apache.org
Date: Sun, 20 Nov 2011 14:01:52 +0000 (UTC)
From: =?utf-8?Q?Christian_M=C3=BCller_=28Updated=29_=28JIRA=29?=
 <jira@apache.org>
To: issues@camel.apache.org
Message-ID: 
 <145368157.49022.1321797712560.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Updated] (CAMEL-4435) Allow specifiying a policy on S3 and
 SNS component
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.atlassia=
n.jira.plugin.system.issuetabpanels:all-tabpanel ]

Christian M=C3=BCller updated CAMEL-4435:
------------------------------------

    Affects Version/s: 2.8.2
        Fix Version/s: 2.9.0
                       2.8.4
           Issue Type: Improvement  (was: New Feature)
              Summary: Allow specifiying a policy on S3 and SNS component  =
(was: Allow specifiying ACL on S3 producer)
   =20
> Allow specifiying a policy on S3 and SNS component
> --------------------------------------------------
>
>                 Key: CAMEL-4435
>                 URL: https://issues.apache.org/jira/browse/CAMEL-4435
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-aws
>    Affects Versions: 2.8.2
>            Reporter: Brendan Long
>            Assignee: Christian M=C3=BCller
>            Priority: Minor
>             Fix For: 2.8.4, 2.9.0
>
>
> 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