gcloud alpha datalineage config update

INFORMATION
gcloud alpha datalineage config update is not available in universe domain universe.
NAME
gcloud alpha datalineage config update - update Data Lineage configuration
SYNOPSIS
gcloud alpha 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: 
gcloud alpha datalineage config update --config=my_config.json

To update the configuration for the project ``my-project`` using an inline JSON string, run: 

gcloud alpha datalineage config update --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.
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 help for details.

NOTES
This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early access allowlist. These variants are also available: 
gcloud datalineage config update
 
gcloud beta datalineage config update