Struct google_accesscontextmanager1_beta::ServicePerimeter [−][src]
pub struct ServicePerimeter { pub status: Option<ServicePerimeterConfig>, pub update_time: Option<String>, pub description: Option<String>, pub title: Option<String>, pub perimeter_type: Option<String>, pub create_time: Option<String>, pub name: Option<String>, }
ServicePerimeter
describes a set of GCP 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 GCP
project can only belong to a single regular Service Perimeter. Service
Perimeter Bridges can contain only GCP projects as members, a single GCP
project may belong to multiple Service Perimeter Bridges.
Activities
This type is used in activities, which are methods you may call on this type or where this type is involved in. The list links the activity name, along with information about where it is used (one of request and response).
- service perimeters create access policies (request)
- service perimeters patch access policies (request)
- service perimeters get access policies (response)
Fields
status: Option<ServicePerimeterConfig>
Current ServicePerimeter configuration. Specifies sets of resources, restricted/unrestricted services and access levels that determine perimeter content and boundaries.
update_time: Option<String>
Output only. Time the ServicePerimeter
was updated in UTC.
description: Option<String>
Description of the ServicePerimeter
and its use. Does not affect
behavior.
title: Option<String>
Human readable title. Must be unique within the Policy.
perimeter_type: Option<String>
Perimeter type indicator. A single project 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, restricted/unrestricted service lists as well as access lists must be empty.
create_time: Option<String>
Output only. Time the ServicePerimeter
was created in UTC.
name: Option<String>
Required. 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}
Trait Implementations
impl Default for ServicePerimeter
[src]
impl Default for ServicePerimeter
fn default() -> ServicePerimeter
[src]
fn default() -> ServicePerimeter
Returns the "default value" for a type. Read more
impl Clone for ServicePerimeter
[src]
impl Clone for ServicePerimeter
fn clone(&self) -> ServicePerimeter
[src]
fn clone(&self) -> ServicePerimeter
Returns a copy of the value. Read more
fn clone_from(&mut self, source: &Self)
1.0.0[src]
fn clone_from(&mut self, source: &Self)
Performs copy-assignment from source
. Read more
impl Debug for ServicePerimeter
[src]
impl Debug for ServicePerimeter
fn fmt(&self, f: &mut Formatter) -> Result
[src]
fn fmt(&self, f: &mut Formatter) -> Result
Formats the value using the given formatter. Read more
impl RequestValue for ServicePerimeter
[src]
impl RequestValue for ServicePerimeter
impl ResponseResult for ServicePerimeter
[src]
impl ResponseResult for ServicePerimeter
Auto Trait Implementations
impl Send for ServicePerimeter
impl Send for ServicePerimeter
impl Sync for ServicePerimeter
impl Sync for ServicePerimeter