[jira] [Closed] (CAMEL-4435) Allow specifiying a policy on S3 and SNS component

["Christian Müller (Closed JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CAMEL-4435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Christian Müller closed CAMEL-4435.
-----------------------------------

    Resolution: Fixed
    
> 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üller
>            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=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