Class ServicePerimeterState.Builder
- java.lang.Object
-
- com.pulumi.gcp.accesscontextmanager.inputs.ServicePerimeterState.Builder
-
- Enclosing class:
- ServicePerimeterState
public static final class ServicePerimeterState.Builder extends java.lang.Object
-
-
Constructor Summary
Constructors Constructor Description Builder()
Builder(ServicePerimeterState defaults)
-
Method Summary
-
-
-
Constructor Detail
-
Builder
public Builder()
-
Builder
public Builder(ServicePerimeterState defaults)
-
-
Method Detail
-
createTime
public ServicePerimeterState.Builder createTime(@Nullable com.pulumi.core.Output<java.lang.String> createTime)
- Parameters:
createTime
- Time the AccessPolicy was created in UTC.- Returns:
- builder
-
createTime
public ServicePerimeterState.Builder createTime(java.lang.String createTime)
- Parameters:
createTime
- Time the AccessPolicy was created in UTC.- Returns:
- builder
-
description
public ServicePerimeterState.Builder description(@Nullable com.pulumi.core.Output<java.lang.String> description)
- Parameters:
description
- Description of the ServicePerimeter and its use. Does not affect behavior.- Returns:
- builder
-
description
public ServicePerimeterState.Builder description(java.lang.String description)
- Parameters:
description
- Description of the ServicePerimeter and its use. Does not affect behavior.- Returns:
- builder
-
name
public ServicePerimeterState.Builder name(@Nullable com.pulumi.core.Output<java.lang.String> name)
- Parameters:
name
- Resource name for the ServicePerimeter. The short_name component must begin with a letter and only include alphanumeric and '_'. Format: accessPolicies/{policy_id}/servicePerimeters/{short_name} ***- Returns:
- builder
-
name
public ServicePerimeterState.Builder name(java.lang.String name)
- Parameters:
name
- Resource name for the ServicePerimeter. The short_name component must begin with a letter and only include alphanumeric and '_'. Format: accessPolicies/{policy_id}/servicePerimeters/{short_name} ***- Returns:
- builder
-
parent
public ServicePerimeterState.Builder parent(@Nullable com.pulumi.core.Output<java.lang.String> parent)
- Parameters:
parent
- The AccessPolicy this ServicePerimeter lives in. Format: accessPolicies/{policy_id}- Returns:
- builder
-
parent
public ServicePerimeterState.Builder parent(java.lang.String parent)
- Parameters:
parent
- The AccessPolicy this ServicePerimeter lives in. Format: accessPolicies/{policy_id}- Returns:
- builder
-
perimeterType
public ServicePerimeterState.Builder perimeterType(@Nullable com.pulumi.core.Output<java.lang.String> perimeterType)
- Parameters:
perimeterType
- Specifies the type of the Perimeter. There are two types: regular and bridge. Regular Service Perimeter contains resources, access levels, and restricted services. Every resource can be in at most ONE regular Service Perimeter. In addition to being in a regular service perimeter, a resource can also be in zero or more perimeter bridges. A perimeter bridge only contains resources. Cross project operations are permitted if all effected resources share some perimeter (whether bridge or regular). Perimeter Bridge does not contain access levels or services: those are governed entirely by the regular perimeter that resource is in. Perimeter Bridges are typically useful when building more complex topologies with many independent perimeters that need to share some data with a common perimeter, but should not be able to share data among themselves. Default value is `PERIMETER_TYPE_REGULAR`. Possible values are: `PERIMETER_TYPE_REGULAR`, `PERIMETER_TYPE_BRIDGE`.- Returns:
- builder
-
perimeterType
public ServicePerimeterState.Builder perimeterType(java.lang.String perimeterType)
- Parameters:
perimeterType
- Specifies the type of the Perimeter. There are two types: regular and bridge. Regular Service Perimeter contains resources, access levels, and restricted services. Every resource can be in at most ONE regular Service Perimeter. In addition to being in a regular service perimeter, a resource can also be in zero or more perimeter bridges. A perimeter bridge only contains resources. Cross project operations are permitted if all effected resources share some perimeter (whether bridge or regular). Perimeter Bridge does not contain access levels or services: those are governed entirely by the regular perimeter that resource is in. Perimeter Bridges are typically useful when building more complex topologies with many independent perimeters that need to share some data with a common perimeter, but should not be able to share data among themselves. Default value is `PERIMETER_TYPE_REGULAR`. Possible values are: `PERIMETER_TYPE_REGULAR`, `PERIMETER_TYPE_BRIDGE`.- Returns:
- builder
-
spec
public ServicePerimeterState.Builder spec(@Nullable com.pulumi.core.Output<ServicePerimeterSpecArgs> spec)
- Parameters:
spec
- 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 `useExplicitDryRunSpec` flag is set. Structure is documented below.- Returns:
- builder
-
spec
public ServicePerimeterState.Builder spec(ServicePerimeterSpecArgs spec)
- Parameters:
spec
- 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 `useExplicitDryRunSpec` flag is set. Structure is documented below.- Returns:
- builder
-
status
public ServicePerimeterState.Builder status(@Nullable com.pulumi.core.Output<ServicePerimeterStatusArgs> status)
- Parameters:
status
- ServicePerimeter configuration. Specifies sets of resources, restricted services and access levels that determine perimeter content and boundaries. Structure is documented below.- Returns:
- builder
-
status
public ServicePerimeterState.Builder status(ServicePerimeterStatusArgs status)
- Parameters:
status
- ServicePerimeter configuration. Specifies sets of resources, restricted services and access levels that determine perimeter content and boundaries. Structure is documented below.- Returns:
- builder
-
title
public ServicePerimeterState.Builder title(@Nullable com.pulumi.core.Output<java.lang.String> title)
- Parameters:
title
- Human readable title. Must be unique within the Policy.- Returns:
- builder
-
title
public ServicePerimeterState.Builder title(java.lang.String title)
- Parameters:
title
- Human readable title. Must be unique within the Policy.- Returns:
- builder
-
updateTime
public ServicePerimeterState.Builder updateTime(@Nullable com.pulumi.core.Output<java.lang.String> updateTime)
- Parameters:
updateTime
- Time the AccessPolicy was updated in UTC.- Returns:
- builder
-
updateTime
public ServicePerimeterState.Builder updateTime(java.lang.String updateTime)
- Parameters:
updateTime
- Time the AccessPolicy was updated in UTC.- Returns:
- builder
-
useExplicitDryRunSpec
public ServicePerimeterState.Builder useExplicitDryRunSpec(@Nullable com.pulumi.core.Output<java.lang.Boolean> useExplicitDryRunSpec)
- Parameters:
useExplicitDryRunSpec
- 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. useExplicitDryRunSpec must bet set to True if any of the fields in the spec are set to non-default values.- Returns:
- builder
-
useExplicitDryRunSpec
public ServicePerimeterState.Builder useExplicitDryRunSpec(java.lang.Boolean useExplicitDryRunSpec)
- Parameters:
useExplicitDryRunSpec
- 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. useExplicitDryRunSpec must bet set to True if any of the fields in the spec are set to non-default values.- Returns:
- builder
-
build
public ServicePerimeterState build()
-
-