youngkermit8-coder opened a new issue, #2033:
URL: https://github.com/apache/rocketmq-dashboard/issues/2033

   ## Bug report\n\nStudio exposes Azure OpenAI as an LLM provider, and the 
backend contract contains deploymentName and piVersion. However, the LLM 
settings page neither renders those fields nor includes them in save/test 
payloads. The backend correctly rejects Azure configurations without a 
deployment name, so Azure cannot be configured through the UI.\n\nThere is a 
second part of the same end-to-end contract gap: provider-specific fields are 
kept in LlmConfigService.overrides only. saveConfig persists the common fields 
into GeneralSettingsVO, but not deploymentName, piVersion, or wsRegion. A 
configuration supplied directly through the API therefore loses those fields 
after a process restart.\n\n## Reproduction\n\n1. Open Studio LLM settings.\n2. 
Select Azure OpenAI.\n3. Observe that no deployment-name or API-version control 
is available.\n4. Test or save the form; the request omits deploymentName, and 
the backend returns llm.config.missing_deployment.\n5. Alternatively, POST a 
 complete Azure config directly to /api/llm/config, restart Studio, then GET 
/api/llm/config; provider-specific values have reverted to defaults/empty 
values.\n\n## Expected behavior\n\n- The settings page should collect and 
submit the provider-specific Azure fields required by the backend contract.\n- 
Saved provider-specific fields should be restored from persistent general 
settings after restart.\n- Changing providers should not leak hidden fields 
into unrelated provider payloads.\n\n## Proposed scope\n\n- Persist 
deploymentName, piVersion, and wsRegion alongside the existing LLM settings 
JSON.\n- Render Azure deployment/API-version fields and the Bedrock region 
field only for the matching provider.\n- Include only the active provider's 
fields in save/test payloads.\n- Add backend persistence and frontend payload 
regression tests.


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