Aias00 opened a new issue, #974: URL: https://github.com/apache/rocketmq-dashboard/issues/974
## Problem\nThe default MySQL schema inserts demo instances, topics, consumer groups, ACL rules, and ACL users after creating tables. docker-compose applies this schema automatically for every fresh database volume.\n\nA normal Studio deployment therefore starts with fabricated control-plane resources and credentials before an operator configures a real cluster. This reintroduces the production-data problem addressed by #790, but through the persistent schema rather than an in-memory repository.\n\n## Evidence\n- : unconditional statements begin at the instance seed block.\n- : mounts this schema into the MySQL initialization directory.\n\n## Expected behavior\nThe default production schema only creates database structure. Demo data must require an explicit development/demo opt-in.\n\n## Proposed fix\nMove seed records into a separate demo SQL file or profile, remove them from the production schema, and update deployment documentation.\n\n## Scope\nStudio Track 1 control-plane da ta correctness and deployment safety. -- 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]
