tencentcloud-sdk-python 3.0.1378__py2.py3-none-any.whl → 3.0.1379__py2.py3-none-any.whl
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.
- tencentcloud/__init__.py +1 -1
- tencentcloud/batch/v20170312/batch_client.py +3 -3
- tencentcloud/batch/v20170312/models.py +230 -168
- tencentcloud/cbs/v20170312/cbs_client.py +1 -1
- tencentcloud/cbs/v20170312/models.py +18 -18
- tencentcloud/clb/v20180317/clb_client.py +7 -7
- tencentcloud/clb/v20180317/models.py +51 -41
- tencentcloud/dbbrain/v20210527/dbbrain_client.py +46 -0
- tencentcloud/dbbrain/v20210527/models.py +368 -0
- tencentcloud/dnspod/v20210323/dnspod_client.py +23 -0
- tencentcloud/dnspod/v20210323/models.py +503 -0
- tencentcloud/domain/v20180808/errorcodes.py +3 -0
- tencentcloud/domain/v20180808/models.py +68 -44
- tencentcloud/lkeap/v20240522/lkeap_client.py +1 -1
- tencentcloud/mps/v20190612/models.py +211 -2
- tencentcloud/postgres/v20170312/models.py +12 -4
- tencentcloud/tcb/v20180608/models.py +4 -4
- tencentcloud/tdmq/v20200217/errorcodes.py +27 -0
- tencentcloud/thpc/v20211109/models.py +2 -2
- tencentcloud/thpc/v20220401/models.py +4 -4
- tencentcloud/thpc/v20230321/errorcodes.py +9 -0
- tencentcloud/thpc/v20230321/models.py +79 -0
- tencentcloud/thpc/v20230321/thpc_client.py +23 -0
- tencentcloud/tmt/v20180321/errorcodes.py +3 -0
- tencentcloud/tmt/v20180321/models.py +296 -1
- tencentcloud/tmt/v20180321/tmt_client.py +28 -0
- tencentcloud/vpc/v20170312/models.py +24 -18
- tencentcloud/waf/v20180125/models.py +15 -0
- tencentcloud/wedata/v20210820/errorcodes.py +9 -0
- tencentcloud/wedata/v20210820/models.py +1078 -0
- tencentcloud/wedata/v20210820/wedata_client.py +46 -0
- {tencentcloud_sdk_python-3.0.1378.dist-info → tencentcloud_sdk_python-3.0.1379.dist-info}/METADATA +1 -1
- {tencentcloud_sdk_python-3.0.1378.dist-info → tencentcloud_sdk_python-3.0.1379.dist-info}/RECORD +36 -36
- {tencentcloud_sdk_python-3.0.1378.dist-info → tencentcloud_sdk_python-3.0.1379.dist-info}/LICENSE +0 -0
- {tencentcloud_sdk_python-3.0.1378.dist-info → tencentcloud_sdk_python-3.0.1379.dist-info}/WHEEL +0 -0
- {tencentcloud_sdk_python-3.0.1378.dist-info → tencentcloud_sdk_python-3.0.1379.dist-info}/top_level.txt +0 -0
tencentcloud/__init__.py
CHANGED
@@ -565,7 +565,7 @@ class BatchClient(AbstractClient):
|
|
565
565
|
|
566
566
|
def RetryJobs(self, request):
|
567
567
|
"""用于重试作业中失败的任务实例。
|
568
|
-
|
568
|
+
仅当作业处于“FAILED”状态,支持重试操作。重试操作成功后,作业会按照有向无环图中指定的任务依赖关系,依次重试各个任务中失败的任务实例。任务实例的历史信息将被重置,如同首次运行一样,参与后续的调度和执行。
|
569
569
|
|
570
570
|
:param request: Request instance for RetryJobs.
|
571
571
|
:type request: :class:`tencentcloud.batch.v20170312.models.RetryJobsRequest`
|
@@ -660,7 +660,7 @@ class BatchClient(AbstractClient):
|
|
660
660
|
def TerminateJob(self, request):
|
661
661
|
"""用于终止作业。
|
662
662
|
当作业处于“SUBMITTED”状态时,禁止终止操作;当作业处于“SUCCEED”状态时,终止操作不会生效。
|
663
|
-
终止作业是一个异步过程。整个终止过程的耗时和任务总数成正比。终止的效果相当于所含的所有任务实例进行TerminateTaskInstance操作。具体效果和用法可参考TerminateTaskInstance。
|
663
|
+
终止作业是一个异步过程。整个终止过程的耗时和任务总数成正比。终止的效果相当于所含的所有任务实例进行[TerminateTaskInstance](https://cloud.tencent.com/document/product/599/15908)操作。具体效果和用法可参考[TerminateTaskInstance](https://cloud.tencent.com/document/product/599/15908)。
|
664
664
|
|
665
665
|
:param request: Request instance for TerminateJob.
|
666
666
|
:type request: :class:`tencentcloud.batch.v20170312.models.TerminateJobRequest`
|
@@ -686,7 +686,7 @@ class BatchClient(AbstractClient):
|
|
686
686
|
"""用于终止任务实例。
|
687
687
|
对于状态已经为“SUCCEED”和“FAILED”的任务实例,不做处理。
|
688
688
|
对于状态为“SUBMITTED”、“PENDING”、“RUNNABLE”的任务实例,状态将置为“FAILED”状态。
|
689
|
-
对于状态为“STARTING”、“RUNNING”、“FAILED_INTERRUPTED
|
689
|
+
对于状态为“STARTING”、“RUNNING”、“FAILED_INTERRUPTED”的任务实例,区分两种情况:如果未显示指定计算环境,会先销毁CVM服务器,然后将状态置为“FAILED”,具有一定耗时;如果指定了计算环境EnvId,任务实例状态置为“FAILED”,并重启执行该任务的CVM服务器,具有一定的耗时。
|
690
690
|
对于状态为“FAILED_INTERRUPTED”的任务实例,终止操作实际成功之后,相关资源和配额才会释放。
|
691
691
|
|
692
692
|
:param request: Request instance for TerminateTaskInstance.
|