wenjin272 opened a new issue, #1334: URL: https://github.com/apache/flink-agents/issues/1334
### Search before asking - [x] I searched the existing issues; #1062 tracks this work at the umbrella level, but there is no dedicated YAML implementation issue. ### Description Parent: #1062. Blocked by: #1333 (Python model routing support). Add model router resource declarations to the YAML API after Python routing support is available, so Java and Python YAML loaders both support model routing. `ModelRouter` is already a Resource backed by a `ResourceDescriptor`, and its strategy configuration is serializable. Reuse the generic descriptor schema and the existing routing implementation. ### Acceptance criteria - [ ] Add router resource lists to both the agent-level and top-level shared-resource YAML specs, reusing `DescriptorSpec`. - [ ] Wire the Java and Python YAML loaders to construct descriptors and register them as `MODEL_ROUTER` resources. - [ ] Support the existing descriptor arguments for candidates, descriptions, strategy configuration, default model, and fallback. - [ ] Reuse existing plan-time and resource validation, with consistent behavior between YAML and programmatic declarations. - [ ] Add loading and execution tests for both loaders, covering agent-local and shared routers, model references, and invalid configurations. - [ ] Document the configuration and provide working YAML examples for both Java and Python. ### Dependency and scope Complete Python model routing support in #1333 before delivering full YAML support. This issue covers resource declaration and loader wiring; routing execution semantics belong to the existing Java implementation and the Python parity work. The Java `@ModelRouterSetup` annotation in #1133 is a separate declaration entry point and is not a prerequisite for YAML registration. ### Are you willing to submit a PR? - [ ] I'm willing to submit a PR! -- 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]
