RockteMQ-AI commented on issue #2210: URL: https://github.com/apache/rocketmq-dashboard/issues/2210#issuecomment-5295483406
**Issue Evaluation** Category: `enhancement` | Status: **Evaluated** **Feasibility:** Feasible **Scope:** `InstanceService`, `InstanceController`, Studio UI instance management **Compatibility:** Additive — new `force` query parameter; existing delete semantics unchanged The analysis is accurate. The current preflight in `InstanceService` calls `provider.countTopics(id)` / `provider.countGroups(id)` before `instanceRepository.deleteById`, which means any provider unavailability (decommissioned endpoint, expired credentials, DNS failure) permanently traps the registration. The proposed 8-point safety contract is well-designed: 1. Normal delete keeps the authoritative preflight ✓ 2. `force=true` does NOT bypass known managed-resource conflicts ✓ 3. Force only activates when preflight is *unavailable*, not when it reports resources ✓ 4. Distinct machine-readable error for unavailable-preflight vs conflict ✓ 5. Audit trail with `forced=true` and sanitized failure summary ✓ This is a clean improvement that resolves a real operational pain point. The safety contract correctly prevents `force` from becoming an unconditional bypass. -- 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]
