tencentcloud-sdk-nodejs-tdmq 4.0.720 → 4.0.722
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +313 -0
- package/SERVICE_CHANGELOG.md +298 -42
- package/package.json +1 -1
- package/products.md +17 -17
- package/src/services/tdmq/v20200217/tdmq_client.ts +61 -32
- package/src/services/tdmq/v20200217/tdmq_models.ts +339 -108
- package/tencentcloud/services/tdmq/v20200217/tdmq_client.d.ts +20 -12
- package/tencentcloud/services/tdmq/v20200217/tdmq_client.js +27 -15
- package/tencentcloud/services/tdmq/v20200217/tdmq_models.d.ts +330 -108
|
@@ -32,14 +32,15 @@ import {
|
|
|
32
32
|
ModifyRabbitMQVirtualHostRequest,
|
|
33
33
|
ModifyEnvironmentAttributesRequest,
|
|
34
34
|
DeleteClusterResponse,
|
|
35
|
-
|
|
35
|
+
ResetRocketMQConsumerOffSetResponse,
|
|
36
|
+
DescribeTopicMsgsResponse,
|
|
36
37
|
ModifyCmqSubscriptionAttributeResponse,
|
|
37
38
|
CreateCmqTopicRequest,
|
|
38
39
|
ModifyRabbitMQVipInstanceRequest,
|
|
39
40
|
Filter,
|
|
40
41
|
ImportRocketMQTopicsResponse,
|
|
41
42
|
DescribeRocketMQMigratingTopicListRequest,
|
|
42
|
-
|
|
43
|
+
ModifyClusterResponse,
|
|
43
44
|
ModifyRocketMQInstanceSpecRequest,
|
|
44
45
|
BindCluster,
|
|
45
46
|
ModifyRoleResponse,
|
|
@@ -108,6 +109,7 @@ import {
|
|
|
108
109
|
DescribeRocketMQClusterResponse,
|
|
109
110
|
DeleteRocketMQVipInstanceResponse,
|
|
110
111
|
DescribeCmqSubscriptionDetailResponse,
|
|
112
|
+
PulsarProInstance,
|
|
111
113
|
VpcBindRecord,
|
|
112
114
|
RewindCmqQueueRequest,
|
|
113
115
|
DescribeRabbitMQUserResponse,
|
|
@@ -126,13 +128,14 @@ import {
|
|
|
126
128
|
CreateRabbitMQUserResponse,
|
|
127
129
|
AcknowledgeMessageResponse,
|
|
128
130
|
DeleteEnvironmentRolesResponse,
|
|
131
|
+
RocketMQTopicDistribution,
|
|
129
132
|
DescribeClusterDetailRequest,
|
|
130
133
|
ModifyRoleRequest,
|
|
131
134
|
RetentionPolicy,
|
|
132
135
|
DeleteCmqQueueResponse,
|
|
133
136
|
DescribeRocketMQClusterRequest,
|
|
134
137
|
DeleteRocketMQTopicResponse,
|
|
135
|
-
|
|
138
|
+
MsgLog,
|
|
136
139
|
ModifyCmqTopicAttributeRequest,
|
|
137
140
|
DescribeRabbitMQVipInstancesResponse,
|
|
138
141
|
DeleteRolesRequest,
|
|
@@ -159,16 +162,18 @@ import {
|
|
|
159
162
|
ModifyRocketMQGroupRequest,
|
|
160
163
|
FilterSubscription,
|
|
161
164
|
DescribeCmqTopicsResponse,
|
|
165
|
+
SendRocketMQMessageResponse,
|
|
162
166
|
DescribeCmqTopicDetailRequest,
|
|
163
167
|
CmqTopic,
|
|
164
168
|
DescribeRocketMQMigratingTopicListResponse,
|
|
165
169
|
UnbindCmqDeadLetterResponse,
|
|
170
|
+
EnvironmentRole,
|
|
166
171
|
ModifyRocketMQNamespaceResponse,
|
|
167
172
|
InternalTenant,
|
|
168
173
|
DescribePulsarProInstancesRequest,
|
|
169
174
|
DeleteEnvironmentsRequest,
|
|
170
175
|
DescribeRocketMQClustersRequest,
|
|
171
|
-
|
|
176
|
+
ConsumerLogs,
|
|
172
177
|
DescribeBindVpcsRequest,
|
|
173
178
|
DescribeClustersResponse,
|
|
174
179
|
RocketMQConsumerConnection,
|
|
@@ -194,7 +199,7 @@ import {
|
|
|
194
199
|
RocketMQClusterDetail,
|
|
195
200
|
DeleteRocketMQGroupResponse,
|
|
196
201
|
CreateCmqQueueResponse,
|
|
197
|
-
|
|
202
|
+
DescribeMsgTraceResponse,
|
|
198
203
|
PartitionsTopic,
|
|
199
204
|
DescribeRocketMQGroupsResponse,
|
|
200
205
|
RocketMQMigrationTopicDistribution,
|
|
@@ -234,7 +239,7 @@ import {
|
|
|
234
239
|
PulsarProClusterSpecInfo,
|
|
235
240
|
DescribeCmqTopicsRequest,
|
|
236
241
|
DescribeRocketMQSubscriptionsRequest,
|
|
237
|
-
|
|
242
|
+
ConsumerLog,
|
|
238
243
|
DeleteTopicsRequest,
|
|
239
244
|
CmqTransactionPolicy,
|
|
240
245
|
BundleSetOpt,
|
|
@@ -245,6 +250,7 @@ import {
|
|
|
245
250
|
PrometheusEndpointInfo,
|
|
246
251
|
CreateCmqSubscribeRequest,
|
|
247
252
|
DeleteCmqSubscribeRequest,
|
|
253
|
+
ServerLog,
|
|
248
254
|
DescribeAMQPClustersResponse,
|
|
249
255
|
RabbitMQUser,
|
|
250
256
|
DescribeCmqDeadLetterSourceQueuesResponse,
|
|
@@ -269,6 +275,7 @@ import {
|
|
|
269
275
|
DeleteRabbitMQVirtualHostRequest,
|
|
270
276
|
CreateRocketMQTopicRequest,
|
|
271
277
|
QueueQuota,
|
|
278
|
+
Sort,
|
|
272
279
|
CreateRoleResponse,
|
|
273
280
|
DeleteRocketMQClusterRequest,
|
|
274
281
|
DescribePulsarProInstancesResponse,
|
|
@@ -282,7 +289,7 @@ import {
|
|
|
282
289
|
PulsarNetworkAccessPointInfo,
|
|
283
290
|
CreateRocketMQTopicResponse,
|
|
284
291
|
CreateRabbitMQVirtualHostRequest,
|
|
285
|
-
|
|
292
|
+
DescribeTopicMsgsRequest,
|
|
286
293
|
VpcEndpointInfo,
|
|
287
294
|
CreateCmqQueueRequest,
|
|
288
295
|
ModifyEnvironmentRoleResponse,
|
|
@@ -296,6 +303,7 @@ import {
|
|
|
296
303
|
DescribeRocketMQConsumerConnectionsRequest,
|
|
297
304
|
CreateRoleRequest,
|
|
298
305
|
DescribeRocketMQTopicMsgsRequest,
|
|
306
|
+
DescribeMsgTraceRequest,
|
|
299
307
|
ImportRocketMQConsumerGroupsResponse,
|
|
300
308
|
DescribeEnvironmentAttributesResponse,
|
|
301
309
|
Role,
|
|
@@ -321,6 +329,7 @@ import {
|
|
|
321
329
|
Topic,
|
|
322
330
|
DeleteCmqSubscribeResponse,
|
|
323
331
|
TraceResult,
|
|
332
|
+
ProducerLog,
|
|
324
333
|
DeleteRabbitMQVipInstanceRequest,
|
|
325
334
|
DescribePublisherSummaryRequest,
|
|
326
335
|
DeleteSubscriptionsRequest,
|
|
@@ -760,16 +769,6 @@ export class Client extends TencentCloudCommon.AbstractClient {
|
|
|
760
769
|
return this.request("DescribeCmqSubscriptionDetail", req, cb)
|
|
761
770
|
}
|
|
762
771
|
|
|
763
|
-
/**
|
|
764
|
-
* 查询RabbitMQ vhost列表
|
|
765
|
-
*/
|
|
766
|
-
async DescribeRabbitMQVirtualHost(
|
|
767
|
-
req: DescribeRabbitMQVirtualHostRequest,
|
|
768
|
-
cb?: (error: string, rep: DescribeRabbitMQVirtualHostResponse) => void
|
|
769
|
-
): Promise<DescribeRabbitMQVirtualHostResponse> {
|
|
770
|
-
return this.request("DescribeRabbitMQVirtualHost", req, cb)
|
|
771
|
-
}
|
|
772
|
-
|
|
773
772
|
/**
|
|
774
773
|
* 枚举cmq死信队列源队列
|
|
775
774
|
*/
|
|
@@ -880,6 +879,16 @@ export class Client extends TencentCloudCommon.AbstractClient {
|
|
|
880
879
|
return this.request("DescribeRabbitMQUser", req, cb)
|
|
881
880
|
}
|
|
882
881
|
|
|
882
|
+
/**
|
|
883
|
+
* 删除角色,支持批量。
|
|
884
|
+
*/
|
|
885
|
+
async DeleteRoles(
|
|
886
|
+
req: DeleteRolesRequest,
|
|
887
|
+
cb?: (error: string, rep: DeleteRolesResponse) => void
|
|
888
|
+
): Promise<DeleteRolesResponse> {
|
|
889
|
+
return this.request("DeleteRoles", req, cb)
|
|
890
|
+
}
|
|
891
|
+
|
|
883
892
|
/**
|
|
884
893
|
* 更新RocketMQ集群信息
|
|
885
894
|
*/
|
|
@@ -970,6 +979,16 @@ export class Client extends TencentCloudCommon.AbstractClient {
|
|
|
970
979
|
return this.request("ResetMsgSubOffsetByTimestamp", req, cb)
|
|
971
980
|
}
|
|
972
981
|
|
|
982
|
+
/**
|
|
983
|
+
* 查询消息轨迹
|
|
984
|
+
*/
|
|
985
|
+
async DescribeMsgTrace(
|
|
986
|
+
req: DescribeMsgTraceRequest,
|
|
987
|
+
cb?: (error: string, rep: DescribeMsgTraceResponse) => void
|
|
988
|
+
): Promise<DescribeMsgTraceResponse> {
|
|
989
|
+
return this.request("DescribeMsgTrace", req, cb)
|
|
990
|
+
}
|
|
991
|
+
|
|
973
992
|
/**
|
|
974
993
|
* RabbitMQ专享版查询节点列表
|
|
975
994
|
*/
|
|
@@ -1121,13 +1140,13 @@ export class Client extends TencentCloudCommon.AbstractClient {
|
|
|
1121
1140
|
}
|
|
1122
1141
|
|
|
1123
1142
|
/**
|
|
1124
|
-
*
|
|
1143
|
+
* 查询RabbitMQ vhost列表
|
|
1125
1144
|
*/
|
|
1126
|
-
async
|
|
1127
|
-
req:
|
|
1128
|
-
cb?: (error: string, rep:
|
|
1129
|
-
): Promise<
|
|
1130
|
-
return this.request("
|
|
1145
|
+
async DescribeRabbitMQVirtualHost(
|
|
1146
|
+
req: DescribeRabbitMQVirtualHostRequest,
|
|
1147
|
+
cb?: (error: string, rep: DescribeRabbitMQVirtualHostResponse) => void
|
|
1148
|
+
): Promise<DescribeRabbitMQVirtualHostResponse> {
|
|
1149
|
+
return this.request("DescribeRabbitMQVirtualHost", req, cb)
|
|
1131
1150
|
}
|
|
1132
1151
|
|
|
1133
1152
|
/**
|
|
@@ -1240,6 +1259,18 @@ BatchReceivePolicy 的接口会一次性返回多条消息:
|
|
|
1240
1259
|
return this.request("CreateRocketMQNamespace", req, cb)
|
|
1241
1260
|
}
|
|
1242
1261
|
|
|
1262
|
+
/**
|
|
1263
|
+
* 批量发送消息
|
|
1264
|
+
|
|
1265
|
+
注意:TDMQ 批量发送消息的接口是在 TDMQ-HTTP 的服务侧将消息打包为一个 Batch,然后将该 Batch 在服务内部当作一次 TCP 请求发送出去。所以在使用过程中,用户还是按照单条消息发送的逻辑,每一条消息是一个独立的 HTTP 的请求,在 TDMQ-HTTP 的服务内部,会将多个 HTTP 的请求聚合为一个 Batch 发送到服务端。即,批量发送消息在使用上与发送单条消息是一致的,batch 的聚合是在 TDMQ-HTTP 的服务内部完成的。
|
|
1266
|
+
*/
|
|
1267
|
+
async SendBatchMessages(
|
|
1268
|
+
req: SendBatchMessagesRequest,
|
|
1269
|
+
cb?: (error: string, rep: SendBatchMessagesResponse) => void
|
|
1270
|
+
): Promise<SendBatchMessagesResponse> {
|
|
1271
|
+
return this.request("SendBatchMessages", req, cb)
|
|
1272
|
+
}
|
|
1273
|
+
|
|
1243
1274
|
/**
|
|
1244
1275
|
* 修改RabbitMQ专享版实例
|
|
1245
1276
|
*/
|
|
@@ -1341,15 +1372,13 @@ BatchReceivePolicy 的接口会一次性返回多条消息:
|
|
|
1341
1372
|
}
|
|
1342
1373
|
|
|
1343
1374
|
/**
|
|
1344
|
-
|
|
1345
|
-
|
|
1346
|
-
|
|
1347
|
-
|
|
1348
|
-
|
|
1349
|
-
|
|
1350
|
-
|
|
1351
|
-
): Promise<SendBatchMessagesResponse> {
|
|
1352
|
-
return this.request("SendBatchMessages", req, cb)
|
|
1375
|
+
* 消息查询
|
|
1376
|
+
*/
|
|
1377
|
+
async DescribeTopicMsgs(
|
|
1378
|
+
req: DescribeTopicMsgsRequest,
|
|
1379
|
+
cb?: (error: string, rep: DescribeTopicMsgsResponse) => void
|
|
1380
|
+
): Promise<DescribeTopicMsgsResponse> {
|
|
1381
|
+
return this.request("DescribeTopicMsgs", req, cb)
|
|
1353
1382
|
}
|
|
1354
1383
|
|
|
1355
1384
|
/**
|