gcloud datalineage config update
Stay organized with collections
Save and categorize content based on your preferences.
- NAME
-
- gcloud datalineage config update - update Data Lineage configuration
- SYNOPSIS
-
-
gcloud datalineage config update--config=CONFIG[--folder=FOLDER|--organization=ORGANIZATION|--project=PROJECT] [GCLOUD_WIDE_FLAG …]
-
- EXAMPLES
-
To update the configuration for the current project using a JSON file
``my_config.json``, run:
gclouddatalineageconfigupdate--config=my_config.jsonTo update the configuration for the project ``my-project`` using an inline JSON string, run:
gclouddatalineageconfigupdate--project=my-project--config='{"ingestion": {"rules":[{"integrationSelector": {"integration": "BIGQUERY"}, "lineageEnablement": {"enabled": true}}]}}' - REQUIRED FLAGS
-
--config=CONFIG- Inline JSON/YAML config or path to a file containing it.
- OPTIONAL FLAGS
-
-
At most one of these can be specified:
--folder=FOLDER- Folder ID.
--organization=ORGANIZATION- Organization ID.
--project=PROJECT- Project ID or number. If none of --project, --folder, or --organization are provided, the current project will be used.
-
At most one of these can be specified:
- GCLOUD WIDE FLAGS
-
These flags are available to all commands:
--access-token-file,--account,--billing-project,--configuration,--flags-file,--flatten,--format,--help,--impersonate-service-account,--log-http,--project,--quiet,--trace-token,--user-output-enabled,--verbosity.Run
$ gcloud helpfor details. - NOTES
-
These variants are also available:
gcloudalphadatalineageconfigupdategcloudbetadatalineageconfigupdate