Aias00 opened a new issue, #1949: URL: https://github.com/apache/rocketmq-dashboard/issues/1949
## Track RocketMQ Studio Track 1: unified control plane / multi-architecture compatibility. ## Problem Studio persists only two instance access types today: `PROXY` and `DIRECT`. As a result, Apache RocketMQ 5.0 Proxy Local mode and Proxy Cluster mode are collapsed into the same value even though they represent different deployment topologies and capability sets. The domain already defines `ClusterType.V5_PROXY_LOCAL` and `ClusterType.V5_PROXY_CLUSTER`, but `InstanceType` and the instance form cannot select them. `RocketMQDashboardProvider` therefore maps every non-direct instance to `V5_PROXY_CLUSTER`. ## Expected behavior - Apache instances can explicitly select Proxy Local, Proxy Cluster, or Direct access. - Dashboard/runtime views map those values to the matching cluster type. - Existing persisted `PROXY` records remain readable and retain Proxy Cluster-compatible behavior. - Older API clients sending `PROXY` when creating an Apache instance are normalized to the explicit Cluster value instead of producing new ambiguous records. - Managed cloud instances may retain the generic `PROXY` value because their physical deployment topology is vendor-controlled. ## Proposed scope 1. Add `PROXY_LOCAL` and `PROXY_CLUSTER` to the backend and frontend instance contracts. 2. Add compatibility helpers so legacy `PROXY` remains supported. 3. Update the Apache instance create/filter UI and type labels. 4. Map instance access types to `V4_DIRECT`, `V5_PROXY_LOCAL`, or `V5_PROXY_CLUSTER` in runtime views. 5. Update API/schema documentation and add backend/frontend regression tests. ## Verification - New Apache Local and Cluster instances persist distinct values. - Legacy `PROXY` create requests normalize to `PROXY_CLUSTER`. - Existing `PROXY` records still deserialize successfully. - Dashboard cluster rows expose the correct `ClusterType` for Local, Cluster, legacy Proxy, and Direct instances. -- 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]
