ServicePerimeterState class

Input properties used for looking up and filtering ServicePerimeter resources.

Constructors

ServicePerimeterState({Input<String?>? createTime, Input<String?>? deletionPolicy, Input<String?>? description, Input<String?>? name, Input<String?>? parent, Input<String?>? perimeterType, Input<ServicePerimeterSpec?>? spec, Input<ServicePerimeterStatus?>? status, Input<String?>? title, Input<String?>? updateTime, Input<bool?>? useExplicitDryRunSpec})
Creates a new ServicePerimeterState. createTime Time the AccessPolicy was created in UTC. deletionPolicy Whether Terraform will be prevented from destroying the resource. Defaults to DELETE. description Description of the ServicePerimeter and its use. Does not affect name Resource name for the ServicePerimeter. The shortName component must parent The AccessPolicy this ServicePerimeter lives in. perimeterType Specifies the type of the Perimeter. There are two types: regular and spec Proposed (or dry run) ServicePerimeter configuration. status ServicePerimeter configuration. Specifies sets of resources, title Human readable title. Must be unique within the Policy. updateTime Time the AccessPolicy was updated in UTC. useExplicitDryRunSpec Use explicit dry run spec flag. Ordinarily, a dry-run spec implicitly exists
const
ServicePerimeterState.fromMap(Map<String, dynamic> map)
factory

Properties

createTime → Input<String?>?
Time the AccessPolicy was created in UTC.
final
deletionPolicy → Input<String?>?
Whether Terraform will be prevented from destroying the resource. Defaults to DELETE. When a 'terraform destroy' or 'pulumi up' would delete the resource, the command will fail if this field is set to "PREVENT" in Terraform state. When set to "ABANDON", the command will remove the resource from Terraform management without updating or deleting the resource in the API. When set to "DELETE", deleting the resource is allowed.
final
description → Input<String?>?
Description of the ServicePerimeter and its use. Does not affect behavior.
final
hashCode → int
The hash code for this object.
no setterinherited
name → Input<String?>?
Resource name for the ServicePerimeter. The shortName component must begin with a letter and only include alphanumeric and '_'. Format: accessPolicies/{policy_id}/servicePerimeters/{short_name}
final
parent → Input<String?>?
The AccessPolicy this ServicePerimeter lives in. Format: accessPolicies/{policy_id}
final
perimeterType → Input<String?>?
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.
final
runtimeType → Type
A representation of the runtime type of the object.
no setterinherited
spec → Input<ServicePerimeterSpec?>?
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.
final
status → Input<ServicePerimeterStatus?>?
ServicePerimeter configuration. Specifies sets of resources, restricted services and access levels that determine perimeter content and boundaries. Structure is documented below.
final
title → Input<String?>?
Human readable title. Must be unique within the Policy.
final
updateTime → Input<String?>?
Time the AccessPolicy was updated in UTC.
final
useExplicitDryRunSpec → Input<bool?>?
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.
final

Methods

noSuchMethod(Invocation invocation) → dynamic
Invoked when a nonexistent method or property is accessed.
inherited
toMap() → Map<String, dynamic>
toString() → String
A string representation of this object.
inherited

Operators

operator ==(Object other) → bool
The equality operator.
inherited