Aias00 opened a new issue, #790: URL: https://github.com/apache/rocketmq-dashboard/issues/790
### Problem `InMemoryInstanceRepository` seeds three demo instances during construction. That makes a fresh RocketMQ Studio backend show production/staging/dev instances even when the operator has not configured any real instances. This can mislead users into treating sample data as real control-plane state, and it is inconsistent with the control-plane goal that real resources should come from configured providers or explicit user actions. ### Evidence - `server/src/main/java/org/apache/rocketmq/studio/instance/InMemoryInstanceRepository.java` calls `initData()` in its constructor. - The seed data includes fixed entries such as `production-proxy`, `staging-proxy`, and `dev-direct`. ### Expected Behavior The default repository state should be empty. Demo instance records should only be loaded when an explicit demo/seed flag is enabled. ### Scope This is in the RocketMQ Studio control-plane scope: ARCH-01 multi-cluster/instance management should avoid fabricating resources by default. -- 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]
