youngkermit8-coder opened a new pull request, #2035:
URL: https://github.com/apache/rocketmq-dashboard/pull/2035

   ## What is the purpose of the change\n\nFixes #2033.\n\nAzure OpenAI is 
selectable in Studio, but the LLM settings page did not expose the deployment 
fields required by the backend. Provider-specific fields were also kept only in 
the in-memory override, so a direct API configuration lost them after 
restart.\n\n## Brief changelog\n\n- Persist deploymentName, piVersion, and 
wsRegion in the existing general-settings JSON.\n- Preserve those fields when 
the general settings form omits them.\n- Show Azure deployment/API-version 
controls and the Bedrock region control only for the matching provider.\n- 
Clear providers without a built-in endpoint instead of retaining the previous 
provider's API base.\n- Submit only the active provider's extra fields.\n- Add 
backend restart/preservation tests and an Azure form payload regression 
test.\n\n## User impact\n\nAzure users can now supply the deployment name 
required by backend validation through the UI. Provider-specific values survive 
a Studi
 o restart, and hidden fields do not leak into another provider's 
request.\n\n## Verification\n\n- mvn -B -ntp test: 1056 tests, 0 
failures/errors; Checkstyle 0 violations.\n- mvn -B -ntp 
-Dtest=LlmConfigServiceTest,SettingsServiceTest test: 58 tests passed.\n- 
   pm test -- --run src/pages/studio/__tests__/LlmSettingsPage.test.tsx: 4 
tests passed.\n- Targeted ESLint and Prettier checks passed for both changed 
frontend files.\n- 
   pm run build: production build succeeded.\n\nThe repository-wide frontend 
lint remains blocked by the pre-existing  eact-hooks/set-state-in-effect error 
in BrokerCluster.tsx:223; this PR does not touch that file.\n\n- [x] Issue 
filed before implementation.\n- [x] Single-purpose change with regression 
coverage.\n- [x] Signed-off-by commit included.


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