scrocquesel opened a new issue, #6705: URL: https://github.com/apache/camel-quarkus/issues/6705
### Describe the feature here After reading the [documentation](https://camel.apache.org/camel-quarkus/3.15.x/reference/extensions/aws2-s3.html#extensions-aws2-s3-additional-camel-quarkus-configuration), I see an opportunity to enhance the user experience. First, an `S3Presigner` bean should have been explicitly declared. However, due to a recently discovered bug, the Quarkus Amazon extension has historically created an `S3Presigner` bean even without an injection point. This means users are not required to add a dummy `S3Presigner` bean. This behavior will be removed in the next major version. I introduced a configuration flag that defaults to the legacy behavior to maintain backward compatibility in the next minor version. Second, the Quarkus Amazon extension is now structured to allow other extensions to "request" a client bean without an injection point. Consequently, this approach should eliminate the need for users to add dummy beans and manually configure the client type. By using [conditional dependencies](https://quarkus.io/guides/conditional-extension-dependencies), we can detect the presence of `quarkus-amazon-s3` and activate an extension that requires `S3Client` and `S3Presigner` beans. It would also be possible to embed an `application.properties` file for configuring the client type property. I don’t think Camel Quarkus users are likely to use an HTTP client implementation other than apache. Third, starting version 2.19, Quarkus amazon will support [named clients](https://docs.quarkiverse.io/quarkus-amazon-services/dev/common-features.html). This was asked by our users to be able to connect to multiple queues with different credentials. Last, I noticed that we’re not fully aligned on the AWS services we support, and even where we do overlap, this isn’t reflected in your documentation (cloudwatch, eventbridge, iam, kms, kinesis, lambda, secretmanager). I can work to close the gap of the missing services. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
