Aias00 opened a new issue, #987: URL: https://github.com/apache/rocketmq-dashboard/issues/987
## Problem ClusterService.listClusters prefers live discovery, but updateClusterConfig and node-operation methods only resolve clusters from ClusterRepository. The production repository is empty unless studio.cluster.seed-demo-data=true. A user can select a real discovered cluster and then receive 404 Cluster not found when updating its configuration. ## Expected Cluster operations resolve the selected live cluster identity and do not require demo or in-memory repository records. ## Acceptance criteria - A discovered cluster can complete a supported configuration update without a repository seed. - Unsupported node actions retain explicit 501 semantics. - Tests cover discovered-cluster update resolution and missing-cluster 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]
