pilichoumao opened a new issue, #7276:
URL: https://github.com/apache/rocketmq-dashboard/issues/7276
### Enhancement proposal
On `rocketmq-studio` at 127c47b06a268cc74224d5f34c56ec7c36ac0d55, the REST
DLQ resend response already contains bounded per-message
`failures[{msgId,targetTopic,reason}]` and `failuresTruncated`. The
`rmq.message.redelivery_dlq` tool intentionally projects only the six aggregate
fields, so AI/CLI consumers cannot see the failed IDs or the reason available
in the UI.
Could the tool expose these existing bounded details as optional output
properties? The existing output is consistent with its schema; this is an
enhancement proposal rather than a claim that the current tool violates its
contract.
### Proposed scope and compatibility
- Keep the existing aggregate fields, instance/resource checks,
confirmation, audit and resend behavior.
- Expose the provider's at-most-100 details and its independent truncation
flag. Keep an unresolved target absent rather than inventing one. Do not retry
automatically.
- Extend the strict output schema with optional properties, update the
central output samples and handler coverage, regenerate the Go catalog, and
test CLI default/JSON/YAML passthrough.
- Retain the legacy output shape as schema-valid so older servers and
clients remain compatible.
- No additional secret lookup or new data source; use the same concise error
details already returned by the authorized REST operation. The appropriate
visibility and output shape remain subject to maintainer feedback.
### Evidence
A Linux/ECS projection probe covered one failed message, a 101-failure
result with 100 retained details, and an empty success result. Current code
keeps all aggregate values but drops the two failure scenarios' details and the
truncation flag; a temporary projection extension retained all three. This was
not a live Broker or complete MCP test. A reviewable draft can include full
schema/catalog validation while this design is discussed.
Related: #4817 introduced the REST failure details; #6845 and #6867 concern
different input/query contracts. Full-state searches for
`MessageRedeliveryDlqOutput` and DLQ tool failure details found no equivalent
proposal.
--
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]
