Camel-AWS: Extract common logic for clients in a separated module - A…

[oscerd]

…WS S3

Description

This a proposal, to move some part of the common logic for AWS clients in a separated module, this should help us avoiding a lot of duplicated code and make the addition of more credentials provider easier. Please provide feedback. The implementation is for AWS S3. I'm planning to add the others if this work out for everyone.

Target

• I checked that the commit is targeting the correct branch (Camel 4 uses the main branch)

Tracking

• If this is a large change, bug fix, or code improvement, I checked there is a JIRA issue filed for the change (usually before you start working on it).

Apache Camel coding standards and style

• I checked that each commit in the pull request has a meaningful subject line and body.

• I have run mvn clean install -DskipTests locally from root folder and I have committed all auto-generated changes.

[github-actions]

🌟 Thank you for your contribution to the Apache Camel project! 🌟

🤖 CI automation will test this PR automatically.

🐫 Apache Camel Committers, please review the following items:

• First-time contributors require MANUAL approval for the GitHub Actions to run

• You can use the command /component-test (camel-)component-name1 (camel-)component-name2.. to request a test from the test bot.

• You can label PRs using build-all, build-dependents, skip-tests and test-dependents to fine-tune the checks executed by this PR.

• Build and test logs are available in the Summary page. Only Apache Camel committers have access to the summary.

• ⚠️ Be careful when sharing logs. Review their contents before sharing them publicly.

[oscerd]

Marked as draft

[oscerd]

/component-tests aws

Result ✅ The tests passed successfully

[github-actions]

🤖 The Apache Camel test robot will run the tests for you 👍

[davsclaus]

you may need to add this new common module as something to skip in the tooling/maven - I think we do this for camel-debezium-common

[oscerd]

It should be ok now.