youngkermit8-coder opened a new pull request, #1521:
URL: https://github.com/apache/rocketmq-dashboard/pull/1521

   ## What changed
   
   - Scope topic deletion broker RPCs to the selected instance's cluster.
   - Scope consumer-group deletion RPCs to the same target cluster.
   - Resolve the cluster name once per operation and reuse it for broker, 
NameServer, and metadata cleanup.
   - Add dual-cluster regression coverage proving the unrelated cluster does 
not receive deletion calls.
   
   ## Why
   
   PR #1429 fixed the create/update paths described in #1428, but the two 
delete paths still called `getAllMasterBrokerAddrs(admin)`. In an instance that 
can see multiple clusters, deleting a topic or consumer group could therefore 
send the operation to every cluster.
   
   This completes the remaining delete-path scope from #1428 while keeping the 
existing cluster-resolution behavior.
   
   ## Impact
   
   Topic and consumer-group deletions now target only the selected cluster, 
preventing same-named resources in other clusters from being deleted.
   
   ## Validation
   
   Validated after applying this commit on top of the backend compilation fix 
from #1502 (`c00a5ef`):
   
   - `mvn -Dtest=RocketMQAdminClientImplTest test` — 16 tests passed
   - Checkstyle — 0 violations
   - `mvn -DskipTests package` — success
   
   Refs #1428
   


-- 
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]

Reply via email to