Struct google_compute1::api::ServiceAttachment
source · pub struct ServiceAttachment {Show 19 fields
pub connected_endpoints: Option<Vec<ServiceAttachmentConnectedEndpoint>>,
pub connection_preference: Option<String>,
pub consumer_accept_lists: Option<Vec<ServiceAttachmentConsumerProjectLimit>>,
pub consumer_reject_lists: Option<Vec<String>>,
pub creation_timestamp: Option<String>,
pub description: Option<String>,
pub domain_names: Option<Vec<String>>,
pub enable_proxy_protocol: Option<bool>,
pub fingerprint: Option<Vec<u8>>,
pub id: Option<u64>,
pub kind: Option<String>,
pub name: Option<String>,
pub nat_subnets: Option<Vec<String>>,
pub producer_forwarding_rule: Option<String>,
pub psc_service_attachment_id: Option<Uint128>,
pub reconcile_connections: Option<bool>,
pub region: Option<String>,
pub self_link: Option<String>,
pub target_service: Option<String>,
}Expand description
Represents a ServiceAttachment resource. A service attachment represents a service that a producer has exposed. It encapsulates the load balancer which fronts the service runs and a list of NAT IP ranges that the producers uses to represent the consumers connecting to the service.
§Activities
This type is used in activities, which are methods you may call on this type or where this type is involved in. The list links the activity name, along with information about where it is used (one of request and response).
- aggregated list service attachments (none)
- delete service attachments (none)
- get service attachments (response)
- get iam policy service attachments (none)
- insert service attachments (request)
- list service attachments (none)
- patch service attachments (request)
- set iam policy service attachments (none)
- test iam permissions service attachments (none)
Fields§
§connected_endpoints: Option<Vec<ServiceAttachmentConnectedEndpoint>>[Output Only] An array of connections for all the consumers connected to this service attachment.
connection_preference: Option<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.
consumer_accept_lists: Option<Vec<ServiceAttachmentConsumerProjectLimit>>Projects that are allowed to connect to this service attachment.
consumer_reject_lists: Option<Vec<String>>Projects that are not allowed to connect to this service attachment. The project can be specified using its id or number.
creation_timestamp: Option<String>[Output Only] Creation timestamp in RFC3339 text format.
description: Option<String>An optional description of this resource. Provide this property when you create the resource.
domain_names: Option<Vec<String>>If specified, the domain name will be used during the integration between the PSC connected endpoints and the Cloud DNS. For example, this is a valid domain name: “p.mycompany.com.”. Current max number of domain names supported is 1.
enable_proxy_protocol: Option<bool>If true, enable the proxy protocol which is for supplying client TCP/IP address data in TCP connections that traverse proxies on their way to destination servers.
fingerprint: Option<Vec<u8>>Fingerprint of this resource. A hash of the contents stored in this object. This field is used in optimistic locking. This field will be ignored when inserting a ServiceAttachment. An up-to-date fingerprint must be provided in order to patch/update the ServiceAttachment; otherwise, the request will fail with error 412 conditionNotMet. To see the latest fingerprint, make a get() request to retrieve the ServiceAttachment.
id: Option<u64>[Output Only] The unique identifier for the resource type. The server generates this identifier.
kind: Option<String>[Output Only] Type of the resource. Always compute#serviceAttachment for service attachments.
name: Option<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]([-a-z0-9]*[a-z0-9])? 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.
nat_subnets: Option<Vec<String>>An array of URLs where each entry is the URL of a subnet provided by the service producer to use for NAT in this service attachment.
producer_forwarding_rule: Option<String>The URL of a forwarding rule with loadBalancingScheme INTERNAL* that is serving the endpoint identified by this service attachment.
psc_service_attachment_id: Option<Uint128>[Output Only] An 128-bit global unique ID of the PSC service attachment.
reconcile_connections: Option<bool>This flag determines whether a consumer accept/reject list change can reconcile the statuses of existing ACCEPTED or REJECTED PSC endpoints. - If false, connection policy update will only affect existing PENDING PSC endpoints. Existing ACCEPTED/REJECTED endpoints will remain untouched regardless how the connection policy is modified . - If true, update will affect both PENDING and ACCEPTED/REJECTED PSC endpoints. For example, an ACCEPTED PSC endpoint will be moved to REJECTED if its project is added to the reject list. For newly created service attachment, this boolean defaults to false.
region: Option<String>[Output Only] URL of the region where the service 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: Option<String>[Output Only] Server-defined URL for the resource.
target_service: Option<String>The URL of a service serving the endpoint identified by this service attachment.
Trait Implementations§
source§impl Clone for ServiceAttachment
impl Clone for ServiceAttachment
source§fn clone(&self) -> ServiceAttachment
fn clone(&self) -> ServiceAttachment
1.0.0 · source§fn clone_from(&mut self, source: &Self)
fn clone_from(&mut self, source: &Self)
source. Read more