GetServiceAttachmentResult

data class GetServiceAttachmentResult(val connectedEndpoints: List<ServiceAttachmentConnectedEndpointResponse>, val connectionPreference: String, val consumerAcceptLists: List<ServiceAttachmentConsumerProjectLimitResponse>, val consumerRejectLists: List<String>, val creationTimestamp: String, val description: String, val domainNames: List<String>, val enableProxyProtocol: Boolean, val fingerprint: String, val kind: String, val name: String, val natSubnets: List<String>, val producerForwardingRule: String, val pscServiceAttachmentId: Uint128Response, val reconcileConnections: Boolean, val region: String, val selfLink: String, val targetService: String)

Constructors

Link copied to clipboard
fun GetServiceAttachmentResult(connectedEndpoints: List<ServiceAttachmentConnectedEndpointResponse>, connectionPreference: String, consumerAcceptLists: List<ServiceAttachmentConsumerProjectLimitResponse>, consumerRejectLists: List<String>, creationTimestamp: String, description: String, domainNames: List<String>, enableProxyProtocol: Boolean, fingerprint: String, kind: String, name: String, natSubnets: List<String>, producerForwardingRule: String, pscServiceAttachmentId: Uint128Response, reconcileConnections: Boolean, region: String, selfLink: String, targetService: String)

Types

Link copied to clipboard
object Companion

Properties

Link copied to clipboard

An array of connections for all the consumers connected to this service attachment.

Link copied to clipboard

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.

Link copied to clipboard

Projects that are allowed to connect to this service attachment.

Link copied to clipboard

Projects that are not allowed to connect to this service attachment. The project can be specified using its id or number.

Link copied to clipboard

Creation timestamp in RFC3339 text format.

Link copied to clipboard

An optional description of this resource. Provide this property when you create the resource.

Link copied to clipboard

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.

Link copied to clipboard

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.

Link copied to clipboard

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.

Link copied to clipboard

Type of the resource. Always compute#serviceAttachment for service attachments.

Link copied to clipboard

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.

Link copied to clipboard

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.

Link copied to clipboard

The URL of a forwarding rule with loadBalancingScheme INTERNAL* that is serving the endpoint identified by this service attachment.

Link copied to clipboard

An 128-bit global unique ID of the PSC service attachment.

Link copied to clipboard

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 true.

Link copied to clipboard

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.

Link copied to clipboard

Server-defined URL for the resource.

Link copied to clipboard

The URL of a service serving the endpoint identified by this service attachment.