gcloud alpha dataplex entry-links update

NAME
gcloud alpha dataplex entry-links update - update a Dataplex Entry Link
SYNOPSIS
gcloud alpha dataplex entry-links update (ENTRY_LINK : --entry-group=ENTRY_GROUP --location=LOCATION) [--update-aspects=YAML_OR_JSON_FILE] [GCLOUD_WIDE_FLAG …]
DESCRIPTION
(ALPHA) Update specified fields in a given Dataplex Entry Link.
EXAMPLES
To add or update aspects from the YAML/JSON file, run: 
gcloud alpha dataplex entry-links update entrylink1 --project=test-project --location=us-central1 --entry-group=entry-group1 --update-aspects=path-to-a-file-with-aspects.json
POSITIONAL ARGUMENTS
Entry link resource - Arguments and flags that define the Dataplex entry link you want to update. The arguments in this group can be used to specify the attributes of this resource. (NOTE) Some attributes are not given arguments in this group but can be set in other ways.

To set the project attribute:

  • provide the argument entry_link on the command line with a fully specified name;
  • provide the argument --project on the command line;
  • set the property core/project.

This must be specified.

ENTRY_LINK
ID of the entry link or fully qualified identifier for the entry link.

To set the entry-link attribute:

  • provide the argument entry_link on the command line.

This positional argument must be specified if any of the other arguments in this group are specified.

--entry-group=ENTRY_GROUP
The name of entry link to use.

To set the entry-group attribute:

  • provide the argument entry_link on the command line with a fully specified name;
  • provide the argument --entry-group on the command line.
--location=LOCATION
The location of the Dataplex resource.

To set the location attribute:

  • provide the argument entry_link on the command line with a fully specified name;
  • provide the argument --location on the command line;
  • set the property dataplex/location.
FLAGS
--update-aspects=YAML_OR_JSON_FILE
Path to a YAML or JSON file containing Aspects to add or update for the EntryLink.

When this flag is specified, only Aspects referenced in the file are going to be added or updated. This does not remove other Aspects from the EntryLink.

The file content must be a map where keys are in the format ASPECT_TYPE. Paths are not allowed in the keys for EntryLink aspects.

Values in the map represent the Aspect's content, which must conform to the template defined for the given ASPECT_TYPE. Each Aspect is fully replaced.

ASPECT_TYPE must be in the format PROJECT_ID.LOCATION.ASPECT_TYPE_ID.

Example YAML format: 

  project-id1.us-central1.my-aspect-type1:
    data:
      aspectField1: someValue
      aspectField2: someOtherValue
  project-id2.us-central1.my-aspect-type2:
    data:
      aspectField3: someValue3
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.