Class: Google::Apis::CloudassetV1beta1::GoogleIdentityAccesscontextmanagerV1ServicePerimeter

Inherits:
Object
  • Object
show all
Includes:
Google::Apis::Core::Hashable, Google::Apis::Core::JsonObjectSupport
Defined in:
lib/google/apis/cloudasset_v1beta1/classes.rb,
lib/google/apis/cloudasset_v1beta1/representations.rb,
lib/google/apis/cloudasset_v1beta1/representations.rb

Overview

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.

Instance Attribute Summary collapse

Instance Method Summary collapse

Constructor Details

#initialize(**args) ⇒ GoogleIdentityAccesscontextmanagerV1ServicePerimeter

Returns a new instance of GoogleIdentityAccesscontextmanagerV1ServicePerimeter.



1889
1890
1891
 
# File 'lib/google/apis/cloudasset_v1beta1/classes.rb', line 1889

def initialize(**args)
   update!(**args)
end

Instance Attribute Details

#description ⇒ String

Description of the ServicePerimeter and its use. Does not affect behavior. Corresponds to the JSON property description

Returns:

  • (String) 


1839
1840
1841
 
# File 'lib/google/apis/cloudasset_v1beta1/classes.rb', line 1839

def description
  @description
end

#name ⇒ String

Resource name for the ServicePerimeter. Format: accessPolicies/ access_policy/servicePerimeters/service_perimeter`. Theservice_perimeter component must begin with a letter, followed by alphanumeric characters or_. After you create aServicePerimeter, you cannot change itsname. Corresponds to the JSON propertyname`

Returns:

  • (String) 


1847
1848
1849
 
# File 'lib/google/apis/cloudasset_v1beta1/classes.rb', line 1847

def name
  @name
end

#perimeter_type ⇒ String

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. Corresponds to the JSON property perimeterType

Returns:

  • (String) 


1856
1857
1858
 
# File 'lib/google/apis/cloudasset_v1beta1/classes.rb', line 1856

def perimeter_type
  @perimeter_type
end

#spec ⇒ Google::Apis::CloudassetV1beta1::GoogleIdentityAccesscontextmanagerV1ServicePerimeterConfig

ServicePerimeterConfig specifies a set of Google Cloud resources that describe specific Service Perimeter configuration. Corresponds to the JSON property spec

Returns:



1862
1863
1864
 
# File 'lib/google/apis/cloudasset_v1beta1/classes.rb', line 1862

def spec
  @spec
end

#status ⇒ Google::Apis::CloudassetV1beta1::GoogleIdentityAccesscontextmanagerV1ServicePerimeterConfig

ServicePerimeterConfig specifies a set of Google Cloud resources that describe specific Service Perimeter configuration. Corresponds to the JSON property status

Returns:



1868
1869
1870
 
# File 'lib/google/apis/cloudasset_v1beta1/classes.rb', line 1868

def status
  @status
end

#title ⇒ String

Human readable title. Must be unique within the Policy. Corresponds to the JSON property title

Returns:

  • (String) 


1873
1874
1875
 
# File 'lib/google/apis/cloudasset_v1beta1/classes.rb', line 1873

def title
  @title
end

#use_explicit_dry_run_spec ⇒ Boolean Also known as: use_explicit_dry_run_spec?

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. Corresponds to the JSON property useExplicitDryRunSpec

Returns:

  • (Boolean) 


1886
1887
1888
 
# File 'lib/google/apis/cloudasset_v1beta1/classes.rb', line 1886

def use_explicit_dry_run_spec
  @use_explicit_dry_run_spec
end

Instance Method Details

#update!(**args) ⇒ Object

Update properties of this object



1894
1895
1896
1897
1898
1899
1900
1901
1902
 
# File 'lib/google/apis/cloudasset_v1beta1/classes.rb', line 1894

def update!(**args)
  @description = args[:description] if args.key?(:description)
  @name = args[:name] if args.key?(:name)
  @perimeter_type = args[:perimeter_type] if args.key?(:perimeter_type)
  @spec = args[:spec] if args.key?(:spec)
  @status = args[:status] if args.key?(:status)
  @title = args[:title] if args.key?(:title)
  @use_explicit_dry_run_spec = args[:use_explicit_dry_run_spec] if args.key?(:use_explicit_dry_run_spec)
end