[GitHub] [camel-quarkus] JiriOndrusek commented on pull request #2911: camel-quarkus-minio: quarkus.minio.url is mandatory and still has to be valid

[GitBox <gi...@apache.org>]

JiriOndrusek commented on pull request #2911:
URL: https://github.com/apache/camel-quarkus/pull/2911#issuecomment-882415507


   @oscerd I'm not sure if I understand. My fix is only setting property ''quarkus.minio.allow-empty" to true, which has no effect on cases, where minio client is initialized from quarkus properties:
   
   - if all other quarkus minio parameters are null, no minio client will be created (without it, it would throw a validation exception)
   
   From this perspective,  everything that worked before, would work after this fix. 
   Only difference is in the case, where all quarkus parameters are null (url, server_secret and server_access) - case of kamelet - it wouldn't throw a validation exception, but return `null` as a client. Autowiring capability of the component then would use minio client from the context.


-- 
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: commits-unsubscribe@camel.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org