[
https://issues.apache.org/jira/browse/CAMEL-23232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-23232:
--------------------------------
Component/s: camel-azure
> Camel-Azure components: Standardize CredentialType enums across all Azure
> components
> ------------------------------------------------------------------------------------
>
> Key: CAMEL-23232
> URL: https://issues.apache.org/jira/browse/CAMEL-23232
> Project: Camel
> Issue Type: Improvement
> Components: camel-azure
> Reporter: Andrea Cosentino
> Assignee: Andrea Cosentino
> Priority: Major
> Fix For: 4.19.0
>
>
> Each of the 10 Azure components (storage-blob, storage-queue,
> storage-datalake, eventhubs, servicebus, cosmosdb, key-vault, files,
> eventgrid, functions) defined its
> own CredentialType enum with inconsistent values and naming. For example,
> some components used SHARED_ACCOUNT_KEY while others used
> SHARED_KEY_CREDENTIAL, and
> connection-string-based auth was only available in messaging components. This
> inconsistency made it confusing for users switching between Azure components
> and
> prevented standardized tooling.
> This change introduces a new camel-azure-common module containing a single
> shared CredentialType enum with all 10 credential types and a component
> support matrix in
> the javadoc. The 10 component-specific enums are deprecated with
> @Deprecated(since="4.19.0"). URI-based configuration requires no changes;
> Java API users only need to update their import statement.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
