GoogleCloudDatacatalogLineageV1Origin
import type { GoogleCloudDatacatalogLineageV1Origin } from "https://googleapis.deno.dev/v1/datalineage:v1.ts";Origin of a process.
interface GoogleCloudDatacatalogLineageV1Origin {
name?: string;
sourceType?:
} | "SOURCE_TYPE_UNSPECIFIED"
| "CUSTOM"
| "BIGQUERY"
| "DATA_FUSION"
| "COMPOSER"
| "LOOKER_STUDIO"
| "DATAPROC"
| "VERTEX_AI";
§Properties
§
name?: string
[src]If the source_type isn't CUSTOM, the value of this field should be a
Google Cloud resource name of the system, which reports lineage. The
project and location parts of the resource name must match the project and
location of the lineage resource being created. Examples: - {source_type: COMPOSER, name: "projects/foo/locations/us/environments/bar"} -
{source_type: BIGQUERY, name: "projects/foo/locations/eu"} -
{source_type: CUSTOM, name: "myCustomIntegration"}
§
sourceType?: "SOURCE_TYPE_UNSPECIFIED" | "CUSTOM" | "BIGQUERY" | "DATA_FUSION" | "COMPOSER" | "LOOKER_STUDIO" | "DATAPROC" | "VERTEX_AI"
[src]Type of the source. Use of a source_type other than CUSTOM for process
creation or updating is highly discouraged. It might be restricted in the
future without notice. There will be increase in cost if you use any of the
source types other than CUSTOM.