The GitHub Actions job "CI" on rocketmq-dashboard.git/fix/cloud-topic-update-unsupported has succeeded. Run started by GitHub user Frun1na (triggered by Frun1na).
Head commit for run: 0cd7c23989cbbf9529fd9d6f9ab4161bb91dc904 / Apulupie <[email protected]> fix(topic): reject the cloud topic updates a vendor cannot apply Both cloud providers accepted a topic update that asked for properties their vendor API cannot change and returned the requested values as if they had been applied. Aliyun's CreateTopicRequest/UpdateTopicRequest carry no queue-count and no permission field, yet updateTopic sent only the remark and echoed the rest of the incoming VO; Tencent's ModifyTopicRequest carries the queue count but no permission, and both providers report every cloud topic as read-write on the read path. The console's edit dialog sends the topic's current values (zero queues and RW for Aliyun), so a remark-only update keeps working, while an explicit queue-count or permission change is now rejected with 400 the way the provider already rejects other operations it cannot perform. The create path is left unchanged: the console's create dialog always sends its 8/8 defaults. Report URL: https://github.com/apache/rocketmq-dashboard/actions/runs/38340728731 With regards, GitHub Actions via GitBox
