import * as pulumi from "@pulumi/pulumi";
import * as outputs from "../../types/output";
/**
 * Gets a service perimeter based on the resource name.
 */
export declare function getServicePerimeter(args: GetServicePerimeterArgs, opts?: pulumi.InvokeOptions): Promise<GetServicePerimeterResult>;
export interface GetServicePerimeterArgs {
    accessPolicyId: string;
    servicePerimeterId: string;
}
export interface GetServicePerimeterResult {
    /**
     * Description of the `ServicePerimeter` and its use. Does not affect behavior.
     */
    readonly description: string;
    /**
     * Resource name for the `ServicePerimeter`. Format: `accessPolicies/{access_policy}/servicePerimeters/{service_perimeter}`. The `service_perimeter` component must begin with a letter, followed by alphanumeric characters or `_`. After you create a `ServicePerimeter`, you cannot change its `name`.
     */
    readonly name: string;
    /**
     * Perimeter type indicator. A single project or VPC network is allowed to be a member of single regular perimeter, but multiple service perimeter bridges. A project cannot be a included in a perimeter bridge without being included in regular perimeter. For perimeter bridges, the restricted service list as well as access level lists must be empty.
     */
    readonly perimeterType: string;
    /**
     * Proposed (or dry run) ServicePerimeter configuration. This configuration allows to specify and test ServicePerimeter configuration without enforcing actual access restrictions. Only allowed to be set when the "use_explicit_dry_run_spec" flag is set.
     */
    readonly spec: outputs.accesscontextmanager.v1.ServicePerimeterConfigResponse;
    /**
     * Current ServicePerimeter configuration. Specifies sets of resources, restricted services and access levels that determine perimeter content and boundaries.
     */
    readonly status: outputs.accesscontextmanager.v1.ServicePerimeterConfigResponse;
    /**
     * Human readable title. Must be unique within the Policy.
     */
    readonly title: string;
    /**
     * Use explicit dry run spec flag. Ordinarily, a dry-run spec implicitly exists for all Service Perimeters, and that spec is identical to the status for those Service Perimeters. When this flag is set, it inhibits the generation of the implicit spec, thereby allowing the user to explicitly provide a configuration ("spec") to use in a dry-run version of the Service Perimeter. This allows the user to test changes to the enforced config ("status") without actually enforcing them. This testing is done through analyzing the differences between currently enforced and suggested restrictions. use_explicit_dry_run_spec must bet set to True if any of the fields in the spec are set to non-default values.
     */
    readonly useExplicitDryRunSpec: boolean;
}
/**
 * Gets a service perimeter based on the resource name.
 */
export declare function getServicePerimeterOutput(args: GetServicePerimeterOutputArgs, opts?: pulumi.InvokeOptions): pulumi.Output<GetServicePerimeterResult>;
export interface GetServicePerimeterOutputArgs {
    accessPolicyId: pulumi.Input<string>;
    servicePerimeterId: pulumi.Input<string>;
}