pub struct NetworkAttachmentResult {Show 15 fields
pub connection_endpoints: Output<Vec<NetworkAttachmentConnectionEndpoint>>,
pub connection_preference: Output<String>,
pub creation_timestamp: Output<String>,
pub description: Output<Option<String>>,
pub fingerprint: Output<String>,
pub kind: Output<String>,
pub name: Output<String>,
pub network: Output<String>,
pub producer_accept_lists: Output<Option<Vec<String>>>,
pub producer_reject_lists: Output<Option<Vec<String>>>,
pub project: Output<String>,
pub region: Output<String>,
pub self_link: Output<String>,
pub self_link_with_id: Output<String>,
pub subnetworks: Output<Vec<String>>,
}Fields§
§connection_endpoints: Output<Vec<NetworkAttachmentConnectionEndpoint>>An array of connections for all the producers connected to this network attachment. Structure is documented below.
connection_preference: Output<String>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.
creation_timestamp: Output<String>Creation timestamp in RFC3339 text format.
description: Output<Option<String>>An optional description of this resource. Provide this property when you create the resource.
fingerprint: Output<String>Fingerprint of this resource. A hash of the contents stored in this object. This field is used in optimistic locking. An up-to-date fingerprint must be provided in order to patch.
kind: Output<String>Type of the resource.
name: Output<String>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.
network: Output<String>The URL of the network which the Network Attachment belongs to. Practically it is inferred by fetching the network of the first subnetwork associated. Because it is required that all the subnetworks must be from the same network, it is assured that the Network Attachment belongs to the same network as all the subnetworks.
producer_accept_lists: Output<Option<Vec<String>>>Projects that are allowed to connect to this network attachment. The project can be specified using its id or number.
producer_reject_lists: Output<Option<Vec<String>>>Projects that are not allowed to connect to this network attachment. The project can be specified using its id or number.
project: Output<String>The ID of the project in which the resource belongs. If it is not provided, the provider project is used.
region: Output<String>URL of the region where the network attachment resides. This field applies only to the region resource. You must specify this field as part of the HTTP request URL. It is not settable as a field in the request body.
self_link: Output<String>Server-defined URL for the resource.
self_link_with_id: Output<String>Server-defined URL for this resource’s resource id.
subnetworks: Output<Vec<String>>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.