RockteMQ-AI commented on issue #1113: URL: https://github.com/apache/rocketmq-dashboard/issues/1113#issuecomment-5202074081
**Issue Evaluation** Category: `enhancement` | Status: **Evaluated** **Feasibility:** feasible **Scope:** Proxy connection model, Instance entity, persistence layer, frontend Proxy management page **Compatibility:** Requires migration strategy for existing deployments with process-local Proxy config This is a well-scoped design issue. The current reliance on process-local Proxy address data is fragile — restarts lose configuration and multi-instance deployments cannot distinguish per-instance Proxy targets. Defining a durable, instance-scoped Proxy connection model before adding CRUD is the right approach. Key design decisions to resolve: 1. Whether Proxy addresses extend the existing `Instance.endpoint` model or require a separate one-to-many entity 2. Migration path for existing unscoped configurations 3. Frontend UX for Proxy address management within the instance context **Recommendation:** proceed with design discussion before implementation. --- *Automated evaluation by github-manager-bot* -- 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]
