youngkermit8-coder opened a new issue, #1579: URL: https://github.com/apache/rocketmq-dashboard/issues/1579
## Description Tencent Cloud RocketMQ 5.x exposes one `QueueNum` field for both CreateTopic and ModifyTopic, with the documented range 3–16: - https://cloud.tencent.com/document/api/1493/97947 - https://cloud.tencent.com/document/product/1493/97944 `TencentInstanceProvider` currently validates only that Studio's separate `writeQueues` and `readQueues` values are non-negative. It then chooses `writeQueues` when positive and otherwise chooses `readQueues`. As a result, the provider can: - send unsupported queue counts such as 1, 2, or values above 16 to Tencent Cloud; - silently discard a different positive `readQueues` value when `writeQueues` is also set. These invalid requests fail only after an unnecessary cloud API call, and mismatched values make the returned Studio model disagree with the single queue count actually sent. ## Expected behavior Before calling Tencent Cloud: - a configured queue count must be between 3 and 16; - when both write and read queue counts are positive, they must match because Tencent Cloud accepts only one `QueueNum`; - the existing all-zero create behavior may continue to use the provider default, while an all-zero update may continue to omit `QueueNum`. Regression tests should verify that invalid and mismatched values fail locally and do not invoke `CreateTopic` or `ModifyTopic`. -- 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]
