|
| 1 | +--- |
| 2 | +# ---------------------------------------------------------------------------- |
| 3 | +# |
| 4 | +# *** AUTO GENERATED CODE *** AUTO GENERATED CODE *** |
| 5 | +# |
| 6 | +# ---------------------------------------------------------------------------- |
| 7 | +# |
| 8 | +# This file is automatically generated by Magic Modules and manual |
| 9 | +# changes will be clobbered when the file is regenerated. |
| 10 | +# |
| 11 | +# Please read more about how to change this file in |
| 12 | +# .github/CONTRIBUTING.md. |
| 13 | +# |
| 14 | +# ---------------------------------------------------------------------------- |
| 15 | +layout: "google" |
| 16 | +page_title: "Google: google_compute_interconnect_attachment" |
| 17 | +sidebar_current: "docs-google-compute-interconnect-attachment" |
| 18 | +description: |- |
| 19 | + Represents an InterconnectAttachment (VLAN attachment) resource. |
| 20 | +--- |
| 21 | + |
| 22 | +# google\_compute\_interconnect\_attachment |
| 23 | + |
| 24 | +Represents an InterconnectAttachment (VLAN attachment) resource. For more |
| 25 | +information, see Creating VLAN Attachments. |
| 26 | + |
| 27 | + |
| 28 | +## Example Usage |
| 29 | + |
| 30 | +```hcl |
| 31 | +resource "google_compute_router" "foobar" { |
| 32 | + name = "my-router" |
| 33 | + network = "${google_compute_network.foobar.name}" |
| 34 | +} |
| 35 | +
|
| 36 | +resource "google_compute_interconnect_attachment" "default" { |
| 37 | + name = "test-interconnect" |
| 38 | + interconnect = "my-interconnect-id" |
| 39 | + router = "${google_compute_router.foobar.self_link}" |
| 40 | +} |
| 41 | +``` |
| 42 | + |
| 43 | +## Argument Reference |
| 44 | + |
| 45 | +The following arguments are supported: |
| 46 | + |
| 47 | + |
| 48 | +* `interconnect` - |
| 49 | + (Required) |
| 50 | + URL of the underlying Interconnect object that this attachment's traffic will |
| 51 | + traverse through. |
| 52 | + |
| 53 | +* `router` - |
| 54 | + (Required) |
| 55 | + URL of the cloud router to be used for dynamic routing. This router must be in |
| 56 | + the same region as this InterconnectAttachment. The InterconnectAttachment will |
| 57 | + automatically connect the Interconnect to the network & region within which the |
| 58 | + Cloud Router is configured. |
| 59 | + |
| 60 | +* `name` - |
| 61 | + (Required) |
| 62 | + Name of the resource. Provided by the client when the resource is created. The |
| 63 | + name must be 1-63 characters long, and comply with RFC1035. Specifically, the |
| 64 | + name must be 1-63 characters long and match the regular expression |
| 65 | + `[a-z]([-a-z0-9]*[a-z0-9])?` which means the first character must be a |
| 66 | + lowercase letter, and all following characters must be a dash, lowercase |
| 67 | + letter, or digit, except the last character, which cannot be a dash. |
| 68 | + |
| 69 | + |
| 70 | +- - - |
| 71 | + |
| 72 | + |
| 73 | +* `description` - |
| 74 | + (Optional) |
| 75 | + An optional description of this resource. |
| 76 | + |
| 77 | +* `region` - |
| 78 | + (Optional) |
| 79 | + Region where the regional interconnect attachment resides. |
| 80 | +* `project` - (Optional) The ID of the project in which the resource belongs. |
| 81 | + If it is not provided, the provider project is used. |
| 82 | + |
| 83 | + |
| 84 | +## Attributes Reference |
| 85 | + |
| 86 | +In addition to the arguments listed above, the following computed attributes are exported: |
| 87 | + |
| 88 | + |
| 89 | +* `cloud_router_ip_address` - |
| 90 | + IPv4 address + prefix length to be configured on Cloud Router |
| 91 | + Interface for this interconnect attachment. |
| 92 | + |
| 93 | +* `customer_router_ip_address` - |
| 94 | + IPv4 address + prefix length to be configured on the customer |
| 95 | + router subinterface for this interconnect attachment. |
| 96 | + |
| 97 | +* `private_interconnect_info` - |
| 98 | + Information specific to an InterconnectAttachment. This property |
| 99 | + is populated if the interconnect that this is attached to is of type DEDICATED. Structure is documented below. |
| 100 | + |
| 101 | +* `google_reference_id` - |
| 102 | + Google reference ID, to be used when raising support tickets with |
| 103 | + Google or otherwise to debug backend connectivity issues. |
| 104 | + |
| 105 | +* `creation_timestamp` - |
| 106 | + Creation timestamp in RFC3339 text format. |
| 107 | +* `self_link` - The URI of the created resource. |
| 108 | + |
| 109 | + |
| 110 | +The `private_interconnect_info` block contains: |
| 111 | + |
| 112 | +* `tag8021q` - |
| 113 | + 802.1q encapsulation tag to be used for traffic between |
| 114 | + Google and the customer, going to and from this network and region. |
| 115 | + |
| 116 | +## Timeouts |
| 117 | + |
| 118 | +This resource provides the following |
| 119 | +[Timeouts](/docs/configuration/resources.html#timeouts) configuration options: |
| 120 | + |
| 121 | +- `create` - Default is 4 minutes. |
| 122 | +- `delete` - Default is 4 minutes. |
| 123 | + |
| 124 | +## Import |
| 125 | + |
| 126 | +InterconnectAttachment can be imported using any of these accepted formats: |
| 127 | + |
| 128 | +``` |
| 129 | +$ terraform import google_compute_interconnect_attachment.default projects/{{project}}/regions/{{region}}/interconnectAttachments/{{name}} |
| 130 | +$ terraform import google_compute_interconnect_attachment.default {{project}}/{{region}}/{{name}} |
| 131 | +$ terraform import google_compute_interconnect_attachment.default {{name}} |
| 132 | +``` |
0 commit comments