Class GoogleIdentityAccesscontextmanagerV1ServicePerimeter
ServicePerimeter
describes a set of Google Cloud resources which can freely import and export data amongst
themselves, but not export outside of the ServicePerimeter
. If a request with a source within this
ServicePerimeter
has a target outside of the ServicePerimeter
, the request will be blocked. Otherwise the
request is allowed. There are two types of Service Perimeter - Regular and Bridge. Regular Service Perimeters
cannot overlap, a single Google Cloud project or VPC network can only belong to a single regular Service
Perimeter. Service Perimeter Bridges can contain only Google Cloud projects as members, a single Google Cloud
project may belong to multiple Service Perimeter Bridges.
Implements
Inherited Members
Namespace: Google.Apis.CloudAsset.v1p5beta1.Data
Assembly: Google.Apis.CloudAsset.v1p5beta1.dll
Syntax
public class GoogleIdentityAccesscontextmanagerV1ServicePerimeter : IDirectResponseSchema
Properties
Description
Description of the ServicePerimeter
and its use. Does not affect behavior.
Declaration
[JsonProperty("description")]
public virtual string Description { get; set; }
Property Value
Type | Description |
---|---|
string |
ETag
Optional. An opaque identifier for the current version of the ServicePerimeter
. Clients should not expect
this to be in any specific format. If etag is not provided, the operation will be performed as if a valid
etag is provided.
Declaration
[JsonProperty("etag")]
public virtual string ETag { get; set; }
Property Value
Type | Description |
---|---|
string |
Name
Identifier. 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
.
Declaration
[JsonProperty("name")]
public virtual string Name { get; set; }
Property Value
Type | Description |
---|---|
string |
PerimeterType
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.
Declaration
[JsonProperty("perimeterType")]
public virtual string PerimeterType { get; set; }
Property Value
Type | Description |
---|---|
string |
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 "use_explicit_dry_run_spec" flag is set.
Declaration
[JsonProperty("spec")]
public virtual GoogleIdentityAccesscontextmanagerV1ServicePerimeterConfig Spec { get; set; }
Property Value
Type | Description |
---|---|
GoogleIdentityAccesscontextmanagerV1ServicePerimeterConfig |
Status
Current ServicePerimeter configuration. Specifies sets of resources, restricted services and access levels that determine perimeter content and boundaries.
Declaration
[JsonProperty("status")]
public virtual GoogleIdentityAccesscontextmanagerV1ServicePerimeterConfig Status { get; set; }
Property Value
Type | Description |
---|---|
GoogleIdentityAccesscontextmanagerV1ServicePerimeterConfig |
Title
Human readable title. Must be unique within the Policy.
Declaration
[JsonProperty("title")]
public virtual string Title { get; set; }
Property Value
Type | Description |
---|---|
string |
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. use_explicit_dry_run_spec must bet set to True if any of the fields in the spec are set to non-default values.
Declaration
[JsonProperty("useExplicitDryRunSpec")]
public virtual bool? UseExplicitDryRunSpec { get; set; }
Property Value
Type | Description |
---|---|
bool? |