[
https://issues.apache.org/jira/browse/CAMEL-11491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16071563#comment-16071563
]
ASF GitHub Bot commented on CAMEL-11491:
----------------------------------------
GitHub user tdemande opened a pull request:
https://github.com/apache/camel/pull/1802
CAMEL-11491: Remove mandatory nature of Amazon Clients when accessKey…
… and secretKey are provided
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/tdemande/camel CAMEL-11491
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/camel/pull/1802.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 #1802
----
commit 73f1c78a3f442711e32001bd538fb8b6d12267c8
Author: Thomas Demande <[email protected]>
Date: 2017-07-02T09:08:07Z
CAMEL-11491: Remove mandatory nature of Amazon Clients when accessKey and
secretKey are provided
----
> Apply non-mandatory nature of amazon client to AWS components being able to
> specify accessKey and secretKey
> -----------------------------------------------------------------------------------------------------------
>
> Key: CAMEL-11491
> URL: https://issues.apache.org/jira/browse/CAMEL-11491
> Project: Camel
> Issue Type: Sub-task
> Components: camel-aws
> Reporter: Thomas Demande
> Fix For: 2.19.2, 2.20.0
>
>
> Following work made on CAMEL-11489, the idea here is to re-apply the same
> non-mandatory nature of Amazon Client for the other components (S3 already
> being fixed) that were touched by CAMEL-9210.
> * DDB
> * EC2
> * SDB
> * SES
> * SNS
> * SQS
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
