Network Attachment Args
{{% examples %}}
Example Usage
{{% /examples %}}
Import
NetworkAttachment can be imported using any of these accepted formats
$ pulumi import gcp:compute/networkAttachment:NetworkAttachment default projects/{{project}}/regions/{{region}}/networkAttachments/{{name}}
$ pulumi import gcp:compute/networkAttachment:NetworkAttachment default {{project}}/{{region}}/{{name}}
$ pulumi import gcp:compute/networkAttachment:NetworkAttachment default {{region}}/{{name}}
$ pulumi import gcp:compute/networkAttachment:NetworkAttachment default {{name}}
Constructors
Properties
The connection preference of service attachment. The value can be set to ACCEPT_AUTOMATIC. An ACCEPT_AUTOMATIC service attachment is one that always accepts the connection from consumer forwarding rules. Possible values are: ACCEPT_AUTOMATIC
, ACCEPT_MANUAL
, INVALID
.
An optional description of this resource. Provide this property when you create the resource.
Name of the resource. Provided by the client when the resource is created. The name must be 1-63 characters long, and comply with RFC1035. Specifically, the name must be 1-63 characters long and match the regular expression a-z? which means the first character must be a lowercase letter, and all following characters must be a dash, lowercase letter, or digit, except the last character, which cannot be a dash.
Projects that are allowed to connect to this network attachment. The project can be specified using its id or number.
Projects that are not allowed to connect to this network attachment. The project can be specified using its id or number.
An array of URLs where each entry is the URL of a subnet provided by the service consumer to use for endpoints in the producers that connect to this network attachment.