You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Luca Burgazzoli (Jira)" <ji...@apache.org> on 2020/02/20 14:07:00 UTC

[jira] [Updated] (CAMEL-14598) Component Properties aliases

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

Luca Burgazzoli updated CAMEL-14598:
------------------------------------
    Summary: Component Properties aliases  (was: Properties alias)

> Component Properties aliases
> ----------------------------
>
>                 Key: CAMEL-14598
>                 URL: https://issues.apache.org/jira/browse/CAMEL-14598
>             Project: Camel
>          Issue Type: New Feature
>          Components: camel-core
>            Reporter: Luca Burgazzoli
>            Priority: Minor
>             Fix For: 3.2.0
>
>
> For some components such as those related to AWS service, each component has its own authentication configuration option so in case you want to use multiple services in the same integration, then you'll end up having to repeat them, like:
> {code}
> # S3
> camel.component.aws-s3.access-key={{env:AWS_ACCESS_KEY}}
> camel.component.aws-s3.secret-key={{env:AWS_SECRET_KEY}}
> camel.component.aws-s3.region={{env:AWS_REGION}}
> # SNS
> camel.component.aws-sns.access-key={{env:AWS_ACCESS_KEY}}
> camel.component.aws-sns.secret-key={{env:AWS_SECRET_KEY}}
> camel.component.aws-sns.region={{env:AWS_REGION}}
> {code}
> So I think it would be nice to have an option to define component properties aliases so we can rewrite the configuration above like:
> {code}
> aws.access-key={{env:AWS_ACCESS_KEY}}
> aws.secret-key={{env:AWS_SECRET_KEY}}
> {code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)