Aias00 opened a new issue, #1094: URL: https://github.com/apache/rocketmq-dashboard/issues/1094
## Problem The VIP Channel and TLS switches save immediately on change, but each setting also exposes an Update button that invokes the same save operation again with the current value. A single operator change can therefore generate duplicate control-plane writes and duplicate audit records. ## Scope Track 1 / Cluster operations. ## Proposed fix Keep the existing switch-to-save interaction and remove the redundant Update controls. Add UI tests proving one switch interaction makes one API request. ## Evidence `web/src/pages/studio/Ops.tsx`: `Switch.onChange` calls `handleUpdateIsVIPChannel` / `handleUpdateUseTLS`, while the adjacent Update button invokes the same handlers with the current state. -- 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]
