network-peering
dcos-terraform/network-peering/gcp
 GCP Network Peering ============================= Creates a GCP network peering between two networks, autocreates routes EXAMPLE ------- ``hcl module "network-peering" { source = "dcos-terraform/network-peering/gcp" version = "~> 0.2.0" cluster_name = "${var.cluster_name}" local_network_name = "master" local_network_self_link = "${var.local_network_self_link}" remote_network_name = "use1" remote_network_self_link = "${var.remote_network_self_link}" } ` Inputs | Name | Description | Type | Default | Required | |------|-------------|:----:|:-----:|:-----:| | cluster\_name | Name of the DC/OS cluster | string | n/a | yes | | local
| Name | Type | Description | Default |
|---|---|---|---|
| cluster_name | string | Name of the DC/OS cluster | required |
| local_network_name | string | Local network name, used for naming the peering | required |
| local_network_self_link | string | Local network self_link | required |
| remote_network_name | string | Remote network name, used for naming the peering | required |
| remote_network_self_link | string | Remote network self_link | required |
| wait_for_peering_id | string | The peering ID we need to wait for, before we can create another peering | "" |
local_peering_state — Local peering statelocal_peering_state_details — Local peering state detailsremote_peering_state — Remote peering stateremote_peering_state_details — Remote peering state detailspeering_resource_id — Peering ID for null_resource triggers usage on additional peering module calls