Aias00 opened a new issue, #1476: URL: https://github.com/apache/rocketmq-dashboard/issues/1476
## Problem The NameServer configuration drift flow is cluster-scoped only. `GET /api/nameservers/config-diff` accepts `clusterId` but no `instanceId`; `NameServerConfigDiffService` consequently resolves the cluster through the default runtime context. The web page also lists clusters and queries drift results without an instance selection. In a multi-instance Studio deployment, the same cluster identifier can be resolved against the wrong managed RocketMQ endpoint, so the displayed drift result is not reliable. ## Scope - Add optional/required `instanceId` propagation from the drift page through the web API and controller/service. - Resolve the cluster and NameServer admin client using that selected instance endpoint. - Preserve existing validation and return an actionable error when the requested cluster is not available for the instance. - Add focused backend and frontend regression tests for instance propagation. ## Out of scope - NameServer lifecycle operations. - Changes to the drift comparison algorithm or safe-key catalog. ## Track Track 1 / ARCH-01 multi-instance runtime management. -- 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]
