Data Lineage V1 API - Class Google::Cloud::DataCatalog::Lineage::ConfigManagement::V1::Config (v0.1.0)

Reference documentation and code samples for the Data Lineage V1 API class Google::Cloud::DataCatalog::Lineage::ConfigManagement::V1::Config.

Configuration for Data Lineage. Defines different configuration options for Lineage customers to control behaviour of lineage systems.

Inherits

  • Object

Extended By

  • Google::Protobuf::MessageExts::ClassMethods

Includes

  • Google::Protobuf::MessageExts

Methods

#etag

def etag() -> ::String
Returns
  • (::String) — Optional. etag is used for optimistic concurrency control as a way to help prevent simultaneous updates of a config from overwriting each other. It is required that systems make use of the etag in the read-modify-write cycle to perform config updates in order to avoid race conditions: An etag is returned in the response to GetConfig, and systems are expected to put that etag in the request to UpdateConfig to ensure that their change will be applied to the same version of the config. If an etag is not provided in the call to UpdateConfig, then the existing config, if any, will be overwritten.

#etag=

def etag=(value) -> ::String
Parameter
  • value (::String) — Optional. etag is used for optimistic concurrency control as a way to help prevent simultaneous updates of a config from overwriting each other. It is required that systems make use of the etag in the read-modify-write cycle to perform config updates in order to avoid race conditions: An etag is returned in the response to GetConfig, and systems are expected to put that etag in the request to UpdateConfig to ensure that their change will be applied to the same version of the config. If an etag is not provided in the call to UpdateConfig, then the existing config, if any, will be overwritten.
Returns
  • (::String) — Optional. etag is used for optimistic concurrency control as a way to help prevent simultaneous updates of a config from overwriting each other. It is required that systems make use of the etag in the read-modify-write cycle to perform config updates in order to avoid race conditions: An etag is returned in the response to GetConfig, and systems are expected to put that etag in the request to UpdateConfig to ensure that their change will be applied to the same version of the config. If an etag is not provided in the call to UpdateConfig, then the existing config, if any, will be overwritten.

#ingestion

def ingestion() -> ::Google::Cloud::DataCatalog::Lineage::ConfigManagement::V1::Config::Ingestion
Returns

#ingestion=

def ingestion=(value) -> ::Google::Cloud::DataCatalog::Lineage::ConfigManagement::V1::Config::Ingestion
Parameter
Returns

#name

def name() -> ::String
Returns
  • (::String) — Identifier. The resource name of the config. Format: organizations/{organization_id}/locations/global/config folders/{folder_id}/locations/global/config projects/{project_id}/locations/global/config projects/{project_number}/locations/global/config

#name=

def name=(value) -> ::String
Parameter
  • value (::String) — Identifier. The resource name of the config. Format: organizations/{organization_id}/locations/global/config folders/{folder_id}/locations/global/config projects/{project_id}/locations/global/config projects/{project_number}/locations/global/config
Returns
  • (::String) — Identifier. The resource name of the config. Format: organizations/{organization_id}/locations/global/config folders/{folder_id}/locations/global/config projects/{project_id}/locations/global/config projects/{project_number}/locations/global/config