tencentcloud-sdk-nodejs 4.1.226 → 4.1.228
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/es/common/sdk_version.js +1 -1
- package/es/services/apm/v20210622/apm_client.js +3 -0
- package/es/services/bh/v20230418/bh_client.js +3 -0
- package/es/services/cls/v20201016/cls_client.js +34 -10
- package/es/services/ioa/v20220601/ioa_client.js +6 -0
- package/es/services/mongodb/v20190725/mongodb_client.js +3 -0
- package/es/services/mqtt/v20240516/mqtt_client.js +6 -0
- package/es/services/ocr/v20181119/ocr_client.js +154 -181
- package/es/services/tcb/v20180608/tcb_client.js +23 -8
- package/es/services/tdmq/v20200217/tdmq_client.js +3 -0
- package/es/services/vod/v20180717/vod_client.js +16 -7
- package/package.json +1 -1
- package/tencentcloud/common/sdk_version.d.ts +1 -1
- package/tencentcloud/common/sdk_version.js +1 -1
- package/tencentcloud/services/apm/v20210622/apm_client.d.ts +5 -1
- package/tencentcloud/services/apm/v20210622/apm_client.js +6 -0
- package/tencentcloud/services/apm/v20210622/apm_models.d.ts +26 -0
- package/tencentcloud/services/bh/v20230418/bh_client.d.ts +5 -1
- package/tencentcloud/services/bh/v20230418/bh_client.js +6 -0
- package/tencentcloud/services/bh/v20230418/bh_models.d.ts +58 -32
- package/tencentcloud/services/cdb/v20170320/cdb_models.d.ts +136 -116
- package/tencentcloud/services/cls/v20201016/cls_client.d.ts +43 -11
- package/tencentcloud/services/cls/v20201016/cls_client.js +63 -15
- package/tencentcloud/services/cls/v20201016/cls_models.d.ts +650 -192
- package/tencentcloud/services/ctsdb/v20230202/ctsdb_client.d.ts +1 -1
- package/tencentcloud/services/ctsdb/v20230202/ctsdb_models.d.ts +6 -1
- package/tencentcloud/services/emr/v20190103/emr_models.d.ts +8 -0
- package/tencentcloud/services/ess/v20201111/ess_models.d.ts +30 -44
- package/tencentcloud/services/essbasic/v20210526/essbasic_models.d.ts +30 -77
- package/tencentcloud/services/hai/v20230812/hai_client.d.ts +1 -1
- package/tencentcloud/services/hai/v20230812/hai_client.js +1 -1
- package/tencentcloud/services/hai/v20230812/hai_models.d.ts +4 -4
- package/tencentcloud/services/ioa/v20220601/ioa_client.d.ts +9 -1
- package/tencentcloud/services/ioa/v20220601/ioa_client.js +12 -0
- package/tencentcloud/services/ioa/v20220601/ioa_models.d.ts +108 -36
- package/tencentcloud/services/live/v20180801/live_client.d.ts +4 -4
- package/tencentcloud/services/live/v20180801/live_client.js +2 -2
- package/tencentcloud/services/live/v20180801/live_models.d.ts +386 -24
- package/tencentcloud/services/lke/v20231130/lke_models.d.ts +56 -30
- package/tencentcloud/services/mongodb/v20190725/mongodb_client.d.ts +5 -1
- package/tencentcloud/services/mongodb/v20190725/mongodb_client.js +6 -0
- package/tencentcloud/services/mongodb/v20190725/mongodb_models.d.ts +52 -9
- package/tencentcloud/services/monitor/v20180724/monitor_models.d.ts +7 -7
- package/tencentcloud/services/mps/v20190612/mps_models.d.ts +10 -2
- package/tencentcloud/services/mqtt/v20240516/mqtt_client.d.ts +9 -1
- package/tencentcloud/services/mqtt/v20240516/mqtt_client.js +12 -0
- package/tencentcloud/services/mqtt/v20240516/mqtt_models.d.ts +115 -26
- package/tencentcloud/services/ocr/v20181119/ocr_client.d.ts +599 -664
- package/tencentcloud/services/ocr/v20181119/ocr_client.js +705 -788
- package/tencentcloud/services/ocr/v20181119/ocr_models.d.ts +6405 -6898
- package/tencentcloud/services/smh/v20210712/smh_models.d.ts +1 -1
- package/tencentcloud/services/sms/v20210111/sms_models.d.ts +13 -8
- package/tencentcloud/services/ssl/v20191205/ssl_models.d.ts +1 -1
- package/tencentcloud/services/tcb/v20180608/tcb_client.d.ts +69 -9
- package/tencentcloud/services/tcb/v20180608/tcb_client.js +82 -12
- package/tencentcloud/services/tcb/v20180608/tcb_models.d.ts +478 -144
- package/tencentcloud/services/tcbr/v20220217/tcbr_models.d.ts +18 -6
- package/tencentcloud/services/tcss/v20201101/tcss_models.d.ts +9 -10
- package/tencentcloud/services/tdai/v20250717/tdai_client.d.ts +1 -1
- package/tencentcloud/services/tdai/v20250717/tdai_models.d.ts +120 -74
- package/tencentcloud/services/tdmq/v20200217/tdmq_client.d.ts +5 -1
- package/tencentcloud/services/tdmq/v20200217/tdmq_client.js +6 -0
- package/tencentcloud/services/tdmq/v20200217/tdmq_models.d.ts +443 -0
- package/tencentcloud/services/teo/v20220901/teo_client.d.ts +1 -1
- package/tencentcloud/services/teo/v20220901/teo_client.js +1 -1
- package/tencentcloud/services/teo/v20220901/teo_models.d.ts +13 -34
- package/tencentcloud/services/tione/v20211111/tione_models.d.ts +40 -0
- package/tencentcloud/services/trtc/v20190722/trtc_models.d.ts +8 -0
- package/tencentcloud/services/vod/v20180717/vod_client.d.ts +33 -22
- package/tencentcloud/services/vod/v20180717/vod_client.js +42 -25
- package/tencentcloud/services/vod/v20180717/vod_models.d.ts +1594 -653
- package/tencentcloud/services/waf/v20180125/waf_models.d.ts +6 -2
- package/tencentcloud/services/wedata/v20210820/wedata_client.d.ts +3 -1
- package/tencentcloud/services/wedata/v20210820/wedata_client.js +3 -1
|
@@ -14,7 +14,7 @@ export declare class Client extends AbstractClient {
|
|
|
14
14
|
/**
|
|
15
15
|
* 查询实例详情
|
|
16
16
|
*/
|
|
17
|
-
DescribeClusterDetail(req
|
|
17
|
+
DescribeClusterDetail(req: DescribeClusterDetailRequest, cb?: (error: string, rep: DescribeClusterDetailResponse) => void): Promise<DescribeClusterDetailResponse>;
|
|
18
18
|
/**
|
|
19
19
|
* 查看数据库/列表
|
|
20
20
|
|
|
@@ -273,7 +273,12 @@ export interface DescribeDatabasesRequest {
|
|
|
273
273
|
/**
|
|
274
274
|
* DescribeClusterDetail请求参数结构体
|
|
275
275
|
*/
|
|
276
|
-
export
|
|
276
|
+
export interface DescribeClusterDetailRequest {
|
|
277
|
+
/**
|
|
278
|
+
* <p>实例ID</p>
|
|
279
|
+
*/
|
|
280
|
+
ClusterID?: string;
|
|
281
|
+
}
|
|
277
282
|
/**
|
|
278
283
|
* DescribeClusterDetail返回参数结构体
|
|
279
284
|
*/
|
|
@@ -4290,6 +4290,10 @@ export interface CreateClusterRequest {
|
|
|
4290
4290
|
* <p>服务ui地址</p><p>枚举值:</p><ul><li>0: 服务ui地址,只返回1条服务ui地址</li><li>1: 服务ui地址,如果服务含有多个ui地址将全部返回,例如impala的Impalad、StateStore、Catalogd</li></ul><p>默认值:0</p>
|
|
4291
4291
|
*/
|
|
4292
4292
|
WebUiVersion?: number;
|
|
4293
|
+
/**
|
|
4294
|
+
* <p>系统盘是否加密</p>
|
|
4295
|
+
*/
|
|
4296
|
+
EnableCbsSysEncryptFlag?: boolean;
|
|
4293
4297
|
}
|
|
4294
4298
|
/**
|
|
4295
4299
|
* CreateSLInstance返回参数结构体
|
|
@@ -4909,6 +4913,10 @@ export interface CreateInstanceRequest {
|
|
|
4909
4913
|
* <p>服务ui地址</p><p>枚举值:</p><ul><li>0: 服务ui地址,只返回1条服务ui地址</li><li>1: 服务ui地址,如果服务含有多个ui地址将全部返回,例如impala的Impalad、StateStore、Catalogd</li></ul><p>默认值:0</p>
|
|
4910
4914
|
*/
|
|
4911
4915
|
WebUiVersion?: number;
|
|
4916
|
+
/**
|
|
4917
|
+
* <p>是否开启集群维度cbs系统盘加密,0关闭1开启</p>
|
|
4918
|
+
*/
|
|
4919
|
+
CbsSysEncrypt?: number;
|
|
4912
4920
|
}
|
|
4913
4921
|
/**
|
|
4914
4922
|
* 动态生成的变更详情条目
|
|
@@ -4288,28 +4288,25 @@ export interface BatchOrganizationRegistrationTasksDetails {
|
|
|
4288
4288
|
*/
|
|
4289
4289
|
export interface RecipientComponentInfo {
|
|
4290
4290
|
/**
|
|
4291
|
-
*
|
|
4291
|
+
* <p>签署方经办人在合同流程中的参与方ID,与控件绑定,是控件的归属方</p>
|
|
4292
4292
|
*/
|
|
4293
4293
|
RecipientId?: string;
|
|
4294
4294
|
/**
|
|
4295
|
-
*
|
|
4296
|
-
<ul>
|
|
4297
|
-
<li>**空值** : 此参与方没有填写控件</li>
|
|
4298
|
-
<li>**0**: 未填写, 表示此参与方还没有填写合同的填写控件</li>
|
|
4299
|
-
<li>**1**: 已填写, 表示此参与方已经填写所有的填写控件</li></ul>
|
|
4300
|
-
|
|
4295
|
+
* <p>参与方填写状态</p><ul><li>**空值** : 此参与方没有填写控件</li><li>**0**: 未填写, 表示此参与方还没有填写合同的填写控件</li><li>**1**: 已填写, 表示此参与方已经填写所有的填写控件</li></ul>
|
|
4301
4296
|
*/
|
|
4302
4297
|
RecipientFillStatus?: string;
|
|
4303
4298
|
/**
|
|
4304
|
-
*
|
|
4305
|
-
<ul><li>true-发起方</li>
|
|
4306
|
-
<li>false-参与方</li></ul>
|
|
4299
|
+
* <p>是否为发起方</p><ul><li>true-发起方</li><li>false-参与方</li></ul>
|
|
4307
4300
|
*/
|
|
4308
4301
|
IsPromoter?: boolean;
|
|
4309
4302
|
/**
|
|
4310
|
-
*
|
|
4303
|
+
* <p>该参与方填写控件信息列表</p>
|
|
4311
4304
|
*/
|
|
4312
4305
|
Components?: Array<FilledComponent>;
|
|
4306
|
+
/**
|
|
4307
|
+
* <p>该参与方签批控件信息</p>
|
|
4308
|
+
*/
|
|
4309
|
+
SignComponents?: Array<FilledComponent>;
|
|
4313
4310
|
}
|
|
4314
4311
|
/**
|
|
4315
4312
|
* ExportContractReviewResult返回参数结构体
|
|
@@ -10546,85 +10543,74 @@ export interface CreateBatchCancelFlowUrlRequest {
|
|
|
10546
10543
|
*/
|
|
10547
10544
|
export interface CreateMultiFlowSignQRCodeRequest {
|
|
10548
10545
|
/**
|
|
10549
|
-
*
|
|
10550
|
-
注: `在调用此接口时,请确保指定的员工已获得所需的接口调用权限,并具备接口传入的相应资源的数据权限。`
|
|
10546
|
+
* <p>执行本接口操作的员工信息。<br>注: <code>在调用此接口时,请确保指定的员工已获得所需的接口调用权限,并具备接口传入的相应资源的数据权限。</code></p>
|
|
10551
10547
|
*/
|
|
10552
10548
|
Operator: UserInfo;
|
|
10553
10549
|
/**
|
|
10554
|
-
*
|
|
10555
|
-
可登录腾讯电子签控制台,在 "模板"->"模板中心"->"列表展示设置"选中模板 ID 中查看某个模板的TemplateId(在页面中展示为模板ID)。
|
|
10550
|
+
* <p>合同模板ID,为32位字符串。<br>可登录腾讯电子签控制台,在 "模板"->"模板中心"->"列表展示设置"选中模板 ID 中查看某个模板的TemplateId(在页面中展示为模板ID)。</p>
|
|
10556
10551
|
*/
|
|
10557
10552
|
TemplateId: string;
|
|
10558
10553
|
/**
|
|
10559
|
-
*
|
|
10560
|
-
该名称还将用于合同签署完成后的下载文件名。
|
|
10554
|
+
* <p>合同流程的名称(可自定义此名称),长度不能超过200,只能由中文、字母、数字和下划线组成。<br>该名称还将用于合同签署完成后的下载文件名。</p>
|
|
10561
10555
|
*/
|
|
10562
10556
|
FlowName: string;
|
|
10563
10557
|
/**
|
|
10564
|
-
*
|
|
10565
|
-
一旦发起流程数超越该限制,该二维码将自动失效。
|
|
10558
|
+
* <p>通过此二维码可发起的流程最大限额,如未明确指定,默认为5份。<br>一旦发起流程数超越该限制,该二维码将自动失效。</p>
|
|
10566
10559
|
*/
|
|
10567
10560
|
MaxFlowNum?: number;
|
|
10568
10561
|
/**
|
|
10569
|
-
*
|
|
10570
|
-
一旦超过二维码的有效期限,该二维码将自动失效。
|
|
10562
|
+
* <p>二维码的有效期限,默认为7天,最高设定不得超过90天。<br>一旦超过二维码的有效期限,该二维码将自动失效。</p>
|
|
10571
10563
|
* @deprecated
|
|
10572
10564
|
*/
|
|
10573
10565
|
QrEffectiveDay?: number;
|
|
10574
10566
|
/**
|
|
10575
|
-
*
|
|
10576
|
-
若在签署截止日期前未完成签署,合同状态将变更为已过期,从而导致合同无效。
|
|
10577
|
-
最长设定期限不得超过30天。
|
|
10567
|
+
* <p>合同流程的签署有效期限,若未设定签署截止日期,则默认为自合同流程创建起的7天内截止。<br>若在签署截止日期前未完成签署,合同状态将变更为已过期,从而导致合同无效。<br>最长设定期限不得超过30天。</p>
|
|
10578
10568
|
*/
|
|
10579
10569
|
FlowEffectiveDay?: number;
|
|
10580
10570
|
/**
|
|
10581
|
-
*
|
|
10582
|
-
|
|
10571
|
+
* <p>在短信通知、填写、签署流程中,若标题、按钮、合同详情等地方存在“合同”字样时,可根据此配置指定文案,可选文案如下:<br> <ul><li> <b>0</b> :合同(默认值)</li> <li> <b>1</b> :文件</li> <li> <b>2</b> :协议</li><li> <b>3</b> :文书</li></ul></p><p>效果如下:<br><img src="https://qcloudimg.tencent-cloud.cn/raw/e4a2c4d638717cc901d3dbd5137c9bbc.png" alt="FlowDisplayType"></p><p>枚举值:</p><ul><li>0: 合同</li><li>1: 文件</li><li>2: 协议</li><li>3: 文书</li></ul><p>默认值:0</p>
|
|
10572
|
+
*/
|
|
10573
|
+
FlowDisplayType?: number;
|
|
10574
|
+
/**
|
|
10575
|
+
* <p>指定签署人信息。<br>在指定签署人后,仅允许特定签署人通过扫描二维码进行签署。</p>
|
|
10583
10576
|
*/
|
|
10584
10577
|
Restrictions?: Array<ApproverRestriction>;
|
|
10585
10578
|
/**
|
|
10586
|
-
*
|
|
10587
|
-
在合同状态变更的回调信息等场景中,该字段的信息将原封不动地透传给贵方。
|
|
10588
|
-
回调的相关说明可参考开发者中心的<a href="https://qian.tencent.com/developers/company/callback_types_v2" target="_blank">回调通知</a>模块。
|
|
10579
|
+
* <p>调用方自定义的个性化字段(可自定义此字段的值),并以base64方式编码,支持的最大数据大小为 20480长度。<br>在合同状态变更的回调信息等场景中,该字段的信息将原封不动地透传给贵方。<br>回调的相关说明可参考开发者中心的<a href="https://qian.tencent.com/developers/company/callback_types_v2" target="_blank">回调通知</a>模块。</p>
|
|
10589
10580
|
*/
|
|
10590
10581
|
UserData?: string;
|
|
10591
10582
|
/**
|
|
10592
|
-
*
|
|
10593
|
-
<br/> 通过一码多扫二维码发起的合同,回调消息可参考文档 https://qian.tencent.com/developers/company/callback_types_contracts_sign
|
|
10594
|
-
<br/> 用户通过签署二维码发起合同时,因企业额度不足导致失败 会触发签署二维码相关回调,具体参考文档 https://qian.tencent.com/developers/company/callback_types_commons#%E7%AD%BE%E7%BD%B2%E4%BA%8C%E7%BB%B4%E7%A0%81%E7%9B%B8%E5%85%B3%E5%9B%9E%E8%B0%83
|
|
10595
|
-
|
|
10583
|
+
* <p>已废弃,回调配置统一使用企业应用管理-应用集成-企业版应用中的配置<br><br> 通过一码多扫二维码发起的合同,回调消息可参考文档 https://qian.tencent.com/developers/company/callback_types_contracts_sign<br><br> 用户通过签署二维码发起合同时,因企业额度不足导致失败 会触发签署二维码相关回调,具体参考文档 https://qian.tencent.com/developers/company/callback_types_commons#%E7%AD%BE%E7%BD%B2%E4%BA%8C%E7%BB%B4%E7%A0%81%E7%9B%B8%E5%85%B3%E5%9B%9E%E8%B0%83</p>
|
|
10596
10584
|
* @deprecated
|
|
10597
10585
|
*/
|
|
10598
10586
|
CallbackUrl?: string;
|
|
10599
10587
|
/**
|
|
10600
|
-
*
|
|
10601
|
-
在集团企业代理子企业操作的场景中,需设置此参数。在此情境下,ProxyOrganizationId(子企业的组织ID)为必填项。
|
|
10588
|
+
* <p>代理企业和员工的信息。<br>在集团企业代理子企业操作的场景中,需设置此参数。在此情境下,ProxyOrganizationId(子企业的组织ID)为必填项。</p>
|
|
10602
10589
|
*/
|
|
10603
10590
|
Agent?: Agent;
|
|
10604
10591
|
/**
|
|
10605
|
-
*
|
|
10592
|
+
* <p>限制二维码用户条件(已弃用)</p>
|
|
10606
10593
|
* @deprecated
|
|
10607
10594
|
*/
|
|
10608
10595
|
ApproverRestrictions?: ApproverRestriction;
|
|
10609
10596
|
/**
|
|
10610
|
-
*
|
|
10597
|
+
* <p>指定签署方在使用个人印章签署控件(SIGN_SIGNATURE) 时可使用的签署方式:自由书写、正楷临摹、系统签名、个人印章。</p>
|
|
10611
10598
|
*/
|
|
10612
10599
|
ApproverComponentLimitTypes?: Array<ApproverComponentLimitType>;
|
|
10613
10600
|
/**
|
|
10614
|
-
*
|
|
10601
|
+
* <p>禁止个人用户重复签署,默认不禁止,即同一用户可多次扫码签署多份合同。若要求同一用户仅能扫码签署一份合同,请传入true。</p>
|
|
10615
10602
|
*/
|
|
10616
10603
|
ForbidPersonalMultipleSign?: boolean;
|
|
10617
10604
|
/**
|
|
10618
|
-
*
|
|
10619
|
-
例如,通过参数FlowName设定的扫码发起合同名称为“员工入职合同”,当扫码人张三(手机号18800009527)扫码签署时,合同名称将自动生成为“员工入职合同-张三-9527”。
|
|
10605
|
+
* <p>合同流程名称是否应包含扫码签署人的信息,且遵循特定格式(flowname-姓名-手机号后四位)。<br>例如,通过参数FlowName设定的扫码发起合同名称为“员工入职合同”,当扫码人张三(手机号18800009527)扫码签署时,合同名称将自动生成为“员工入职合同-张三-9527”。</p>
|
|
10620
10606
|
*/
|
|
10621
10607
|
FlowNameAppendScannerInfo?: boolean;
|
|
10622
10608
|
/**
|
|
10623
|
-
*
|
|
10609
|
+
* <p>签署二维码的名称(可自定义此名称),长度不能超过200,只能由中文、字母、数字和下划线组成,会在生成的二维码图片上展示,若为空,则使用FlowName</p>
|
|
10624
10610
|
*/
|
|
10625
10611
|
QrCodeName?: string;
|
|
10626
10612
|
/**
|
|
10627
|
-
*
|
|
10613
|
+
* <p>签署二维码截止时间,格式为Unix标准时间戳(秒),如果未设置签署截止时间,则默认为签署二维码创建后的7天时截止,最长可设置为签署二维码创建后的365天时截止。</p>
|
|
10628
10614
|
*/
|
|
10629
10615
|
QrCodeExpiredOn?: number;
|
|
10630
10616
|
}
|
|
@@ -10974,11 +10960,11 @@ export interface CreatePrepareFlowGroupResponse {
|
|
|
10974
10960
|
*/
|
|
10975
10961
|
export interface CreateMultiFlowSignQRCodeResponse {
|
|
10976
10962
|
/**
|
|
10977
|
-
*
|
|
10963
|
+
* <p>一码多签签署码的基本信息,用户可扫描该二维码进行签署操作。</p>
|
|
10978
10964
|
*/
|
|
10979
10965
|
QrCode?: SignQrCode;
|
|
10980
10966
|
/**
|
|
10981
|
-
*
|
|
10967
|
+
* <p>一码多签签署码的链接信息,适用于客户系统整合二维码功能。通过链接,用户可直接访问电子签名小程序并签署合同。</p>
|
|
10982
10968
|
*/
|
|
10983
10969
|
SignUrls?: SignUrl;
|
|
10984
10970
|
/**
|
|
@@ -5188,77 +5188,71 @@ export interface RegistrationOrganizationInfo {
|
|
|
5188
5188
|
*/
|
|
5189
5189
|
export interface ChannelCreateMultiFlowSignQRCodeRequest {
|
|
5190
5190
|
/**
|
|
5191
|
-
*
|
|
5192
|
-
|
|
5193
|
-
此接口下面信息必填。
|
|
5194
|
-
<ul>
|
|
5195
|
-
<li>渠道应用标识: Agent.AppId</li>
|
|
5196
|
-
<li>第三方平台子客企业标识: Agent.ProxyOrganizationOpenId</li>
|
|
5197
|
-
<li>第三方平台子客企业中的员工标识: Agent. ProxyOperator.OpenId</li>
|
|
5198
|
-
</ul>
|
|
5199
|
-
第三方平台子客企业和员工必须已经经过实名认证
|
|
5191
|
+
* <p>关于渠道应用的相关信息,包括渠道应用标识、第三方平台子客企业标识及第三方平台子客企业中的员工标识等内容,您可以参阅开发者中心所提供的 Agent 结构体以获取详细定义。</p><p>此接口下面信息必填。</p><ul><li>渠道应用标识: Agent.AppId</li><li>第三方平台子客企业标识: Agent.ProxyOrganizationOpenId</li><li>第三方平台子客企业中的员工标识: Agent. ProxyOperator.OpenId</li></ul>第三方平台子客企业和员工必须已经经过实名认证
|
|
5200
5192
|
*/
|
|
5201
5193
|
Agent: Agent;
|
|
5202
5194
|
/**
|
|
5203
|
-
*
|
|
5195
|
+
* <p>合同模板ID,为32位字符串。</p>
|
|
5204
5196
|
*/
|
|
5205
5197
|
TemplateId: string;
|
|
5206
5198
|
/**
|
|
5207
|
-
*
|
|
5199
|
+
* <p>合同流程的名称(可自定义此名称),长度不能超过200,只能由中文、字母、数字和下划线组成。 该名称还将用于合同签署完成后的下载文件名。</p>
|
|
5208
5200
|
*/
|
|
5209
5201
|
FlowName: string;
|
|
5210
5202
|
/**
|
|
5211
|
-
*
|
|
5203
|
+
* <p>通过此二维码可发起的流程最大限额,如未明确指定,默认为5份。 一旦发起流程数超越该限制,该二维码将自动失效。</p>
|
|
5212
5204
|
*/
|
|
5213
5205
|
MaxFlowNum?: number;
|
|
5214
5206
|
/**
|
|
5215
|
-
*
|
|
5207
|
+
* <p>合同流程的签署有效期限,若未设定签署截止日期,则默认为自合同流程创建起的7天内截止。 若在签署截止日期前未完成签署,合同状态将变更为已过期,从而导致合同无效。 最长设定期限不得超过30天。</p>
|
|
5216
5208
|
*/
|
|
5217
5209
|
FlowEffectiveDay?: number;
|
|
5218
5210
|
/**
|
|
5219
|
-
*
|
|
5211
|
+
* <p>在短信通知、填写、签署流程中,若标题、按钮、合同详情等地方存在“合同”字样时,可根据此配置指定文案,可选文案如下:<br> <ul><li> <b>0</b> :合同(默认值)</li> <li> <b>1</b> :文件</li> <li> <b>2</b> :协议</li><li> <b>3</b> :文书</li></ul></p><p>效果如下:<br><img src="https://qcloudimg.tencent-cloud.cn/raw/e4a2c4d638717cc901d3dbd5137c9bbc.png" alt="FlowDisplayType"></p><p>枚举值:</p><ul><li>0: 合同</li><li>1: 文件</li><li>2: 协议</li><li>3: 文书</li></ul><p>默认值:0</p>
|
|
5212
|
+
*/
|
|
5213
|
+
FlowDisplayType?: number;
|
|
5214
|
+
/**
|
|
5215
|
+
* <p>二维码的有效期限,默认为7天,最高设定不得超过90天。 一旦超过二维码的有效期限,该二维码将自动失效。</p>
|
|
5220
5216
|
* @deprecated
|
|
5221
5217
|
*/
|
|
5222
5218
|
QrEffectiveDay?: number;
|
|
5223
5219
|
/**
|
|
5224
|
-
*
|
|
5220
|
+
* <p>指定签署人信息。 在指定签署人后,仅允许特定签署人通过扫描二维码进行签署。</p>
|
|
5225
5221
|
*/
|
|
5226
5222
|
Restrictions?: Array<ApproverRestriction>;
|
|
5227
5223
|
/**
|
|
5228
|
-
*
|
|
5224
|
+
* <p>指定签署方经办人控件类型是个人印章签署控件(SIGN_SIGNATURE) 时,可选的签名方式。</p>
|
|
5229
5225
|
*/
|
|
5230
5226
|
ApproverComponentLimitTypes?: Array<ApproverComponentLimitType>;
|
|
5231
5227
|
/**
|
|
5232
|
-
*
|
|
5233
|
-
<br/> 通过一码多扫二维码发起的合同,回调消息可参考文档 https://qian.tencent.com/developers/partner/callback_types_contracts_sign
|
|
5234
|
-
<br/> 用户通过签署二维码发起合同时,因企业额度不足导致失败 会触发签署二维码相关回调,具体参考文档 https://qian.tencent.com/developers/partner/callback_types_commons#%E7%AD%BE%E7%BD%B2%E4%BA%8C%E7%BB%B4%E7%A0%81%E7%9B%B8%E5%85%B3%E5%9B%9E%E8%B0%83
|
|
5228
|
+
* <p>已废弃,回调配置统一使用企业应用管理-应用集成-第三方应用中的配置<br><br> 通过一码多扫二维码发起的合同,回调消息可参考文档 https://qian.tencent.com/developers/partner/callback_types_contracts_sign<br><br> 用户通过签署二维码发起合同时,因企业额度不足导致失败 会触发签署二维码相关回调,具体参考文档 https://qian.tencent.com/developers/partner/callback_types_commons#%E7%AD%BE%E7%BD%B2%E4%BA%8C%E7%BB%B4%E7%A0%81%E7%9B%B8%E5%85%B3%E5%9B%9E%E8%B0%83</p>
|
|
5235
5229
|
* @deprecated
|
|
5236
5230
|
*/
|
|
5237
5231
|
CallbackUrl?: string;
|
|
5238
5232
|
/**
|
|
5239
|
-
*
|
|
5233
|
+
* <p>限制二维码用户条件(已弃用)</p>
|
|
5240
5234
|
* @deprecated
|
|
5241
5235
|
*/
|
|
5242
5236
|
ApproverRestrictions?: ApproverRestriction;
|
|
5243
5237
|
/**
|
|
5244
|
-
*
|
|
5238
|
+
* <p>暂未开放</p>
|
|
5245
5239
|
* @deprecated
|
|
5246
5240
|
*/
|
|
5247
5241
|
Operator?: UserInfo;
|
|
5248
5242
|
/**
|
|
5249
|
-
*
|
|
5243
|
+
* <p>禁止个人用户重复签署,默认不禁止,即同一用户可多次扫码签署多份合同。若要求同一用户仅能扫码签署一份合同,请传入true。</p>
|
|
5250
5244
|
*/
|
|
5251
5245
|
ForbidPersonalMultipleSign?: boolean;
|
|
5252
5246
|
/**
|
|
5253
|
-
*
|
|
5247
|
+
* <p>合同流程名称是否应包含扫码签署人的信息,且遵循特定格式(flowname-姓名-手机号后四位)。 例如,通过参数FlowName设定的扫码发起合同名称为“员工入职合同”,当扫码人张三(手机号18800009527)扫码签署时,合同名称将自动生成为“员工入职合同-张三-9527”。</p>
|
|
5254
5248
|
*/
|
|
5255
5249
|
FlowNameAppendScannerInfo?: boolean;
|
|
5256
5250
|
/**
|
|
5257
|
-
*
|
|
5251
|
+
* <p>签署二维码的名称(可自定义此名称),长度不能超过200,只能由中文、字母、数字和下划线组成,会在生成的二维码图片上展示,若为空,则使用FlowName</p>
|
|
5258
5252
|
*/
|
|
5259
5253
|
QrCodeName?: string;
|
|
5260
5254
|
/**
|
|
5261
|
-
*
|
|
5255
|
+
* <p>签署二维码截止时间,格式为Unix标准时间戳(秒),如果未设置签署截止时间,则默认为签署二维码创建后的7天时截止,最长可设置为签署二维码创建后的365天时截止。</p>
|
|
5262
5256
|
*/
|
|
5263
5257
|
QrCodeExpiredOn?: number;
|
|
5264
5258
|
}
|
|
@@ -7445,11 +7439,11 @@ export interface ChannelCreateFlowGroupByFilesResponse {
|
|
|
7445
7439
|
*/
|
|
7446
7440
|
export interface ChannelCreateMultiFlowSignQRCodeResponse {
|
|
7447
7441
|
/**
|
|
7448
|
-
*
|
|
7442
|
+
* <p>一码多签签署码的基本信息,用户可扫描该二维码进行签署操作。</p>
|
|
7449
7443
|
*/
|
|
7450
7444
|
QrCode?: SignQrCode;
|
|
7451
7445
|
/**
|
|
7452
|
-
*
|
|
7446
|
+
* <p>一码多签签署码链接信息,适用于客户系统整合二维码功能。通过链接,用户可直接访问电子签名小程序并签署合同。</p>
|
|
7453
7447
|
*/
|
|
7454
7448
|
SignUrls?: SignUrl;
|
|
7455
7449
|
/**
|
|
@@ -7963,7 +7957,7 @@ export interface GetDownloadFlowUrlRequest {
|
|
|
7963
7957
|
*/
|
|
7964
7958
|
export interface ChannelCreateEmbedWebUrlResponse {
|
|
7965
7959
|
/**
|
|
7966
|
-
*
|
|
7960
|
+
* <p>嵌入的web链接,5分钟有效</p>
|
|
7967
7961
|
*/
|
|
7968
7962
|
WebUrl?: string;
|
|
7969
7963
|
/**
|
|
@@ -9482,74 +9476,33 @@ export interface OrganizationInfo {
|
|
|
9482
9476
|
*/
|
|
9483
9477
|
export interface ChannelCreateEmbedWebUrlRequest {
|
|
9484
9478
|
/**
|
|
9485
|
-
*
|
|
9486
|
-
|
|
9487
|
-
此接口下面信息必填。
|
|
9488
|
-
<ul>
|
|
9489
|
-
<li>渠道应用标识: Agent.AppId</li>
|
|
9490
|
-
<li>第三方平台子客企业标识: Agent.ProxyOrganizationOpenId</li>
|
|
9491
|
-
<li>第三方平台子客企业中的员工标识: Agent. ProxyOperator.OpenId</li>
|
|
9492
|
-
</ul>
|
|
9493
|
-
第三方平台子客企业和员工必须已经经过实名认证
|
|
9479
|
+
* <p>关于渠道应用的相关信息,包括渠道应用标识、第三方平台子客企业标识及第三方平台子客企业中的员工标识等内容,您可以参阅开发者中心所提供的 Agent 结构体以获取详细定义。</p><p>此接口下面信息必填。</p><ul><li>渠道应用标识: Agent.AppId</li><li>第三方平台子客企业标识: Agent.ProxyOrganizationOpenId</li><li>第三方平台子客企业中的员工标识: Agent. ProxyOperator.OpenId</li></ul>第三方平台子客企业和员工必须已经经过实名认证
|
|
9494
9480
|
*/
|
|
9495
9481
|
Agent: Agent;
|
|
9496
9482
|
/**
|
|
9497
|
-
*
|
|
9498
|
-
|
|
9499
|
-
<ul>
|
|
9500
|
-
<li>CREATE_SEAL: 生成创建印章的嵌入页面</li>
|
|
9501
|
-
<li>CREATE_TEMPLATE:生成创建模板的嵌入页面</li>
|
|
9502
|
-
<li>MODIFY_TEMPLATE:生成修改模板的嵌入页面</li>
|
|
9503
|
-
<li>PREVIEW_TEMPLATE:生成预览模板的嵌入页面</li>
|
|
9504
|
-
<li>PREVIEW_FLOW:生成预览合同文档的嵌入页面(H5链接,支持移动端的浏览器中打开)</li>
|
|
9505
|
-
<li>PREVIEW_FLOW_DETAIL:生成预览合同详情的嵌入页面(仅支持PC的浏览器中打开)</li>
|
|
9506
|
-
<li>PREVIEW_SEAL_LIST:生成预览印章列表的嵌入页面</li>
|
|
9507
|
-
<li>PREVIEW_SEAL_DETAIL:生成预览印章详情的嵌入页面</li>
|
|
9508
|
-
<li>EXTEND_SERVICE:生成扩展服务的嵌入页面</li>
|
|
9509
|
-
</ul>
|
|
9483
|
+
* <p>要生成WEB嵌入界面的类型, 可以选择的值如下: </p><ul><li>CREATE_SEAL: 生成创建印章的嵌入页面</li><li>CREATE_TEMPLATE:生成创建模板的嵌入页面</li><li>MODIFY_TEMPLATE:生成修改模板的嵌入页面</li><li>PREVIEW_TEMPLATE:生成预览模板的嵌入页面</li><li>PREVIEW_FLOW:生成预览合同文档的嵌入页面(H5链接,支持移动端的浏览器中打开)</li><li>PREVIEW_FLOW_DETAIL:生成预览合同详情的嵌入页面(仅支持PC的浏览器中打开)</li><li>PREVIEW_SEAL_LIST:生成预览印章列表的嵌入页面</li><li>PREVIEW_SEAL_DETAIL:生成预览印章详情的嵌入页面</li><li>EXTEND_SERVICE:生成扩展服务的嵌入页面</li></ul>
|
|
9510
9484
|
*/
|
|
9511
9485
|
EmbedType: string;
|
|
9512
9486
|
/**
|
|
9513
|
-
* WEB嵌入的业务资源ID
|
|
9514
|
-
|
|
9515
|
-
当EmbedType取值
|
|
9516
|
-
<ul>
|
|
9517
|
-
<li>为MODIFY_TEMPLATE,PREVIEW_TEMPLATE必填,取值为模板id</li>
|
|
9518
|
-
<li>为CREATE_TEMPLATE,非必填,取值为资源id。*资源Id获取可使用接口[上传文件](https://qian.tencent.com/developers/partnerApis/files/UploadFiles)*</li>
|
|
9519
|
-
<li>为PREVIEW_FLOW,PREVIEW_FLOW_DETAIL必填,取值为合同id</li>
|
|
9520
|
-
<li>为PREVIEW_SEAL_DETAIL必填,取值为印章id</li>
|
|
9521
|
-
</ul>
|
|
9522
|
-
|
|
9523
|
-
|
|
9524
|
-
注意:
|
|
9525
|
-
1. CREATE_TEMPLATE中的BusinessId仅支持PDF文件类型, 如果您的文件不是PDF, 请使用接口[创建文件转换任务](https://qian.tencent.com/developers/partnerApis/files/ChannelCreateConvertTaskApi) 和[查询转换任务状态](https://qian.tencent.com/developers/partnerApis/files/ChannelGetTaskResultApi) 来进行转换成PDF资源。
|
|
9487
|
+
* <p>WEB嵌入的业务资源ID</p><p>当EmbedType取值</p><ul><li>为MODIFY_TEMPLATE,PREVIEW_TEMPLATE必填,取值为模板id</li><li>为CREATE_TEMPLATE,非必填,取值为资源id。*资源Id获取可使用接口[上传文件](https://qian.tencent.com/developers/partnerApis/files/UploadFiles)*</li><li>为PREVIEW_FLOW,PREVIEW_FLOW_DETAIL必填,取值为合同id</li><li>为PREVIEW_SEAL_DETAIL必填,取值为印章id</li></ul><p>注意:</p><ol><li>CREATE_TEMPLATE中的BusinessId仅支持PDF文件类型, 如果您的文件不是PDF, 请使用接口<a href="https://qian.tencent.com/developers/partnerApis/files/ChannelCreateConvertTaskApi">创建文件转换任务</a> 和<a href="https://qian.tencent.com/developers/partnerApis/files/ChannelGetTaskResultApi">查询转换任务状态</a> 来进行转换成PDF资源。</li></ol>
|
|
9526
9488
|
*/
|
|
9527
9489
|
BusinessId?: string;
|
|
9528
9490
|
/**
|
|
9529
|
-
*
|
|
9491
|
+
* <p>是否隐藏控件,只有预览模板时生效,目前字段已废弃,请使用<a href="https://qian.tencent.com/developers/partnerApis/dataTypes#embedurloption">嵌入式页面url个性化参数Option</a> 的ShowTemplateComponent来指定是否展示or隐藏控件</p>
|
|
9492
|
+
* @deprecated
|
|
9530
9493
|
*/
|
|
9531
9494
|
HiddenComponents?: boolean;
|
|
9532
9495
|
/**
|
|
9533
|
-
*
|
|
9496
|
+
* <p>渠道操作者信息</p>
|
|
9534
9497
|
* @deprecated
|
|
9535
9498
|
*/
|
|
9536
9499
|
Operator?: UserInfo;
|
|
9537
9500
|
/**
|
|
9538
|
-
*
|
|
9539
|
-
<ul>
|
|
9540
|
-
<li>目前仅支持EmbedType=CREATE_TEMPLATE时传入</li>
|
|
9541
|
-
<li>指定后,创建,编辑,删除模板时,回调都会携带该userData</li>
|
|
9542
|
-
<li>支持的格式:json字符串的BASE64编码字符串</li>
|
|
9543
|
-
<li>示例:<ul>
|
|
9544
|
-
<li>json字符串:{"ComeFrom":"xxx"},BASE64编码:eyJDb21lRnJvbSI6Inh4eCJ9</li>
|
|
9545
|
-
<li>eyJDb21lRnJvbSI6Inh4eCJ9,为符合要求的userData数据格式</li>
|
|
9546
|
-
</ul>
|
|
9547
|
-
</li>
|
|
9548
|
-
</ul>
|
|
9501
|
+
* <p>用户自定义参数</p><ul><li>目前仅支持EmbedType=CREATE_TEMPLATE时传入</li><li>指定后,创建,编辑,删除模板时,回调都会携带该userData</li><li>支持的格式:json字符串的BASE64编码字符串</li><li>示例:<ul> <li>json字符串:{"ComeFrom":"xxx"},BASE64编码:eyJDb21lRnJvbSI6Inh4eCJ9</li> <li>eyJDb21lRnJvbSI6Inh4eCJ9,为符合要求的userData数据格式</li></ul></li></ul>
|
|
9549
9502
|
*/
|
|
9550
9503
|
UserData?: string;
|
|
9551
9504
|
/**
|
|
9552
|
-
*
|
|
9505
|
+
* <p>个性化参数,用于控制页面展示内容</p>
|
|
9553
9506
|
*/
|
|
9554
9507
|
Option?: EmbedUrlOption;
|
|
9555
9508
|
}
|
|
@@ -28,7 +28,7 @@ export declare class Client extends AbstractClient {
|
|
|
28
28
|
*/
|
|
29
29
|
DeleteService(req: DeleteServiceRequest, cb?: (error: string, rep: DeleteServiceResponse) => void): Promise<DeleteServiceResponse>;
|
|
30
30
|
/**
|
|
31
|
-
* 本接口(UpdateServiceConfigs)
|
|
31
|
+
* 本接口(UpdateServiceConfigs)用于更新服务配置。
|
|
32
32
|
*/
|
|
33
33
|
UpdateServiceConfigs(req: UpdateServiceConfigsRequest, cb?: (error: string, rep: UpdateServiceConfigsResponse) => void): Promise<UpdateServiceConfigsResponse>;
|
|
34
34
|
/**
|
|
@@ -58,7 +58,7 @@ class Client extends abstract_client_1.AbstractClient {
|
|
|
58
58
|
return this.request("DeleteService", req, cb);
|
|
59
59
|
}
|
|
60
60
|
/**
|
|
61
|
-
* 本接口(UpdateServiceConfigs)
|
|
61
|
+
* 本接口(UpdateServiceConfigs)用于更新服务配置。
|
|
62
62
|
*/
|
|
63
63
|
async UpdateServiceConfigs(req, cb) {
|
|
64
64
|
return this.request("UpdateServiceConfigs", req, cb);
|
|
@@ -289,11 +289,11 @@ export interface NetworkStatus {
|
|
|
289
289
|
*/
|
|
290
290
|
export interface ComputeInfo {
|
|
291
291
|
/**
|
|
292
|
-
*
|
|
292
|
+
* <p>资源类型及数量</p>
|
|
293
293
|
*/
|
|
294
294
|
ComputeResources?: Array<ComputeResource>;
|
|
295
295
|
/**
|
|
296
|
-
*
|
|
296
|
+
* <p>副本数</p>
|
|
297
297
|
*/
|
|
298
298
|
Replicas?: number;
|
|
299
299
|
}
|
|
@@ -1060,11 +1060,11 @@ export interface DeployInferServiceRequest {
|
|
|
1060
1060
|
*/
|
|
1061
1061
|
export interface DeploymentConfig {
|
|
1062
1062
|
/**
|
|
1063
|
-
*
|
|
1063
|
+
* <p>容器配置</p>
|
|
1064
1064
|
*/
|
|
1065
1065
|
Container?: ContainerInfo;
|
|
1066
1066
|
/**
|
|
1067
|
-
*
|
|
1067
|
+
* <p>容器数量</p>
|
|
1068
1068
|
*/
|
|
1069
1069
|
ContainerCount?: number;
|
|
1070
1070
|
}
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
import { AbstractClient } from "../../../common/abstract_client";
|
|
2
2
|
import { ClientConfig } from "../../../common/interface";
|
|
3
|
-
import { CreatePrivilegeCodeRequest, DescribeDeviceDetailListResponse, DescribeAggrSoftDeviceListRequest, DescribeDeviceHardwareInfoListResponse, DescribeResourceGrantedAccountsRequest, DescribeResourceGrantedAccountGroupsRequest, DescribeDevicesResponse, GrantResourcesByVirtualGroupsRequest, DescribeDirectAccountGroupResourcesResponse, DescribeDeviceVirtualGroupsResponse, CreateBusinessResourceResponse, DescribeAggrSoftCategorySoftListRequest, CreateDeviceVirtualGroupRequest, CreateDeviceTaskRequest, DescribeSoftCensusListByDeviceRequest, DescribeResourceGrantedAccountsResponse, DescribeResourceGrantedAccountGroupsResponse, DescribeResourceGrantedVirtualGroupsResponse, DescribeLocalAccountsRequest, CreateDeviceTaskResponse, GrantResourcesByAccountGroupsRequest, ModifyDeviceTrustStatusResponse, CreateDLPFileDetectionTaskRequest,
|
|
3
|
+
import { CreatePrivilegeCodeRequest, DescribeDeviceDetailListResponse, ModifyBusinessResourceRequest, DescribeAggrSoftDeviceListRequest, DescribeDeviceHardwareInfoListResponse, DescribeResourceGrantedAccountsRequest, DescribeResourceGrantedAccountGroupsRequest, DescribeDevicesResponse, GrantResourcesByVirtualGroupsRequest, DescribeDirectAccountGroupResourcesResponse, DescribeDeviceVirtualGroupsResponse, CreateBusinessResourceResponse, DescribeAggrSoftCategorySoftListRequest, CreateDeviceVirtualGroupRequest, CreateDeviceTaskRequest, DescribeSoftCensusListByDeviceRequest, DescribeResourceGrantedAccountsResponse, DescribeResourceGrantedAccountGroupsResponse, DescribeResourceGrantedVirtualGroupsResponse, DescribeLocalAccountsRequest, CreateDeviceTaskResponse, GrantResourcesByAccountGroupsRequest, ModifyDeviceTrustStatusResponse, CreateDLPFileDetectionTaskRequest, BindBusinessResourceConnectorGroupRequest, ModifyBusinessResourceResponse, CreateBusinessResourceRequest, DescribeDeviceInfoRequest, GrantResourcesByAccountsRequest, DescribeDeviceVirtualGroupsRequest, DescribeDeviceChildGroupsRequest, DescribeDeviceInfoResponse, DescribeDLPEdgeNodesResponse, ExportSoftwareInformationListResponse, DescribeResourceGrantedVirtualGroupsRequest, DescribeBusinessResourcesRequest, DescribeSoftwareInformationRequest, DescribeDLPFileDetectTaskResultResponse, CreateDLPFileDetectTaskResponse, DescribeDLPEdgeNodesRequest, GrantResourcesByAccountsResponse, DescribeBusinessResourcesResponse, DescribeAggrSoftDetailRequest, DescribeDLPEdgeNodeGroupsRequest, DescribeVirtualDevicesResponse, CreateDLPFileDetectTaskRequest, DescribeDLPFileDetectResultRequest, ExportDeviceDownloadTaskRequest, CreateDeviceVirtualGroupResponse, ExportDeviceDownloadTaskResponse, DescribeSoftwareInformationResponse, GrantResourcesByAccountGroupsResponse, ModifyVirtualDeviceGroupsResponse, DescribeLocalAccountsResponse, DescribeAccountGroupsResponse, DescribeSoftCensusListByDeviceResponse, DescribeDLPEdgeNodeGroupsResponse, GrantResourcesByVirtualGroupsResponse, ModifyDeviceTrustStatusRequest, DescribeAggrSoftDeviceListResponse, DescribeRootAccountGroupResponse, DescribeAccountGroupsRequest, DescribeDLPFileDetectTaskResultRequest, DescribeDeviceDetailListRequest, ExportSoftwareInformationListRequest, ModifyVirtualDeviceGroupsRequest, BindBusinessResourceConnectorGroupResponse, DescribeDirectAccountGroupResourcesRequest, DescribeRootAccountGroupRequest, DescribeDevicesRequest, DescribeAggrSoftCategorySoftListResponse, DescribeAggrSoftDetailResponse, CreateDLPFileDetectionTaskResponse, DescribeDeviceChildGroupsResponse, DescribeDLPFileDetectResultResponse, DescribeVirtualDevicesRequest, CreatePrivilegeCodeResponse, DescribeDeviceHardwareInfoListRequest } from "./ioa_models";
|
|
4
4
|
/**
|
|
5
5
|
* ioa client
|
|
6
6
|
* @class
|
|
@@ -79,6 +79,10 @@ export declare class Client extends AbstractClient {
|
|
|
79
79
|
* 查询边缘节点列表,私有化调用path为:capi/DlpOpenApi/DescribeDLPEdgeNodes
|
|
80
80
|
*/
|
|
81
81
|
DescribeDLPEdgeNodes(req: DescribeDLPEdgeNodesRequest, cb?: (error: string, rep: DescribeDLPEdgeNodesResponse) => void): Promise<DescribeDLPEdgeNodesResponse>;
|
|
82
|
+
/**
|
|
83
|
+
* saas版本,创建/修改业务资源后,调用绑定连接器接口,私有化调用path为:capi/GatewayResource/BindBusinessResourceConnectorGroup
|
|
84
|
+
*/
|
|
85
|
+
BindBusinessResourceConnectorGroup(req: BindBusinessResourceConnectorGroupRequest, cb?: (error: string, rep: BindBusinessResourceConnectorGroupResponse) => void): Promise<BindBusinessResourceConnectorGroupResponse>;
|
|
82
86
|
/**
|
|
83
87
|
* 列表账户组直接关联的资源,私有化调用path为:capi/Assets/DescribeDirectAccountGroupResources
|
|
84
88
|
*/
|
|
@@ -123,6 +127,10 @@ export declare class Client extends AbstractClient {
|
|
|
123
127
|
* 获取账号列表,支持分页,模糊搜索,私有化调用path为:/capi/Assets/Account/DescribeLocalAccounts
|
|
124
128
|
*/
|
|
125
129
|
DescribeLocalAccounts(req: DescribeLocalAccountsRequest, cb?: (error: string, rep: DescribeLocalAccountsResponse) => void): Promise<DescribeLocalAccountsResponse>;
|
|
130
|
+
/**
|
|
131
|
+
* 修改业务资源,会对一些必填参数进行校验和参数合法性校验,修改业务资源时,先调用下校验相同业务资源接口,看资源是不是有冲突。修改时也会做校验,但没有返回对应的异常信息,私有化调用path为:capi/GatewayResource/ModifyBusinessResource
|
|
132
|
+
*/
|
|
133
|
+
ModifyBusinessResource(req: ModifyBusinessResourceRequest, cb?: (error: string, rep: ModifyBusinessResourceResponse) => void): Promise<ModifyBusinessResourceResponse>;
|
|
126
134
|
/**
|
|
127
135
|
* 查询边缘节点分组,私有化调用path为:capi/Connectors/DescribeDLPEdgeNodeGroups
|
|
128
136
|
*/
|
|
@@ -135,6 +135,12 @@ class Client extends abstract_client_1.AbstractClient {
|
|
|
135
135
|
async DescribeDLPEdgeNodes(req, cb) {
|
|
136
136
|
return this.request("DescribeDLPEdgeNodes", req, cb);
|
|
137
137
|
}
|
|
138
|
+
/**
|
|
139
|
+
* saas版本,创建/修改业务资源后,调用绑定连接器接口,私有化调用path为:capi/GatewayResource/BindBusinessResourceConnectorGroup
|
|
140
|
+
*/
|
|
141
|
+
async BindBusinessResourceConnectorGroup(req, cb) {
|
|
142
|
+
return this.request("BindBusinessResourceConnectorGroup", req, cb);
|
|
143
|
+
}
|
|
138
144
|
/**
|
|
139
145
|
* 列表账户组直接关联的资源,私有化调用path为:capi/Assets/DescribeDirectAccountGroupResources
|
|
140
146
|
*/
|
|
@@ -201,6 +207,12 @@ class Client extends abstract_client_1.AbstractClient {
|
|
|
201
207
|
async DescribeLocalAccounts(req, cb) {
|
|
202
208
|
return this.request("DescribeLocalAccounts", req, cb);
|
|
203
209
|
}
|
|
210
|
+
/**
|
|
211
|
+
* 修改业务资源,会对一些必填参数进行校验和参数合法性校验,修改业务资源时,先调用下校验相同业务资源接口,看资源是不是有冲突。修改时也会做校验,但没有返回对应的异常信息,私有化调用path为:capi/GatewayResource/ModifyBusinessResource
|
|
212
|
+
*/
|
|
213
|
+
async ModifyBusinessResource(req, cb) {
|
|
214
|
+
return this.request("ModifyBusinessResource", req, cb);
|
|
215
|
+
}
|
|
204
216
|
/**
|
|
205
217
|
* 查询边缘节点分组,私有化调用path为:capi/Connectors/DescribeDLPEdgeNodeGroups
|
|
206
218
|
*/
|