X-LightYear opened a new issue, #7302:
URL: https://github.com/apache/rocketmq-dashboard/issues/7302
## Problem
The `rmq.cluster.list` MCP catalog accepts any non-empty string for the
optional `status` filter, but the handler only recognizes the four
`ClusterStatus` values `healthy`, `warning`, `error`, and `offline`.
## Reproduction
1. Call `rmq.cluster.list` with `{ status: degraded }`.
2. The runtime input validator accepts the request.
3. The handler compares the value with the supported enum values and returns
an empty result instead of reporting an invalid input.
## Expected behavior
The catalog/runtime contract should reject unsupported status values before
handler execution.
## Actual behavior
An unsupported status value is accepted by the MCP input schema and silently
produces no matching clusters.
## Fix
Declare the supported status enum in the YAML tool catalog and regenerate
the rmqctl catalog so MCP clients receive the same contract.
## Testing
- deterministic runtime schema regression test rejects `degraded`
- affected catalog, cluster handler, and output contract tests pass
- rmqctl catalog tests pass
- checkstyle passes
Fixes #REPLACE
--
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]
