youngkermit8-coder opened a new issue, #1507: URL: https://github.com/apache/rocketmq-dashboard/issues/1507
## Bug Report ### Runtime platform environment Any environment running the `rocketmq-studio` branch. ### RocketMQ version `rocketmq-studio` at `2471563` or later. ### Describe the Bug The Tencent Cloud RocketMQ 5.x onboarding catalog exposes a hard-coded list of only 10 regions. Tencent Cloud currently documents 19 regions that support 5.x clusters, so instances in the following supported regions cannot be selected in Studio: - `ap-shenzhen-fsi` - `ap-shanghai-fsi` - `ap-shanghai-adc` - `ap-bangkok` - `ap-jakarta` - `ap-seoul` - `na-ashburn` - `eu-frankfurt` - `sa-saopaulo` There is a second issue for the two financial regions. `TencentClientFactory` always uses the nearby-access endpoint `trocket.tencentcloudapi.com`, while Tencent Cloud documents that financial regions are isolated from non-financial regions and require a regional endpoint: - `trocket.ap-shenzhen-fsi.tencentcloudapi.com` - `trocket.ap-shanghai-fsi.tencentcloudapi.com` Therefore, adding the missing financial regions to the dropdown alone would still make their catalog calls fail. Official references: - Product region matrix: https://cloud.tencent.com/document/product/1493/119006 - API request endpoints and financial-region requirement: https://cloud.tencent.com/document/product/1493/96034 ### Steps to Reproduce 1. Create a Tencent Cloud RocketMQ 5.x cluster in one of the missing regions, for example `ap-seoul`. 2. Open Studio's instance onboarding modal and choose Tencent Cloud. 3. Select a Tencent credential. 4. Observe that Seoul is not available in the region selector, so the cluster cannot be discovered or added. For a financial-region credential, calling the catalog with `ap-shenzhen-fsi` also uses the non-financial nearby-access endpoint instead of the required regional endpoint. ### Expected Behavior All regions currently documented for Tencent Cloud RocketMQ 5.x should be selectable. SDK clients for financial regions should use their region-specific endpoints; other regions should continue using the recommended nearby-access endpoint. ### Proposed Fix - Complete the supported 5.x region catalog. - Select the regional API endpoint for `*-fsi` regions. - Add regression tests for both the region list and endpoint selection. -- 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]
