Aias00 opened a new issue, #775: URL: https://github.com/apache/rocketmq-dashboard/issues/775
### Problem On the rocketmq-studio branch, `ClusterRepositoryImpl` calls `initStubData()` from its default constructor. This means the backend always exposes demo clusters such as `rmq-cluster-prod` and `rmq-cluster-staging` even when the UI is running against the real API path. That behavior can mislead users in Studio cluster and dashboard views because demo infrastructure looks like real discovered RocketMQ clusters. ### Evidence - `server/src/main/java/org/apache/rocketmq/studio/cluster/broker/ClusterRepositoryImpl.java` calls `initStubData()` unconditionally in the constructor. - The seeded records include fixed endpoints like `10.0.0.1:9876`, proxy addresses, broker TPS, topic counts, and group counts. ### Expected behavior Demo seed data should be controlled by an explicit configuration flag and should be disabled by default. Tests or local demo setups can opt in, but production/runtime API responses should not contain demo clusters unless explicitly requested. ### Scope This is in the RocketMQ Studio scope for ARCH-01 / multi-cluster management correctness. The proposed fix is a small repository hardening change, not a full persistent cluster registry implementation. -- 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]
