Aias00 opened a new issue, #1167: URL: https://github.com/apache/rocketmq-dashboard/issues/1167
## Problem The Topic delete request already carries `instanceId`, but `ApacheInstanceProvider.deleteTopic` delegates to `AdminClient.deleteTopic(name)`. `RocketMQAdminClientImpl` then uses the process-wide `DefaultMQAdminExt`, so deletion may target the configured default cluster instead of the selected instance. PR #1150 scopes the persisted database deletion by `(cluster_id, name)`, but does not change the runtime AdminClient endpoint. ## Expected behavior For Apache instances, Topic deletion resolves `instanceId -> Instance.endpoint` through `RuntimeAdminClientResolver` and executes the Broker/NameServer operation through that instance-bound Admin client. The legacy no-instance path remains compatible. ## Scope - Propagate `instanceId` through the `AdminClient` delete contract. - Route Apache provider deletion through `RuntimeAdminClientResolver`. - Add regression coverage proving the global Admin client is not used when an instance is selected. ## Related - #982 - #1136 - #1165 -- 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]
