pulumi-google-native-kotlin/com.pulumi.googlenative.accesscontextmanager.v1.kotlin/ServicePerimeterArgs

ServicePerimeterArgs

data class ServicePerimeterArgs(val accessPolicyId: Output<String>? = null, val description: Output<String>? = null, val name: Output<String>? = null, val perimeterType: Output<ServicePerimeterPerimeterType>? = null, val spec: Output<ServicePerimeterConfigArgs>? = null, val title: Output<String>? = null, val useExplicitDryRunSpec: Output<Boolean>? = null) : ConvertibleToJava<ServicePerimeterArgs>

Creates a service perimeter. The long-running operation from this RPC has a successful status after the service perimeter propagates to long-lasting storage. If a service perimeter contains errors, an error response is returned for the first error encountered.

Constructors

fun ServicePerimeterArgs(accessPolicyId: Output<String>? = null, description: Output<String>? = null, name: Output<String>? = null, perimeterType: Output<ServicePerimeterPerimeterType>? = null, spec: Output<ServicePerimeterConfigArgs>? = null, title: Output<String>? = null, useExplicitDryRunSpec: Output<Boolean>? = null)

Functions

toJava

open override fun toJava(): ServicePerimeterArgs

Properties

accessPolicyId

val accessPolicyId: Output<String>? = null

description

val description: Output<String>? = null

Description of the ServicePerimeter and its use. Does not affect behavior.

name

val name: Output<String>? = null

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.

perimeterType

val perimeterType: Output<ServicePerimeterPerimeterType>? = null

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.

spec

val spec: Output<ServicePerimeterConfigArgs>? = null

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.

title

val title: Output<String>? = null

Human readable title. Must be unique within the Policy.

useExplicitDryRunSpec

val useExplicitDryRunSpec: Output<Boolean>? = null

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.