Frun1na opened a new issue, #4624: URL: https://github.com/apache/rocketmq-dashboard/issues/4624
### Bug Description `rmqctl` prompts "Type \"yes\" to continue" before executing L2/L3 mutations, but after the user confirms, the execution call is sent **without** a `confirm_token`. The server requires a token issued by a matching dry-run preview for every non-dry-run mutation and rejects the call with `CONFIRMATION_TOKEN_REQUIRED` (HTTP 400). The transparent two-phase handshake that fetches the token automatically only runs when `--yes` is supplied (`cmd/catalog.go`: `if tool.RiskLevel != "L1" && runtime.options.yes`), so the interactive confirmation path can never reach a successful execution: ``` $ rmqctl topic update --topic-name orders --write-queues 8 WARNING ... Type "yes" to continue: yes ERROR CONFIRMATION_TOKEN_REQUIRED ... ``` ### Steps to Reproduce 1. Run any L2 mutation (e.g. `rmqctl topic update ...`) against a Studio server, without `--yes` and without `--confirm-token`. 2. Answer "yes" at the interactive prompt. 3. The server rejects the execution with `CONFIRMATION_TOKEN_REQUIRED`. Expected: after the user confirms, the CLI runs the dry-run preview itself and executes with the issued token (as it already does for `--yes`). Fix proposed in #4623. -- 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]
