Aias00 opened a new issue, #1740: URL: https://github.com/apache/rocketmq-dashboard/issues/1740
## Problem The Proxy management page persists and submits `clusterId`, but the backend only validates the field and then ignores it. `ProxyController.reloadProxyConfig` delegates solely by address to a process-global `ProxyAddressService`; `GET /api/proxies` similarly requires a cluster id but returns the same global address list. This makes the cluster selector misleading and can reload a Proxy that does not belong to the operator-selected cluster. ## Scope - Remove the misleading editable cluster context from the legacy global Proxy page until an instance/cluster-scoped Proxy provider exists. - Do not send a `clusterId` that the reload endpoint cannot honor. - Keep proxy address validation and structured failure behavior unchanged. ## Acceptance criteria - The page does not imply that a manually entered cluster id scopes Proxy discovery or reload. - The reload API contract no longer accepts an unused `clusterId`. - Regression tests cover the reduced API contract and UI call shape. Track: Control Plane / Proxy management (ARCH-01). -- 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]
