Aias00 opened a new issue, #2002: URL: https://github.com/apache/rocketmq-dashboard/issues/2002
### Before Creating the Issue - [x] I searched the open issues and pull requests for the same API documentation drift. - [x] I compared the published contract with the latest `rocketmq-studio` controllers and DTOs. ### Description Several Track 1 runtime endpoints in `docs/api-spec.md` no longer match the instance-scoped backend contract: - message list and trace omit required `instanceId`; - DLQ list documents `clusterId` instead of required `instanceId`; - DLQ resend omits required `instanceId`, documents time fields as ISO strings instead of epoch-millisecond numbers, and documents a null response although the endpoint returns a resend outcome; - client connections omit required `instanceId`; - NameServer restart, upgrade, and delete omit required `clusterId`; - NameServer update documents a nonexistent `newAddr` field instead of the DTO's optional `version` field; - NameServer upgrade omits required `targetVersion`; - message list omits the supported `tag` filter and documents timestamps with incompatible types. Clients following the published examples receive validation errors or construct requests that do not express the selected instance/cluster scope. ### Expected behavior The API specification should accurately describe required instance and cluster context, request field names/types, and response shapes implemented by the controllers and DTOs. ### Suggested scope Update only the affected Message, DLQ, Client, and NameServer sections in `docs/api-spec.md`, with examples that preserve the selected instance context. ### Verification Cross-check every documented field against: - `MessageController` - `DLQController` / `DLQResendRequestDTO` / `DLQResendResultVO` - `ClientController` - `NameServerController` and its command DTOs ### Scope RocketMQ Studio Track 1: unified control-plane API contract. -- 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]
