wenjin272 opened a new issue, #1248: URL: https://github.com/apache/flink-agents/issues/1248
Parent: #1232 ### Problem and scope The Chat Models page does not consistently expose all resource declaration entry points, and built-in provider guidance needs clearer capability boundaries, naming, and migration scope. #### Scope - [ ] Introduce connection/setup concepts before annotation, programmatic Agent/environment, and YAML declaration entry points. Link to the YAML reference for configuration details. - [ ] Keep provider-specific conversion, supported block/source/media types, and model restrictions in Built-in Chat Model Providers. Link to Chat with Models for the framework message/content model instead of duplicating it. - [ ] Verify provider capability descriptions against 0.4, including the distinction between OpenAI Chat Completions and Responses, and keep them consistent with the capability warning in Chat with Models. - [ ] Use `DashScope (Alibaba Cloud Model Studio)` consistently across chat, embedding, YAML, and FAQ, matching the delivered public API and migration policy. - [ ] Scope Azure AI Inference migration instructions to affected old-integration users upgrading from 0.2.x/0.3.x to 0.4.x, distinguishing Azure OpenAI and fresh installations. #### Coordination and acceptance Use the merged Calling LLMs hierarchy and #1229's Resource model. Coordinate aliases with #1231 and the message/provider boundary with the Chat with Models child of #1232. Related API work: #1196 (DashScope naming). Verify representative declaration snippets, provider capability statements, migration applicability, and cross-links against the delivered implementation. #### Review coverage DOC-011, DOC-042, DOC-047. Provider-side changes supporting DOC-044, DOC-045, and DOC-046 are coordinated with the Chat with Models issue, which owns those findings. The actionable scope is described above. -- 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]
