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

ASF GitHub Bot commented on CAMEL-12437:
----------------------------------------

GitHub user alaptseu opened a pull request:

    https://github.com/apache/camel/pull/2290

    CAMEL-12437

    I created a jira ticket for this improvement 
https://issues.apache.org/jira/browse/CAMEL-12437
    
    Basically with current implementation (as per camel version 2.20.2) there 
is no way to provide dynamic s3 bucket name when you upload files (it's 
possible though if copying files from source bucket to destination bucket).
    I think we could use S3Constants.BUCKET_NAME provided at exchange header 
and if it is set use that value as bucket name where file will be uploaded, if 
S3Constants.BUCKET_NAME is not provided then  use bucket which is preconfigured 
at configuration.
    


You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/alaptseu/camel master

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/camel/pull/2290.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #2290
    
----
commit 97304063ec80f448ebd7040720f27bc2b8f59d5c
Author: Laptseu <alexlaptseu1@...>
Date:   2018-04-12T12:28:46Z

    CAMEL-12437

----


> Ability to define dynamic bucket name for s3 router using standard 
> S3Constants.BUCKET_NAME supplied in header
> -------------------------------------------------------------------------------------------------------------
>
>                 Key: CAMEL-12437
>                 URL: https://issues.apache.org/jira/browse/CAMEL-12437
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-aws
>    Affects Versions: 2.20.2
>            Reporter: Aliaksandr Laptseu
>            Priority: Major
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to