zmuxuny opened a new issue, #4491:
URL: https://github.com/apache/rocketmq-dashboard/issues/4491

   ## Motivation
   
   RocketMQ Studio already has a Topic-level **Send Message** operator 
workflow, but the backend currently returns HTTP 501 for every cloud instance 
and the UI hides the action. This makes the same diagnostic workflow available 
for Apache instances but unavailable for managed RocketMQ 5.x instances.
   
   The SDK versions already pinned by Studio expose official control-plane 
test-send APIs:
   
   - Aliyun RocketMQ 5.x: `VerifySendMessage`, including body/tag/key, user 
properties, FIFO message group and delivery timestamp.
   - Tencent Trocket 5.x: `SendMessage`, documented for sending a small number 
of console test messages and returning a message ID.
   
   No dependency upgrade is required.
   
   ## Proposed behavior
   
   Add a provider-level `MESSAGE_SEND` capability and `sendMessage` operation, 
then route the existing Studio send workflow through `InstanceProvider` instead 
of hard-coding Apache.
   
   - Apache keeps the existing producer path unchanged.
   - Aliyun maps the existing `SendMessageDTO` to `VerifySendMessage`.
   - Tencent maps body/key/tag to `SendMessage`; fields its console API cannot 
represent are rejected explicitly instead of silently discarded.
   - The Topic UI exposes test sending for cloud **NORMAL** topics. Advanced 
FIFO/delay controls stay out of scope until the UI can collect the required 
semantics safely.
   
   ## Safety / scope
   
   This is an operator diagnostic feature, not a replacement for application 
producers. Existing authentication/authorization on the mutation endpoint 
remains unchanged. Provider errors stay visible, and unsupported fields fail 
closed.
   
   ## Acceptance criteria
   
   1. NORMAL topics on Aliyun and Tencent instances can send a test message and 
receive a message ID.
   2. Apache behavior is unchanged.
   3. Aliyun preserves supported tag/key/properties and advanced DTO fields.
   4. Tencent never silently drops unsupported user properties/FIFO/delay 
fields.
   5. Provider capability contracts advertise `MESSAGE_SEND`.
   6. Provider mapping tests and Topic-page UI regression tests cover the new 
behavior.
   
   AI-assisted design and implementation; SDK signatures and current master 
behavior were verified locally before opening this issue.


-- 
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]

Reply via email to