Open jamesnetherton opened 1 year ago
I'd like to confess that I am guilty of copying the current mess to https://github.com/quarkiverse/quarkus-azure-services . Not sure how much sense it makes to tidy up on our side given that we'll probably start consuming quarkus-azure-services sooner or later?
Currently we have:
camel-quarkus-support-azure-core
camel-quarkus-support-azure-core-http-client-vertx
I was considering creating a new 'support' extension for
azure-identity
. But, given the logic in these extensions applies to all of the Camel Azure component extensions, it probably makes more sense to combine it all under a singlecamel-quarkus-support-azure
module.