[
https://issues.apache.org/jira/browse/CAMEL-23468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrea Cosentino resolved CAMEL-23468.
--------------------------------------
Resolution: Fixed
> Camel-AWS-Bedrock: Add support for InvokeFlow operation in Bedrock Agent
> Runtime
> --------------------------------------------------------------------------------
>
> Key: CAMEL-23468
> URL: https://issues.apache.org/jira/browse/CAMEL-23468
> Project: Camel
> Issue Type: New Feature
> Reporter: Andrea Cosentino
> Assignee: Andrea Cosentino
> Priority: Major
>
> Bedrock Flows are a managed orchestration feature for chaining prompts,
> knowledge bases, and Lambda functions. The {{aws-bedrock-agent-runtime}} SDK
> exposes {{invokeFlow(InvokeFlowRequest)}}, but no Camel operation surfaces it.
> {{invokeFlow}} returns an event-stream response
> ({{InvokeFlowResponseHandler}}) similar to {{InvokeAgent}}, so the same async
> streaming infrastructure (proposed alongside CAMEL-XXX for InvokeAgent) will
> apply.
> *Suggested scope:*
> * Add {{invokeFlow}} to {{BedrockAgentRuntimeOperations}}.
> * Add {{flowIdentifier}} and {{flowAliasIdentifier}} to
> {{BedrockAgentRuntimeConfiguration}} (with header overrides).
> * Add input-content support: text, document, and chained flow inputs.
> * Implement event-stream handling for {{FlowResponseStream}} events
> ({{flowOutputEvent}}, {{flowCompletionEvent}}, {{flowTraceEvent}}).
> * Surface flow output and trace events via headers/body.
> * Add tests and update {{aws-bedrock-agent-runtime-component.adoc}}.
> ----
> _Filed by Claude Code on behalf of Andrea Cosentino._
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
