davsclaus opened a new pull request, #24980:
URL: https://github.com/apache/camel/pull/24980

   ## Summary
   
   _Claude Code on behalf of davsclaus_
   
   Adds a new `openSearchClient` component option to `camel-opensearch`, 
allowing users to provide a pre-configured `OpenSearchClient` instance instead 
of having the component build one internally from host addresses. This is 
useful when a custom transport is needed, for example when connecting to AWS 
OpenSearch Service with IAM-based authentication via `AwsSdk2Transport`.
   
   **Key design points:**
   - Component-level option with `@Metadata(label = "advanced", autowired = 
true)` — follows the same pattern as the existing `client` (RestClient) option
   - When both `RestClient` and `OpenSearchClient` are available, the 
`OpenSearchClient` takes precedence
   - All lifecycle methods (`doStart`, `process`, `cleanup`, `doStop`) are 
properly guarded — the component never closes or manages resources it doesn't 
own (the user's custom client/transport)
   
   **Changes:**
   - `OpensearchComponent` — new `openSearchClient` field with autowiring
   - `OpensearchEndpoint` — stores and exposes the client
   - `OpensearchProducer` — branches on custom client in `process()`, guards 
lifecycle in `doStart`/`doStop`/`cleanup`
   - Documentation — new "Custom OpenSearchClient Example" section
   - Generated files — catalog, component configurer, component DSL all 
regenerated
   
   **Supersedes:** #24320 (contributor did not complete review feedback after 
multiple rounds)
   
   ## Test plan
   
   - [x] Unit tests pass (`mvn test` in `components/camel-opensearch`)
   - [ ] CI build passes
   - [ ] Integration tests with OpenSearch container validate default 
(RestClient) path is unbroken
   
   🤖 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]

Reply via email to