You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
feat: enable usage of existing VPC/Subnets feature (#666)
Added the following optional properties to the configuration map for `vpcs` in order to support deployment of landing-zone into existing VPCs and Subnets.
* `existing_vpc_id` (string)
* `existing_subnet_ids` (list(string))
| <aname="input_transit_gateway_resource_group"></a> [transit\_gateway\_resource\_group](#input\_transit\_gateway\_resource\_group)| Name of resource group to use for transit gateway. Must be included in `var.resource_group`|`string`| n/a | yes |
| <aname="input_vpn_gateways"></a> [vpn\_gateways](#input\_vpn\_gateways)| List of VPN Gateways to create. | <pre>list(<br> object({<br> name = string<br> vpc_name = string<br> subnet_name = string # Do not include prefix, use same name as in `var.subnets`<br> mode = optional(string)<br> resource_group = optional(string)<br> access_tags = optional(list(string), [])<br> })<br> )</pre> | n/a | yes |
| <aname="input_wait_till"></a> [wait\_till](#input\_wait\_till)| To avoid long wait times when you run your Terraform code, you can specify the stage when you want Terraform to mark the cluster resource creation as completed. Depending on what stage you choose, the cluster creation might not be fully completed and continues to run in the background. However, your Terraform code can continue to run without waiting for the cluster to be fully created. Supported args are `MasterNodeReady`, `OneWorkerNodeReady`, and `IngressReady`|`string`|`"IngressReady"`| no |
0 commit comments