import * as pulumi from "@pulumi/pulumi";
import * as outputs from "../../types/output";
/**
 * Returns the specified ServiceAttachment resource in the given scope.
 */
export declare function getServiceAttachment(args: GetServiceAttachmentArgs, opts?: pulumi.InvokeOptions): Promise<GetServiceAttachmentResult>;
export interface GetServiceAttachmentArgs {
    project?: string;
    region: string;
    serviceAttachment: string;
}
export interface GetServiceAttachmentResult {
    /**
     * An array of connections for all the consumers connected to this service attachment.
     */
    readonly connectedEndpoints: outputs.compute.alpha.ServiceAttachmentConnectedEndpointResponse[];
    /**
     * 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.
     */
    readonly connectionPreference: string;
    /**
     * Projects that are allowed to connect to this service attachment.
     */
    readonly consumerAcceptLists: outputs.compute.alpha.ServiceAttachmentConsumerProjectLimitResponse[];
    /**
     * Projects that are not allowed to connect to this service attachment. The project can be specified using its id or number.
     */
    readonly consumerRejectLists: string[];
    /**
     * Creation timestamp in RFC3339 text format.
     */
    readonly creationTimestamp: string;
    /**
     * An optional description of this resource. Provide this property when you create the resource.
     */
    readonly description: 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.
     */
    readonly domainNames: string[];
    /**
     * 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.
     */
    readonly enableProxyProtocol: boolean;
    /**
     * 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.
     */
    readonly fingerprint: string;
    /**
     * Type of the resource. Always compute#serviceAttachment for service attachments.
     */
    readonly kind: 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.
     */
    readonly name: 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.
     */
    readonly natSubnets: string[];
    /**
     * The URL of a forwarding rule with loadBalancingScheme INTERNAL* that is serving the endpoint identified by this service attachment.
     */
    readonly producerForwardingRule: string;
    /**
     * The number of VPCs to which this endpoint is allowed to be propagated per accept list resource (project or network). For ACCEPT_AUTOMATIC service attachment, this limit is default to per project.
     */
    readonly propagatedConnectionLimit: number;
    /**
     * An 128-bit global unique ID of the PSC service attachment.
     */
    readonly pscServiceAttachmentId: outputs.compute.alpha.Uint128Response;
    /**
     * 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.
     */
    readonly reconcileConnections: boolean;
    /**
     * 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.
     */
    readonly region: string;
    /**
     * Server-defined URL for the resource.
     */
    readonly selfLink: string;
    /**
     * The URL of a service serving the endpoint identified by this service attachment.
     */
    readonly targetService: string;
    /**
     * When a tunneling config is set on this service attachment it will encapsulate traffic between consumer and producer. When tunneling is enabled: - nat_subnets must be unset - enable_proxy_protocol must be false - producer_forwarding_rule must be a L4 ILB. -
     */
    readonly tunnelingConfig: outputs.compute.alpha.ServiceAttachmentTunnelingConfigResponse;
}
/**
 * Returns the specified ServiceAttachment resource in the given scope.
 */
export declare function getServiceAttachmentOutput(args: GetServiceAttachmentOutputArgs, opts?: pulumi.InvokeOptions): pulumi.Output<GetServiceAttachmentResult>;
export interface GetServiceAttachmentOutputArgs {
    project?: pulumi.Input<string>;
    region: pulumi.Input<string>;
    serviceAttachment: pulumi.Input<string>;
}