From 899d15642d3bdd126aa44b4ba72707fbf2cfae0f Mon Sep 17 00:00:00 2001 From: mikatong Date: Thu, 24 Apr 2025 15:03:25 +0800 Subject: [PATCH] update doc --- .../services/mongodb/resource_tc_mongodb_instance.go | 9 ++++----- website/docs/r/mongodb_instance.html.markdown | 9 ++++----- 2 files changed, 8 insertions(+), 10 deletions(-) diff --git a/tencentcloud/services/mongodb/resource_tc_mongodb_instance.go b/tencentcloud/services/mongodb/resource_tc_mongodb_instance.go index 0b64fa9c0a..48e2ebf88e 100644 --- a/tencentcloud/services/mongodb/resource_tc_mongodb_instance.go +++ b/tencentcloud/services/mongodb/resource_tc_mongodb_instance.go @@ -109,11 +109,10 @@ func ResourceTencentCloudMongodbInstance() *schema.Resource { Elem: &schema.Schema{ Type: schema.TypeString, }, - Description: `A list of nodes deployed in multiple availability zones. For more information, please use the API DescribeSpecInfo. - - Multi-availability zone deployment nodes can only be deployed in 3 different availability zones. It is not supported to deploy most nodes of the cluster in the same availability zone. For example, a 3-node cluster does not support the deployment of 2 nodes in the same zone. - - Version 4.2 and above are not supported. - - Read-only disaster recovery instances are not supported. - - Basic network cannot be selected.`, + Description: "If cloud database instances are deployed in multiple availability zones, specify a list of multiple availability zones.\n" + + " - To deploy an instance with multiple availability zones, the parameter Zone specifies the primary availability zone information of the instance; Availability ZoneList specifies all availability zone information, including the primary availability zone. The input format is as follows: [ap-Guangzhou-2,ap-Guangzhou-3,ap-Guangzhou-4].\n" + + " - You can obtain availability zone information planned in different regions of the cloud database through the interface DescribeSpecInfo, so as to specify effective availability zones.\n" + + " - Multiple availability zone deployment nodes can only be deployed in 3 different availability zones. Deploying most nodes of a cluster in the same availability zone is not supported. For example, a 3-node cluster does not support 2 nodes deployed in the same zone.", }, "hidden_zone": { Type: schema.TypeString, diff --git a/website/docs/r/mongodb_instance.html.markdown b/website/docs/r/mongodb_instance.html.markdown index 7784f84b95..f4e9d193bd 100644 --- a/website/docs/r/mongodb_instance.html.markdown +++ b/website/docs/r/mongodb_instance.html.markdown @@ -40,11 +40,10 @@ The following arguments are supported: * `volume` - (Required, Int) Disk size. The minimum value is 25, and unit is GB. Memory and volume must be upgraded or degraded simultaneously. * `add_node_list` - (Optional, List) Add node attribute list. * `auto_renew_flag` - (Optional, Int) Auto renew flag. Valid values are `0`(NOTIFY_AND_MANUAL_RENEW), `1`(NOTIFY_AND_AUTO_RENEW) and `2`(DISABLE_NOTIFY_AND_MANUAL_RENEW). Default value is `0`. Note: only works for PREPAID instance. Only supports`0` and `1` for creation. -* `availability_zone_list` - (Optional, List: [`String`]) A list of nodes deployed in multiple availability zones. For more information, please use the API DescribeSpecInfo. - - Multi-availability zone deployment nodes can only be deployed in 3 different availability zones. It is not supported to deploy most nodes of the cluster in the same availability zone. For example, a 3-node cluster does not support the deployment of 2 nodes in the same zone. - - Version 4.2 and above are not supported. - - Read-only disaster recovery instances are not supported. - - Basic network cannot be selected. +* `availability_zone_list` - (Optional, List: [`String`]) If cloud database instances are deployed in multiple availability zones, specify a list of multiple availability zones. + - To deploy an instance with multiple availability zones, the parameter Zone specifies the primary availability zone information of the instance; Availability ZoneList specifies all availability zone information, including the primary availability zone. The input format is as follows: [ap-Guangzhou-2,ap-Guangzhou-3,ap-Guangzhou-4]. + - You can obtain availability zone information planned in different regions of the cloud database through the interface DescribeSpecInfo, so as to specify effective availability zones. + - Multiple availability zone deployment nodes can only be deployed in 3 different availability zones. Deploying most nodes of a cluster in the same availability zone is not supported. For example, a 3-node cluster does not support 2 nodes deployed in the same zone. * `charge_type` - (Optional, String, ForceNew) The charge type of instance. Valid values are `PREPAID` and `POSTPAID_BY_HOUR`. Default value is `POSTPAID_BY_HOUR`. Note: TencentCloud International only supports `POSTPAID_BY_HOUR`. Caution that update operation on this field will delete old instances and create new one with new charge type. * `hidden_zone` - (Optional, String) The availability zone to which the Hidden node belongs. This parameter is required in cross-AZ instance deployment. * `in_maintenance` - (Optional, Int) Switch time for instance configuration changes.