Aias00 opened a new issue, #788: URL: https://github.com/apache/rocketmq-dashboard/issues/788
### Problem The RocketMQ Studio Ops page exposes write operations for NameServer selection, adding NameServer addresses, VIP channel, and TLS settings. The backend currently stores these values in `OpsService` process-local fields and returns success, but the settings are not wired into the RocketMQ admin/client configuration path. Users can therefore receive a successful response even though the selected NameServer/VIP/TLS settings do not affect real MQAdmin calls. ### Evidence - `server/src/main/java/org/apache/rocketmq/studio/ops/OpsService.java` keeps `namesrvAddrs`, `currentNamesrv`, `useVIPChannel`, and `useTLS` as service fields. - `web/src/pages/studio/Ops.tsx` shows success after these endpoints resolve. ### Expected Behavior Until the Ops settings are connected to the real cluster/AdminClient configuration flow, write endpoints should not report a successful applied change. They should return a clear unavailable/unsupported error so the UI does not imply that runtime MQAdmin settings were changed. ### Scope This is in the RocketMQ Studio control-plane scope: BASE-01 Ops compatibility and ARCH-01 AdminClient configuration behavior. -- 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]
