Aias00 opened a new issue, #956: URL: https://github.com/apache/rocketmq-dashboard/issues/956
## Problem\n\nRocketMQ Studio currently stores general settings and Prometheus data-source definitions in . A process restart loses the configuration, which prevents durable multi-cluster operations.\n\nThis issue covers persistence for **Studio-owned configuration only**. It does not introduce a database mirror for RocketMQ metadata, messages, offsets, or runtime state.\n\n## Scope\n\n- Add an opt-in PostgreSQL-backed implementation.\n- Persist:\n - \n - \n- Keep the in-memory implementation as the default for local development.\n- Add a dedicated Spring profile and schema migration.\n- Add integration coverage against PostgreSQL using Testcontainers.\n\n## Security boundary\n\nSecrets must not be exposed by read APIs or application logs. The initial storage implementation must document how API keys are protected and leave encryption/secret-reference integration as an explicit follow-up if not delivered in this change.\n\n## Non-goals\n\n- Persisting Topic, Consumer Group, Bro ker, Proxy, message, or offset data.\n- Replacing / .\n- Adding cloud-provider metadata adapters.\n\n## Acceptance criteria\n\n- With the PostgreSQL profile enabled, a Studio restart preserves general settings and data-source CRUD state.\n- Default startup remains dependency-free and uses the existing in-memory repository.\n- Schema is managed through versioned migrations.\n- PostgreSQL integration tests cover save, update, delete, reload, and repository selection.\n- API-key values are neither returned in plaintext by read APIs nor written to logs. -- 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]
