imjasonh/gcloud-help
1
0
Fork 0
mirror of https://github.com/imjasonh/gcloud-help synced 2026-07-15 17:35:31 +00:00
Code Activity

gcloud: Thu May 30 09:26:18 UTC 2024

Browse source
This commit is contained in:
Automated 2024-05-30 09:26:18 +00:00
parent e617a432f4
commit 595ac8640a
232 changed files with 10919 additions and 274 deletions
Download patch file Download diff file Expand all files Collapse all files

92
gcloud/dataplex/entry-groups/add-iam-policy-binding Normal file
View file

@ -0,0 +1,92 @@
NAME
gcloud dataplex entry-groups add-iam-policy-binding - add IAM policy
binding to a Dataplex Entry Group
SYNOPSIS
gcloud dataplex entry-groups add-iam-policy-binding
(ENTRY_GROUP : --location=LOCATION) --member=PRINCIPAL --role=ROLE
[GCLOUD_WIDE_FLAG ...]
DESCRIPTION
Add IAM policy binding to a Dataplex Entry Group.
EXAMPLES
To add an IAM policy binding for the role of roles/dataplex.viewer for the
user test-user@gmail.com to Entry Group test-entry-group in project
test-project and in location us-central1, run:
$ gcloud dataplex entry-groups add-iam-policy-binding \
test-entry-group --project=test-project --location=us-central1 \
--role=roles/dataplex.viewer --member=user:foo@gmail.com
See https://cloud.google.com/dataplex/docs/iam-roles for details of policy
role and member types.
POSITIONAL ARGUMENTS
Entry group resource - Arguments and flags that define the Dataplex entry
group you want to add IAM policy binding to. 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_group 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_GROUP
ID of the entry group or fully qualified identifier for the entry
group.
To set the entry_group attribute:
▸ provide the argument entry_group on the command line.
This positional argument must be specified if any of the other
arguments in this group are specified.
--location=LOCATION
The location of the Dataplex resource.
To set the location attribute:
▸ provide the argument entry_group on the command line with a fully
specified name;
▸ provide the argument --location on the command line;
▸ set the property dataplex/location.
REQUIRED FLAGS
--member=PRINCIPAL
The principal to add the binding for. Should be of the form
user|group|serviceAccount:email or domain:domain.
Examples: user:test-user@gmail.com, group:admins@example.com,
serviceAccount:test123@example.domain.com, or
domain:example.domain.com.
Some resources also accept the following special values:
◆ allUsers - Special identifier that represents anyone who is on the
internet, with or without a Google account.
◆ allAuthenticatedUsers - Special identifier that represents anyone
who is authenticated with a Google account or a service account.
--role=ROLE
Role name to assign to the principal. The role name is the complete
path of a predefined role, such as roles/logging.viewer, or the role ID
for a custom role, such as
organizations/{ORGANIZATION_ID}/roles/logging.viewer.
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 variant is also available:
$ gcloud alpha dataplex entry-groups add-iam-policy-binding

92
gcloud/dataplex/entry-groups/create Normal file
View file

@ -0,0 +1,92 @@
NAME
gcloud dataplex entry-groups create - create a Dataplex Entry Group
SYNOPSIS
gcloud dataplex entry-groups create (ENTRY_GROUP : --location=LOCATION)
[--description=DESCRIPTION] [--display-name=DISPLAY_NAME]
[--labels=[KEY=VALUE,...]] [--async | --validate-only]
[GCLOUD_WIDE_FLAG ...]
DESCRIPTION
Entry Group acts as a logical container used to organize Entries.
EXAMPLES
To create Entry Group test-entry-group in project test-dataplex at location
us-central1, with description test description and displayName test display
name, run:
$ gcloud dataplex entry-groups create test-entry-group \
--location=us-central1 --project=test-project \
--description='test description' \
--display-name='test display name'
POSITIONAL ARGUMENTS
Entry group resource - Arguments and flags that define the Dataplex entry
group you want to create. 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_group 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_GROUP
ID of the entry group or fully qualified identifier for the entry
group.
To set the entry_group attribute:
▸ provide the argument entry_group on the command line.
This positional argument must be specified if any of the other
arguments in this group are specified.
--location=LOCATION
The location of the Dataplex resource.
To set the location attribute:
▸ provide the argument entry_group on the command line with a fully
specified name;
▸ provide the argument --location on the command line;
▸ set the property dataplex/location.
FLAGS
--description=DESCRIPTION
Description of the Entry Group.
--display-name=DISPLAY_NAME
Display name of the Entry Group.
--labels=[KEY=VALUE,...]
List of label KEY=VALUE pairs to add.
Keys must start with a lowercase character and contain only hyphens
(-), underscores (_), lowercase characters, and numbers. Values must
contain only hyphens (-), underscores (_), lowercase characters, and
numbers.
At most one of these can be specified:
--async
Return immediately, without waiting for the operation in progress to
complete.
--validate-only
Validate the create action, but don't actually perform it.
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 variant is also available:
$ gcloud alpha dataplex entry-groups create

75
gcloud/dataplex/entry-groups/delete Normal file
View file

@ -0,0 +1,75 @@
NAME
gcloud dataplex entry-groups delete - delete a Dataplex Entry Group
SYNOPSIS
gcloud dataplex entry-groups delete (ENTRY_GROUP : --location=LOCATION)
[--async] [--etag=ETAG] [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
Delete a Dataplex Entry Group.
EXAMPLES
To delete Entry Group test-entry-group in project test-project and in
location us-central1, run:
$ gcloud dataplex entry-groups delete test-entry-group \
--location=us-central1 --project=test-project
POSITIONAL ARGUMENTS
Entry group resource - Arguments and flags that define the Dataplex Entry
Group you want to delete. 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_group on the command line with a fully
specified name;
◆ set the property core/project;
◆ provide the argument --project on the command line.
This must be specified.
ENTRY_GROUP
ID of the entry group or fully qualified identifier for the entry
group.
To set the entry_group attribute:
▸ provide the argument entry_group on the command line.
This positional argument must be specified if any of the other
arguments in this group are specified.
--location=LOCATION
Location of the Dataplex resource.
To set the location attribute:
▸ provide the argument entry_group on the command line with a fully
specified name;
▸ provide the argument --location on the command line;
▸ set the property dataplex/location.
FLAGS
--async
Return immediately, without waiting for the operation in progress to
complete.
--etag=ETAG
etag for the Entry Group you want to delete.
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.
API REFERENCE
This command uses the dataplex/v1 API. The full documentation for this API
can be found at: https://cloud.google.com/dataplex/docs
NOTES
This variant is also available:
$ gcloud alpha dataplex entry-groups delete

67
gcloud/dataplex/entry-groups/describe Normal file
View file

@ -0,0 +1,67 @@
NAME
gcloud dataplex entry-groups describe - describe a Dataplex Entry Group
SYNOPSIS
gcloud dataplex entry-groups describe (ENTRY_GROUP : --location=LOCATION)
[GCLOUD_WIDE_FLAG ...]
DESCRIPTION
Displays all details of an Entry Group given a valid Entry Group ID.
EXAMPLES
To describe a Dataplex Entry Group test-entry-group in location us-central1
and in project test-project, run:
$ gcloud dataplex entry-groups describe test-entry-group \
--location=us-central1 --project=test-project
POSITIONAL ARGUMENTS
Entry group resource - Arguments and flags that define the Dataplex Entry
Group you want to retrieve. 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_group on the command line with a fully
specified name;
◆ set the property core/project;
◆ provide the argument --project on the command line.
This must be specified.
ENTRY_GROUP
ID of the entry group or fully qualified identifier for the entry
group.
To set the entry_group attribute:
▸ provide the argument entry_group on the command line.
This positional argument must be specified if any of the other
arguments in this group are specified.
--location=LOCATION
Location of the Dataplex resource.
To set the location attribute:
▸ provide the argument entry_group on the command line with a fully
specified name;
▸ provide the argument --location on the command line;
▸ set the property dataplex/location.
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.
API REFERENCE
This command uses the dataplex/v1 API. The full documentation for this API
can be found at: https://cloud.google.com/dataplex/docs
NOTES
This variant is also available:
$ gcloud alpha dataplex entry-groups describe

99
gcloud/dataplex/entry-groups/get-iam-policy Normal file
View file

@ -0,0 +1,99 @@
NAME
gcloud dataplex entry-groups get-iam-policy - retrieve a Dataplex Entry
Group IAM policy
SYNOPSIS
gcloud dataplex entry-groups get-iam-policy
(ENTRY_GROUP : --location=LOCATION) [--filter=EXPRESSION]
[--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]]
[GCLOUD_WIDE_FLAG ...]
DESCRIPTION
Displays the IAM policy associated with a Dataplex Entry Group resource. If
formatted as JSON, the output can be edited and used as a policy file for
set-iam-policy. The output includes an "etag" field identifying the version
emitted and allowing detection of concurrent policy updates.
EXAMPLES
To get the IAM policy of a Dataplex Entry Group test-entry-group in project
test-project under location us-central1, run:
$ gcloud dataplex entry-groups get-iam-policy test-entry-group \
--project=test-project --location=us-central1
POSITIONAL ARGUMENTS
Entry group resource - Arguments and flags that define the Dataplex Entry
Group IAM policy you want to retrieve. 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_group on the command line with a fully
specified name;
◆ set the property core/project;
◆ provide the argument --project on the command line.
This must be specified.
ENTRY_GROUP
ID of the entry group or fully qualified identifier for the entry
group.
To set the entry_group attribute:
▸ provide the argument entry_group on the command line.
This positional argument must be specified if any of the other
arguments in this group are specified.
--location=LOCATION
Location of the Dataplex resource.
To set the location attribute:
▸ provide the argument entry_group on the command line with a fully
specified name;
▸ provide the argument --location on the command line;
▸ set the property dataplex/location.
LIST COMMAND FLAGS
--filter=EXPRESSION
Apply a Boolean filter EXPRESSION to each resource item to be listed.
If the expression evaluates True, then that item is listed. For more
details and examples of filter expressions, run $ gcloud topic filters.
This flag interacts with other flags that are applied in this order:
--flatten, --sort-by, --filter, --limit.
--limit=LIMIT
Maximum number of resources to list. The default is unlimited. This
flag interacts with other flags that are applied in this order:
--flatten, --sort-by, --filter, --limit.
--page-size=PAGE_SIZE
Some services group resource list output into pages. This flag
specifies the maximum number of resources per page. The default is
determined by the service if it supports paging, otherwise it is
unlimited (no paging). Paging may be applied before or after --filter
and --limit depending on the service.
--sort-by=[FIELD,...]
Comma-separated list of resource field key names to sort by. The
default order is ascending. Prefix a field with ``~'' for descending
order on that field. This flag interacts with other flags that are
applied in this order: --flatten, --sort-by, --filter, --limit.
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.
API REFERENCE
This command uses the dataplex/v1 API. The full documentation for this API
can be found at: https://cloud.google.com/dataplex/docs
NOTES
This variant is also available:
$ gcloud alpha dataplex entry-groups get-iam-policy

50
gcloud/dataplex/entry-groups/help Normal file
View file

@ -0,0 +1,50 @@
NAME
gcloud dataplex entry-groups - manage Dataplex Entry Groups
SYNOPSIS
gcloud dataplex entry-groups COMMAND [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
Manage Dataplex Entry Groups.
GCLOUD WIDE FLAGS
These flags are available to all commands: --help.
Run $ gcloud help for details.
COMMANDS
COMMAND is one of the following:
add-iam-policy-binding
Add IAM policy binding to a Dataplex Entry Group.
create
Create a Dataplex Entry Group.
delete
Delete a Dataplex Entry Group.
describe
Describe a Dataplex Entry Group.
get-iam-policy
Retrieve a Dataplex Entry Group IAM policy.
list
List Dataplex Entry Groups.
remove-iam-policy-binding
Remove IAM policy binding from a Dataplex Entry Group.
set-iam-policy
Set an IAM policy binding for a Dataplex Entry Group as defined in a
JSON or YAML file.
update
Update a Dataplex Entry Group.
NOTES
This variant is also available:
$ gcloud alpha dataplex entry-groups

88
gcloud/dataplex/entry-groups/list Normal file
View file

@ -0,0 +1,88 @@
NAME
gcloud dataplex entry-groups list - list Dataplex Entry Groups
SYNOPSIS
gcloud dataplex entry-groups list [--location=LOCATION]
[--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE]
[--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
List Dataplex Entry Groups based on project and location.
gcloud dataplex entry-groups list --project={project_id}
--location={location}
EXAMPLES
To list Entry Groups in project test-dataplex at location us-central1
$ gcloud dataplex entry-groups list --location=us-central1 \
--project=test-dataplex
FLAGS
Location resource - Location to list Entry Groups in. This represents a
Cloud 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 --location on the command line with a fully
specified name;
◆ set the property dataplex/location with a fully specified name;
◆ set the property core/project;
◆ provide the argument --project on the command line.
--location=LOCATION
ID of the location or fully qualified identifier for the location.
To set the location attribute:
▸ provide the argument --location on the command line;
▸ set the property dataplex/location.
LIST COMMAND FLAGS
--filter=EXPRESSION
Apply a Boolean filter EXPRESSION to each resource item to be listed.
If the expression evaluates True, then that item is listed. For more
details and examples of filter expressions, run $ gcloud topic filters.
This flag interacts with other flags that are applied in this order:
--flatten, --sort-by, --filter, --limit.
--limit=LIMIT
Maximum number of resources to list. The default is unlimited. This
flag interacts with other flags that are applied in this order:
--flatten, --sort-by, --filter, --limit.
--page-size=PAGE_SIZE
Some services group resource list output into pages. This flag
specifies the maximum number of resources per page. The default is
determined by the service if it supports paging, otherwise it is
unlimited (no paging). Paging may be applied before or after --filter
and --limit depending on the service.
--sort-by=[FIELD,...]
Comma-separated list of resource field key names to sort by. The
default order is ascending. Prefix a field with ``~'' for descending
order on that field. This flag interacts with other flags that are
applied in this order: --flatten, --sort-by, --filter, --limit.
--uri
Print a list of resource URIs instead of the default output, and change
the command output to a list of URIs. If this flag is used with
--format, the formatting is applied on this URI list. To display URIs
alongside other keys instead, use the uri() transform.
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.
API REFERENCE
This command uses the dataplex/v1 API. The full documentation for this API
can be found at: https://cloud.google.com/dataplex/docs
NOTES
This variant is also available:
$ gcloud alpha dataplex entry-groups list

93
gcloud/dataplex/entry-groups/remove-iam-policy-binding Normal file
View file

@ -0,0 +1,93 @@
NAME
gcloud dataplex entry-groups remove-iam-policy-binding - remove IAM policy
binding from a Dataplex Entry Group
SYNOPSIS
gcloud dataplex entry-groups remove-iam-policy-binding
(ENTRY_GROUP : --location=LOCATION) --member=PRINCIPAL --role=ROLE
[GCLOUD_WIDE_FLAG ...]
DESCRIPTION
Remove IAM policy binding from a Dataplex Entry Group.
EXAMPLES
To remove an IAM policy binding for the role roles/dataplex.viewer for the
user testuser@gmail.com from an entry group test-entry-group in project
test-project and in location us-central1, run:
$ gcloud dataplex entry-groups remove-iam-policy-binding \
test-entry-group --project=test-project --location=us-central1 \
--role=roles/dataplex.viewer --member=user:testuser@gmail.com
See https://cloud.google.com/dataplex/docs/iam-roles for details of policy
role and member types.
POSITIONAL ARGUMENTS
Entry group resource - Arguments and flags that define the Dataplex entry
group you want to remove IAM policy binding from 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_group 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_GROUP
ID of the entry group or fully qualified identifier for the entry
group.
To set the entry_group attribute:
▸ provide the argument entry_group on the command line.
This positional argument must be specified if any of the other
arguments in this group are specified.
--location=LOCATION
The location of the Dataplex resource.
To set the location attribute:
▸ provide the argument entry_group on the command line with a fully
specified name;
▸ provide the argument --location on the command line;
▸ set the property dataplex/location.
REQUIRED FLAGS
--member=PRINCIPAL
The principal to remove the binding for. Should be of the form
user|group|serviceAccount:email or domain:domain.
Examples: user:test-user@gmail.com, group:admins@example.com,
serviceAccount:test123@example.domain.com, or
domain:example.domain.com.
Deleted principals have an additional deleted: prefix and a ?uid=UID
suffix, where UID is a unique identifier for the principal. Example:
deleted:user:test-user@gmail.com?uid=123456789012345678901.
Some resources also accept the following special values:
◆ allUsers - Special identifier that represents anyone who is on the
internet, with or without a Google account.
◆ allAuthenticatedUsers - Special identifier that represents anyone
who is authenticated with a Google account or a service account.
--role=ROLE
The role to remove the principal from.
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 variant is also available:
$ gcloud alpha dataplex entry-groups remove-iam-policy-binding

75
gcloud/dataplex/entry-groups/set-iam-policy Normal file
View file

@ -0,0 +1,75 @@
NAME
gcloud dataplex entry-groups set-iam-policy - set an IAM policy binding for
a Dataplex Entry Group as defined in a JSON or YAML file
SYNOPSIS
gcloud dataplex entry-groups set-iam-policy
(ENTRY_GROUP : --location=LOCATION) POLICY_FILE [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
See https://cloud.google.com/iam/docs/managing-policies for details of the
policy file format and contents.
EXAMPLES
The following command will read an IAM policy defined in a JSON file
policy.json and set it for the Dataplex Entry Group test-entry-group in
project test-project and in location us-central1:
$ gcloud dataplex entry-groups set-iam-policy test-entry-group \
--project=test-project --location=us-central1 policy.json
where policy.json is the relative path to the JSON file.
POSITIONAL ARGUMENTS
Entry group resource - Arguments and flags that define the Dataplex entry
group you want to set IAM policy to. 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_group 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_GROUP
ID of the entry group or fully qualified identifier for the entry
group.
To set the entry_group attribute:
▸ provide the argument entry_group on the command line.
This positional argument must be specified if any of the other
arguments in this group are specified.
--location=LOCATION
The location of the Dataplex resource.
To set the location attribute:
▸ provide the argument entry_group on the command line with a fully
specified name;
▸ provide the argument --location on the command line;
▸ set the property dataplex/location.
POLICY_FILE
Path to a local JSON or YAML formatted file containing a valid policy.
The output of the get-iam-policy command is a valid file, as is any
JSON or YAML file conforming to the structure of a Policy
(https://cloud.google.com/iam/reference/rest/v1/Policy).
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 variant is also available:
$ gcloud alpha dataplex entry-groups set-iam-policy

95
gcloud/dataplex/entry-groups/update Normal file
View file

@ -0,0 +1,95 @@
NAME
gcloud dataplex entry-groups update - update a Dataplex Entry Group
SYNOPSIS
gcloud dataplex entry-groups update (ENTRY_GROUP : --location=LOCATION)
[--description=DESCRIPTION] [--display-name=DISPLAY_NAME] [--etag=ETAG]
[--labels=[KEY=VALUE,...]] [--async | --validate-only]
[GCLOUD_WIDE_FLAG ...]
DESCRIPTION
Update a Dataplex Entry Group.
EXAMPLES
To update Entry Group test-entry-group in project test-project at location
us-central1, with description updated description and display name updated
display name, run:
$ gcloud dataplex entry-groups update test-entry-group \
--location=us-central1 --project=test-project \
--description='updated description' \
--display-name='updated display name'
POSITIONAL ARGUMENTS
Entry group resource - Arguments and flags that define the Dataplex entry
group 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_group 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_GROUP
ID of the entry group or fully qualified identifier for the entry
group.
To set the entry_group attribute:
▸ provide the argument entry_group on the command line.
This positional argument must be specified if any of the other
arguments in this group are specified.
--location=LOCATION
The location of the Dataplex resource.
To set the location attribute:
▸ provide the argument entry_group on the command line with a fully
specified name;
▸ provide the argument --location on the command line;
▸ set the property dataplex/location.
FLAGS
--description=DESCRIPTION
Description of the Entry Group.
--display-name=DISPLAY_NAME
Display name of the Entry Group.
--etag=ETAG
etag value for particular Entry Group.
--labels=[KEY=VALUE,...]
List of label KEY=VALUE pairs to add.
Keys must start with a lowercase character and contain only hyphens
(-), underscores (_), lowercase characters, and numbers. Values must
contain only hyphens (-), underscores (_), lowercase characters, and
numbers.
At most one of these can be specified:
--async
Return immediately, without waiting for the operation in progress to
complete.
--validate-only
Validate the update action, but don't actually perform it.
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 variant is also available:
$ gcloud alpha dataplex entry-groups update