Skip to content

Commit 899d156

Browse files
author
mikatong
committed
update doc
1 parent fc8ef63 commit 899d156

File tree

2 files changed

+8
-10
lines changed

2 files changed

+8
-10
lines changed

tencentcloud/services/mongodb/resource_tc_mongodb_instance.go

Lines changed: 4 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -109,11 +109,10 @@ func ResourceTencentCloudMongodbInstance() *schema.Resource {
109109
Elem: &schema.Schema{
110110
Type: schema.TypeString,
111111
},
112-
Description: `A list of nodes deployed in multiple availability zones. For more information, please use the API DescribeSpecInfo.
113-
- 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.
114-
- Version 4.2 and above are not supported.
115-
- Read-only disaster recovery instances are not supported.
116-
- Basic network cannot be selected.`,
112+
Description: "If cloud database instances are deployed in multiple availability zones, specify a list of multiple availability zones.\n" +
113+
" - 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" +
114+
" - 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" +
115+
" - 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.",
117116
},
118117
"hidden_zone": {
119118
Type: schema.TypeString,

website/docs/r/mongodb_instance.html.markdown

Lines changed: 4 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -40,11 +40,10 @@ The following arguments are supported:
4040
* `volume` - (Required, Int) Disk size. The minimum value is 25, and unit is GB. Memory and volume must be upgraded or degraded simultaneously.
4141
* `add_node_list` - (Optional, List) Add node attribute list.
4242
* `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.
43-
* `availability_zone_list` - (Optional, List: [`String`]) A list of nodes deployed in multiple availability zones. For more information, please use the API DescribeSpecInfo.
44-
- 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.
45-
- Version 4.2 and above are not supported.
46-
- Read-only disaster recovery instances are not supported.
47-
- Basic network cannot be selected.
43+
* `availability_zone_list` - (Optional, List: [`String`]) If cloud database instances are deployed in multiple availability zones, specify a list of multiple availability zones.
44+
- 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].
45+
- 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.
46+
- 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.
4847
* `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.
4948
* `hidden_zone` - (Optional, String) The availability zone to which the Hidden node belongs. This parameter is required in cross-AZ instance deployment.
5049
* `in_maintenance` - (Optional, Int) Switch time for instance configuration changes.

0 commit comments

Comments
 (0)