RockteMQ-AI commented on issue #4624: URL: https://github.com/apache/rocketmq-dashboard/issues/4624#issuecomment-5752312791
**Issue Evaluation** Category: `bug` | Status: **Confirmed** The reported issue has been verified against the current codebase. **Root Cause:** In `rmqctl/cmd/catalog.go` (line 216), the transparent two-phase confirmation handshake (dry-run preview → extract `confirm_token` → execute with token) is gated behind `runtime.options.yes`. When the user confirms interactively (without `--yes`), the code path at line 319 calls `confirm()` which only prints the prompt but does not trigger the token-fetching preview, so the subsequent execution call lacks the required `confirm_token`. **Impact:** All interactive L2/L3 mutations via `rmqctl` (topic update, delete, etc.) will fail with `CONFIRMATION_TOKEN_REQUIRED` after the user confirms. Only `--yes` mode works. **Severity:** high — the default interactive workflow is completely broken for any non-dry-run mutation. A fix has been proposed in #4623. --- *Automated evaluation by github-manager* -- 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]
