You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Andrea Cosentino (Jira)" <ji...@apache.org> on 2023/01/24 17:06:00 UTC

[jira] [Commented] (CAMEL-18976) camel file storage copyObject support for multiple authenticated client

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

Andrea Cosentino commented on CAMEL-18976:
------------------------------------------

I don't think it makes sense a second client or a second set of credentials in parameters or headers or wherever. This will only pollute the endpoint options. You have the ability to do the operation through two different operations. I don't think it worths to introduce more complexities just for one single operation corner case.

> camel file storage copyObject support for multiple authenticated client
> -----------------------------------------------------------------------
>
>                 Key: CAMEL-18976
>                 URL: https://issues.apache.org/jira/browse/CAMEL-18976
>             Project: Camel
>          Issue Type: New Feature
>          Components: camel-aws2, camel-azure, camel-google-storage, camel-minio
>    Affects Versions: 3.20.1, 4.0, Future
>            Reporter: Hitesh C
>            Priority: Major
>
> Presently Copy Object operation works well when the same set of credentials have access to both source and destination buckets.
> So when i am performing copy object from an S3 bucket to another S3 bucket with different set of credentials, I have to do a getObject and PutObject operation separately.
>  
> An functionality accepting a pair of client (s3, minio, cloud-storage), etc and the respective storage bucket as source and destination could help in simplifying the process even further.
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)