DanielLeens commented on issue #11547: URL: https://github.com/apache/seatunnel/issues/11547#issuecomment-5081478076
Thanks for writing this up so concretely and for already opening PR #11548. This reads as a real feature enhancement rather than a bug. I checked the current CLI provider split on July 26, 2026, and the gap you described is real: the existing `bedrock` path is built around the standard Bedrock runtime APIs, while the existing `openai` path assumes the Chat Completions API shape. That means a Responses-API-only Bedrock endpoint is not covered by either provider today. Since PR #11548 is already open and the issue is assigned to you, I think the right next step is to keep the first scope intentionally narrow: 1. add one dedicated provider path for the mantle Responses API 2. handle bearer-token acquisition and refresh cleanly from AWS credentials 3. prove request/response mapping for the CLI's message and tool-call flow 4. keep unsupported parameters such as `temperature` explicitly out of the provider contract The main review points will be provider-boundary clarity, auth refresh behavior, streaming/function-call compatibility, and making sure this does not regress the existing `openai` or standard `bedrock` providers. Keeping the first PR focused on that path is the best way to get it reviewed efficiently. -- 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]
