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
Copy file name to clipboardExpand all lines: 1-org/envs/shared/README.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -36,6 +36,7 @@
36
36
| dns\_hub\_project\_id | The DNS hub project ID |
37
37
| domains\_to\_allow | The list of domains to allow users from in IAM. |
38
38
| interconnect\_project\_id | The Dedicated Interconnect project ID |
39
+
| interconnect\_project\_number | The Dedicated Interconnect project number |
39
40
| logs\_export\_bigquery\_dataset\_name | The log bucket for destination of log exports. See https://cloud.google.com/logging/docs/routing/overview#buckets|
40
41
| logs\_export\_logbucket\_name | The log bucket for destination of log exports. See https://cloud.google.com/logging/docs/routing/overview#buckets|
41
42
| logs\_export\_pubsub\_topic | The Pub/Sub topic for destination of log exports |
Copy file name to clipboardExpand all lines: 3-networks-dual-svpc/README.md
+3Lines changed: 3 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -94,8 +94,11 @@ This step makes use of the **Dual Shared VPC** architecture, and more details ca
94
94
95
95
If you provisioned the prerequisites listed in the [Dedicated Interconnect README](./modules/dedicated_interconnect/README.md), follow these steps to enable Dedicated Interconnect to access on-premises resources.
96
96
97
+
1. Rename `interconnect.tf.example` to `interconnect.tf` in the shared envs folder in `3-networks-dual-svpc/envs/shared`
98
+
1. Update the file `interconnect.tf` with values that are valid for your environment for the interconnects, locations, candidate subnetworks, vlan_tag8021q and peer info.
97
99
1. Rename `interconnect.tf.example` to `interconnect.tf` in base_env folder in `3-networks-dual-svpc/modules/base_env`.
98
100
1. Update the file `interconnect.tf` with values that are valid for your environment for the interconnects, locations, candidate subnetworks, vlan_tag8021q and peer info.
101
+
1. Set variable `enable_dedicated_interconnect` to `true`
99
102
1. The candidate subnetworks and vlan_tag8021q variables can be set to `null` to allow the interconnect module to auto generate these values.
Copy file name to clipboardExpand all lines: 3-networks-dual-svpc/modules/base_env/README.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,6 +13,7 @@
13
13
| default\_region2 | Second subnet region. The shared vpc modules only configures two regions. |`string`| n/a | yes |
14
14
| domain | The DNS name of peering managed zone, for instance 'example.com.'. Must end with a period. |`string`| n/a | yes |
15
15
| egress\_policies | A list of all [egress policies](https://cloud.google.com/vpc-service-controls/docs/ingress-egress-rules#egress-rules-reference), each list object has a `from` and `to` value that describes egress\_from and egress\_to.<br><br>Example: `[{ from={ identities=[], identity_type="ID_TYPE" }, to={ resources=[], operations={ "SRV_NAME"={ OP_TYPE=[] }}}}]`<br><br>Valid Values:<br>`ID_TYPE` = `null` or `IDENTITY_TYPE_UNSPECIFIED` (only allow indentities from list); `ANY_IDENTITY`; `ANY_USER_ACCOUNT`; `ANY_SERVICE_ACCOUNT`<br>`SRV_NAME` = "`*`" (allow all services) or [Specific Services](https://cloud.google.com/vpc-service-controls/docs/supported-products#supported_products)<br>`OP_TYPE` = [methods](https://cloud.google.com/vpc-service-controls/docs/supported-method-restrictions) or [permissions](https://cloud.google.com/vpc-service-controls/docs/supported-method-restrictions)| <pre>list(object({<br> from = any<br> to = any<br> }))</pre> |`[]`| no |
16
+
| enable\_dedicated\_interconnect | Enable Dedicated Interconnect in the environment. |`bool`|`false`| no |
16
17
| enable\_partner\_interconnect | Enable Partner Interconnect in the environment. |`bool`|`false`| no |
17
18
| env | The environment to prepare (ex. development) |`string`| n/a | yes |
18
19
| environment\_code | A short form of the folder level resources (environment) within the Google Cloud organization (ex. d). |`string`| n/a | yes |
0 commit comments