REST Resource: projects.locations.config

Resource: Config

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

JSON representation 
{
  "name": string,
  "ingestion": {
    object (Ingestion)
  },
  "etag": string
}
Fields
name

string

Identifier. The resource name of the config. Format: organizations/{organization_id}/locations/global/config folders/{folder_id}/locations/global/config projects/{projectId}/locations/global/config projects/{project_number}/locations/global/config
ingestion

object (Ingestion)

Optional. Ingestion rule for Data Lineage ingestion.
etag

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 config.get, and systems are expected to put that etag in the request to config.patch 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 config.patch, then the existing config, if any, will be overwritten.

Methods

get

 Get the Config for a given resource.

patch

 Update the Config for a given resource.