pilichoumao opened a new pull request, #7278: URL: https://github.com/apache/rocketmq-dashboard/pull/7278
### Which Issue(s) This PR Fixes Fixes #7276. ### Brief Description Draft enhancement pending discussion of the tool's failure-detail visibility and output shape in #7276. `rmq.message.redelivery_dlq` currently returns only aggregate counts even though the authorized REST resend already provides bounded failed-message IDs, destinations and reasons. Project those existing details and their independent truncation flag into the tool result. Preserve all six aggregate fields, confirmations, authorization, audit and resend behavior; do not retry automatically. Extend the strict schema with optional `failures` (at most 100 items) and `failuresTruncated`, keep an unresolved destination absent, retain legacy aggregate-only output as valid, regenerate the Go catalog, and document the result. Handler, central schema and CLI default/JSON/YAML tests cover the complete output chain. This builds on #4817's REST failure details. ### How Did You Test This Change? - JDK 21: `mvn -B -ntp -Dtest=MessageRedeliveryDlqToolHandlerTest,ToolOutputSchemaContractTest,ToolCatalogTest test`: 23 passed, including legacy output, 100 retained details/101 failures, unresolved targets and rejection of excessive/undeclared fields. - `make -C rmqctl ci`: passed, including catalog freshness, gofmt, race tests, vet, six target builds and per-target license checks. The focused CLI test checks six format/legacy combinations through the real command and HTTP test server. - `git diff --check`: passed. - Clean Linux/ECS Maven/build, discriminating projection mutation and Go verification are pending. The default local Maven cache has a RocketMQ POM differing from Maven Central, so it is not used as release-build evidence. No live Broker or database was contacted. The PR remains draft for design feedback even after validation completes. -- 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]
