Aias00 opened a new issue, #809:
URL: https://github.com/apache/rocketmq-dashboard/issues/809

   ### Before Creating the Bug Report
   
   - [x] I found a bug, not just asking a question, which should be created in 
GitHub Issues.
   - [x] I have searched the existing issues and believe this is not a 
duplicate.
   - [x] I have confirmed that this bug belongs to the current repository.
   
   ### Describe the Bug
   
   Studio LLM Settings currently exposes Azure OpenAI and AWS Bedrock as 
selectable providers, but the active OpenAI-compatible gateway only supports 
openai, deepseek, tongyi, and ollama.
   
   Code evidence:
   
   - web/src/pages/studio/LlmSettings.tsx includes provider cards for azure and 
bedrock.
   - 
server/src/main/java/org/apache/rocketmq/studio/ops/ai/OpenAiCompatibleLlmClient.java
 defines SUPPORTED_PROVIDERS as openai, deepseek, tongyi, and ollama.
   - 
server/src/main/java/org/apache/rocketmq/studio/ops/ai/OpenAiCompatibleLlmGateway.java
 returns llm.config.unsupported_provider for unsupported provider values.
   
   This creates a misleading user path: users can select Azure or Bedrock in 
the settings UI, but chat/model calls through the current gateway cannot 
succeed with those providers.
   
   ### Expected Behavior
   
   The LLM provider settings UI should not allow users to select providers that 
are not supported by the currently wired gateway. Unsupported providers should 
either be hidden/disabled until implemented, or the backend should implement 
real provider-specific support.
   
   ### Scope
   
   RocketMQ Studio Track 3 / AI Native LLM provider configuration.
   
   ### Proposed Fix
   
   For the current OpenAI-compatible gateway phase, keep only supported 
providers selectable in the Studio LLM Settings page and add a frontend 
regression test that Azure/Bedrock are not exposed as selectable provider cards.
   


-- 
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