oscerd opened a new pull request, #24879: URL: https://github.com/apache/camel/pull/24879
### Motivation [CAMEL-23244](https://issues.apache.org/jira/browse/CAMEL-23244): the ten component-specific `CredentialType` enums have been deprecated since 4.19.0 in favor of the shared `org.apache.camel.component.azure.common.CredentialType` (which is a superset of all of them, with a per-component support matrix in its javadoc). This completes the migration by removing them. ### Changes - Removed the deprecated `CredentialType` enums from cosmosdb, eventgrid, eventhubs, files, functions, key-vault, servicebus, storage-blob, storage-datalake, storage-queue. - Rewired all references (configurations, client factories, components, endpoints, tests — including static imports) to the shared enum; regenerated configurers, module JSON, catalog and endpoint/component DSL factories. - Upgrade-guide entry in `camel-4x-upgrade-guide-4_22.adoc` (breaking for Java/Endpoint-DSL imports; endpoint URIs unaffected — option values keep the same names, and each component's `enums=` restriction still lists only its supported values). - Side effect worth noting: `SERVICE_CLIENT_INSTANCE` (datalake) and `TOKEN_CREDENTIAL` (functions) were already advertised in those components' option metadata but missing from their local enums, so binding them could never resolve — with the shared enum they now bind as advertised. Main-only (4.22.0): removal is intentionally not backported. ### Testing - `mvn clean install` for camel-azure-common + all 10 migrated modules: 11/11 BUILD SUCCESS, no test failures. - Full reactor `mvn clean install -DskipTests` from root: success, all regenerated files committed. _Claude Code on behalf of Andrea Cosentino (@oscerd)._ 🤖 Generated with [Claude Code](https://claude.com/claude-code) -- 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]
