docs: fix docs of vpc_v1

docs/data-sources/vpc_route_v2.md

@@ -42,6 +42,12 @@ route whose data will be exported as attributes.
 
 * `type` (Optional) - Route type for filtering.
 
+* `nexthop` (Optional) - Specifies the next hop. If the route type is peering, enter the VPC peering connection ID.
+  Changing this creates a new Route.
+
+* `region` - (Optional) The region in which to obtain the V1 VPC client. A VPC client is needed to retrieve VPCs.
+  If omitted, the region argument of the provider is used.
+
 ## Attribute Reference
 
 All of the argument attributes are also exported as

docs/data-sources/vpc_subnet_ids_v1.md

@@ -33,6 +33,9 @@ The following arguments are supported:
 
 * `vpc_id` (Required) - Specifies the VPC ID used as the query filter.
 
+* `region` - (Optional) The region in which to obtain the V1 VPC client. A VPC client is needed to retrieve VPCs.
+  If omitted, the region argument of the provider is used.
+
 ## Attributes Reference
 
 The following attributes are exported:

docs/data-sources/vpc_subnet_v1.md

@@ -42,6 +42,9 @@ subnet whose data will be exported as attributes.
 
 * `primary_dns` (Optional) - The IP address of DNS server 1 on the specific subnet.
 
+* `region` - (Optional) The region in which to obtain the V1 VPC client. A VPC client is needed to retrieve VPCs.
+  If omitted, the region argument of the provider is used.
+
 * `secondary_dns` (Optional) - The IP address of DNS server 2 on the specific subnet.
 
 * `availability_zone` (Optional) - The availability zone (AZ) to which the subnet should belong.

docs/data-sources/vpc_v1.md

@@ -57,3 +57,7 @@ The following attributes are exported:
 * `shared` - Specifies whether the cross-tenant sharing is supported.
 
 * `region` - See Argument Reference above.
+
+* `routes.destination` - Specifies the destination network segment of a routex.
+
+* `routes.nexthop` - Specifies the next hop of a route.

docs/resources/vpc_route_v2.md

@@ -25,6 +25,9 @@ resource "flexibleengine_vpc_route_v2" "vpc_route" {
 
 The following arguments are supported:
 
+* `region` - (Optional, String, ForceNew) The region in which to create the vpc route table.
+  If omitted, the provider-level region will be used. Changing this creates a new resource.
+
 * `destination` (Required) - Specifies the destination IP address or CIDR block. Changing this creates a new Route.
 
 * `nexthop` (Required) - Specifies the next hop. If the route type is peering, enter the VPC peering connection ID.
@@ -44,3 +47,10 @@ All of the argument attributes are also exported as
 result attributes:
 
 * `id` - The route ID.
+
+## Timeouts
+
+This resource provides the following timeouts configuration options:
+
+* `create` - Default is 10 minute.
+* `delete` - Default is 10 minute.

docs/resources/vpc_subnet_v1.md

@@ -75,6 +75,9 @@ The following arguments are supported:
 
 * `tags` - (Optional, Map) The key/value pairs to associate with the subnet.
 
+* `description` (Optional, String) - Provides supplementary information about the subnet.
+  The value can contain no more than 255 characters and cannot contain angle brackets (< or >).
+
 ## Attributes Reference
 
 In addition to all arguments above, the following attributes are exported:
@@ -91,6 +94,13 @@ In addition to all arguments above, the following attributes are exported:
 
 * `ipv6_gateway` - The IPv6 subnet gateway.
 
+## Timeouts
+
+This resource provides the following timeouts configuration options:
+
+* `create` - Default is 5 minute.
+* `delete` - Default is 5 minute.
+
 ## Import
 
 Subnets can be imported using the VPC subnet ID, e.g.

docs/resources/vpc_v1.md

@@ -59,6 +59,13 @@ In addition to all arguments above, the following attributes are exported:
 
 * `status` - The current status of the VPC. Possible values are as follows: CREATING, OK or ERROR.
 
+## Timeouts
+
+This resource provides the following timeouts configuration options:
+
+* `create` - Default is 10 minute.
+* `delete` - Default is 3 minute.
+
 ## Import
 
 VPCs can be imported using the `id`, e.g.