Aias00 opened a new issue, #1113: URL: https://github.com/apache/rocketmq-dashboard/issues/1113
## Problem The Studio Proxy page currently relies on process-local proxy address data and default endpoints. That configuration is neither persisted nor tied to the selected managed instance, so a restart or a multi-instance deployment can display or operate on the wrong Proxy target. ## Design scope Define a durable, instance-scoped Proxy connection model before adding CRUD: - decide whether Proxy addresses belong to the existing `Instance.endpoint` model or require a separate one-to-many address entity; - define migration and backward compatibility for existing single endpoint instances; - define validation, deduplication, and masking rules for any credentials; - make reads and writes resolve the selected instance rather than a process-global default; - document which lifecycle operations can be backed by the current RocketMQ Admin APIs and which must remain unavailable. ## Out of scope This Issue does not add simulated Proxy configuration, guessed runtime operations, or a database schema before the ownership model is agreed. -- 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]
