youngkermit8-coder opened a new pull request, #1581: URL: https://github.com/apache/rocketmq-dashboard/pull/1581
## Summary - validate Tencent Cloud RocketMQ 5.x Topic queue counts locally before OpenAPI calls - reject configured counts outside the documented 3–16 range - reject different positive write/read counts because Tencent accepts only one `QueueNum` - preserve the default create count of 8 and the update behavior that omits `QueueNum` when both values are zero ## Root cause Studio models separate write and read queue counts, while Tencent Cloud's CreateTopic and ModifyTopic APIs expose a single `QueueNum` field. The provider previously checked only for negative values and then silently preferred a positive write count over the read count. Unsupported or inconsistent values therefore reached the cloud API and either failed remotely or produced a result different from the requested model. Tencent Cloud documents `QueueNum` as a single value in the range 3–16: - https://cloud.tencent.com/document/api/1493/97947 - https://cloud.tencent.com/document/product/1493/97944 Fixes #1579. ## Verification ```text mvn -Dtest=TencentInstanceProviderTest clean package Tests run: 7, Failures: 0, Errors: 0, Skipped: 0 Checkstyle violations: 0 BUILD SUCCESS ``` The tests cover the default value, both valid boundaries, values below and above the supported range, mismatched write/read counts, no OpenAPI interaction on invalid requests, and omission of the optional update field. -- 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]
