Aias00 opened a new issue, #869: URL: https://github.com/apache/rocketmq-dashboard/issues/869
### Problem `ClientProviderStub` is registered as a normal Spring component and returns hard-coded client connections such as `producer-001` and `consumer-001`. With the current default application profile, these demo rows can be exposed through `/api/clients` even when Studio is not connected to a real RocketMQ client source. For the Control Plane / CLIENT-01 scope, client connection data must be protocol-aware and trustworthy. Showing demo client rows by default can mislead operators during validation and troubleshooting. ### Expected behavior - Do not expose demo client connections unless demo data is explicitly enabled. - Keep the application startup safe when no real client provider is wired yet. - Return an empty client list as the default fallback instead of hard-coded clients. - Add tests covering the default empty provider and the opt-in demo provider behavior. ### Scope RocketMQ Studio / CLIENT-01 client connection management baseline. -- 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]
