RockteMQ-AI commented on issue #1740: URL: https://github.com/apache/rocketmq-dashboard/issues/1740#issuecomment-5252973161
## Issue Evaluation Category: `type/bug` | Status: **Confirmed** The issue is valid. `ProxyController.reloadProxyConfig` ignores the `clusterId` parameter and delegates solely by address to a global `ProxyAddressService`, making the cluster selector misleading. **Root Cause:** Backend validates but does not use `clusterId` for routing; the global proxy address service returns the same list regardless of selected cluster. **Impact:** Operational risk — reloading a proxy from the wrong cluster could cause unintended configuration changes. **Severity:** High The proposed approach (remove misleading cluster context until proper instance-scoped provider exists) is pragmatic. A fix PR can be generated. Reply `/approve` to proceed. --- *Automated evaluation by RockteMQ-AI* -- 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]
