1
0
Fork 0
mirror of https://github.com/imjasonh/gcloud-help synced 2026-07-20 04:58:26 +00:00

gcloud: Wed Oct 26 10:52:11 UTC 2022

This commit is contained in:
Automated 2022-10-26 10:52:11 +00:00
parent 5c08d21169
commit 235c67283b
Failed to extract signature
215 changed files with 6787 additions and 1005 deletions

View file

@ -0,0 +1,96 @@
NAME
gcloud alpha dataplex content add-iam-policy-binding - adds IAM policy
binding to a Dataplex Content
SYNOPSIS
gcloud alpha dataplex content add-iam-policy-binding
(CONTENT : --lake=LAKE --location=LOCATION) --member=PRINCIPAL
--role=ROLE [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(ALPHA) Adds IAM policy binding to a Dataplex Content.
EXAMPLES
To add an IAM policy binding for the role of roles/dataplex.viewer for the
user 'testuser@gmail.com' to content test-content within lake test-lake in
location us-central, run:
$ gcloud alpha dataplex content add-iam-policy-binding \
test-content --project=test-project --location=us-central1 \
--lake=test-lake --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
Content resource - The Content 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 content 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.
CONTENT
ID of the content or fully qualified identifier for the content. To
set the content attribute:
▸ provide the argument content on the command line.
This positional argument must be specified if any of the other
arguments in this group are specified.
--lake=LAKE
The identifier of the Dataplex lake resource. To set the lake
attribute:
▸ provide the argument content on the command line with a fully
specified name;
▸ provide the argument --lake on the command line.
--location=LOCATION
The location of the Dataplex resource. To set the location attribute:
▸ provide the argument content 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 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. This variant is also available:
$ gcloud dataplex content add-iam-policy-binding

View file

@ -0,0 +1,107 @@
NAME
gcloud alpha dataplex content create - creating a content
SYNOPSIS
gcloud alpha dataplex content create --data-text=DATA_TEXT --path=PATH
(--kernel-type=KERNEL_TYPE | --query-engine=QUERY_ENGINE)
(--lake=LAKE : --location=LOCATION) [--description=DESCRIPTION]
[--labels=[KEY=VALUE,...]] [--validate-only] [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(ALPHA) Creating a content.
EXAMPLES
To create a Dataplex content test-content of type notebook within lake
test-lake in location us-central1.
$ gcloud alpha dataplex content create --project=test-project \
--location=us-central1 --lake=test-lake --kernel-type=PYTHON3 \
--data-text='' --path='test-content'
REQUIRED FLAGS
--data-text=DATA_TEXT
Content data in string format
--path=PATH
The path for the Content file, represented as directory structure
Sql script or notebook related configurations.
Exactly one of these must be specified:
Notebook related configurations.
--kernel-type=KERNEL_TYPE
Kernel Type of the notebook. KERNEL_TYPE must be (currently only
one value is supported):
PYTHON3
python3
Sql script related configurations.
--query-engine=QUERY_ENGINE
Query Engine to be used for the Sql Query. QUERY_ENGINE must be
(currently only one value is supported):
SPARK
spark
Lakes resource - Arguments and flags that define the Dataplex lake you
want to create a Content 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 --lake 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.
--lake=LAKE
ID of the lakes or fully qualified identifier for the lakes. To set
the lake attribute:
▸ provide the argument --lake on the command line.
This flag 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 --lake on the command line with a fully
specified name;
▸ provide the argument --location on the command line;
▸ set the property dataplex/location.
OPTIONAL FLAGS
--description=DESCRIPTION
Description of the Content
--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.
--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 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. This variant is also available:
$ gcloud dataplex content create

View file

@ -0,0 +1,76 @@
NAME
gcloud alpha dataplex content delete - delete a Dataplex Content Resource
SYNOPSIS
gcloud alpha dataplex content delete
(CONTENT : --lake=LAKE --location=LOCATION) [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(ALPHA) Delete a Dataplex Content resource based on project, location,
lake, and content.
EXAMPLES
To delete a content test-content in lake test-lake under location
us-central1 inside project test-project, run :
$ gcloud alpha dataplex content delete --project=test-project \
--location=us-central1 --lake=test-lake test-content
POSITIONAL ARGUMENTS
Content resource - Arguments and flags that define the Dataplex Content
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 content 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.
CONTENT
ID of the content or fully qualified identifier for the content. To
set the content attribute:
▸ provide the argument content on the command line.
This positional argument must be specified if any of the other
arguments in this group are specified.
--lake=LAKE
Identifier of the Dataplex lake resource.
To set the lake attribute:
▸ provide the argument content on the command line with a fully
specified name;
▸ provide the argument --lake on the command line.
--location=LOCATION
Location of the Dataplex resource.
To set the location attribute:
▸ provide the argument content 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 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. This variant is also available:
$ gcloud dataplex content delete

View file

@ -0,0 +1,89 @@
NAME
gcloud alpha dataplex content describe - retrieve a Dataplex Content
Resource
SYNOPSIS
gcloud alpha dataplex content describe
(CONTENT : --lake=LAKE --location=LOCATION)
[--view=VIEW; default="basic"] [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(ALPHA) Get a Dataplex Content resource based on project, location, lake,
and content.
EXAMPLES
To describe a Dataplex Content test-content in project test-project under
loaction us-central1 inside project test-project, run:
$ gcloud alpha dataplex content describe test-content \
--project=test-project --location=us-central1 --lake=test-lake
POSITIONAL ARGUMENTS
Content resource - Arguments and flags that define the Dataplex Content
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 content 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.
CONTENT
ID of the content or fully qualified identifier for the content. To
set the content attribute:
▸ provide the argument content on the command line.
This positional argument must be specified if any of the other
arguments in this group are specified.
--lake=LAKE
Identifier of the Dataplex lake resource.
To set the lake attribute:
▸ provide the argument content on the command line with a fully
specified name;
▸ provide the argument --lake on the command line.
--location=LOCATION
Location of the Dataplex resource.
To set the location attribute:
▸ provide the argument content on the command line with a fully
specified name;
▸ provide the argument --location on the command line;
▸ set the property dataplex/location.
FLAGS
--view=VIEW; default="basic"
There are two possible views, 'basic' and 'full'. The default view is
'basic'. VIEW must be one of:
basic
Does not include the Content data in response.
full
Includes the content data in response.
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 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. This variant is also available:
$ gcloud dataplex content describe

View file

@ -0,0 +1,105 @@
NAME
gcloud alpha dataplex content get-iam-policy - retrieve the IAM policy for
a Dataplex Content
SYNOPSIS
gcloud alpha dataplex content get-iam-policy
(CONTENT : --lake=LAKE --location=LOCATION) [--filter=EXPRESSION]
[--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]]
[GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(ALPHA) Get a Dataplex Content Iam Policy based on project_id, location,
lake_id, and contents_id.
EXAMPLES
To get the IAM policy of a Dataplex Content test-content in project
test-project under loaction us-central1 inside lake test-lake, run:
$ gcloud alpha dataplex content get-iam-policy test-content \
--project=test-project --location=us-central1 --lake=test-lake
POSITIONAL ARGUMENTS
Content resource - Arguments and flags that define the Dataplex contents
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 content 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.
CONTENT
ID of the content or fully qualified identifier for the content. To
set the content attribute:
▸ provide the argument content on the command line.
This positional argument must be specified if any of the other
arguments in this group are specified.
--lake=LAKE
Identifier of the Dataplex lake resource.
To set the lake attribute:
▸ provide the argument content on the command line with a fully
specified name;
▸ provide the argument --lake on the command line.
--location=LOCATION
Location of the Dataplex resource.
To set the location attribute:
▸ provide the argument content 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 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. This variant is also available:
$ gcloud dataplex content get-iam-policy

View file

@ -0,0 +1,54 @@
NAME
gcloud alpha dataplex content - manage Dataplex Content
SYNOPSIS
gcloud alpha dataplex content COMMAND [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(ALPHA) Manage Dataplex Content.
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
(ALPHA) Adds IAM policy binding to a Dataplex Content.
create
(ALPHA) Creating a content.
delete
(ALPHA) Delete a Dataplex Content Resource.
describe
(ALPHA) Retrieve a Dataplex Content Resource.
get-iam-policy
(ALPHA) Retrieve the IAM policy for a Dataplex Content.
list
(ALPHA) List Dataplex Content Resources.
remove-iam-policy-binding
(ALPHA) Removes IAM policy binding from a Dataplex Content.
set-iam-policy
(ALPHA) Set the IAM policy to a Dataplex Content as defined in a JSON
or YAML file.
update
(ALPHA) Update a Dataplex Content Resource with the given
configurations.
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. This variant is also available:
$ gcloud dataplex content

View file

@ -0,0 +1,101 @@
NAME
gcloud alpha dataplex content list - list Dataplex Content Resources
SYNOPSIS
gcloud alpha dataplex content list (--lake=LAKE : --location=LOCATION)
[--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE]
[--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(ALPHA) List Dataplex Content resource based on project, location, and
lake. Currently list does not support project/{project_id}/.../ notation.
EXAMPLES
To list all Dataplex Content resource in lake test-lake under location
us-central1 inside project test-project, run :
$ gcloud alpha dataplex content list --project=test-project \
--location=us-central1 --lake=test-lake
REQUIRED FLAGS
Lake resource - Arguments and flags that define the Dataplex Content you
want to list. 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 --lake 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.
--lake=LAKE
ID of the lake or fully qualified identifier for the lake. To set the
lake attribute:
▸ provide the argument --lake on the command line.
This flag 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 --lake 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.
--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 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. This variant is also available:
$ gcloud dataplex content list

View file

@ -0,0 +1,97 @@
NAME
gcloud alpha dataplex content remove-iam-policy-binding - removes IAM
policy binding from a Dataplex Content
SYNOPSIS
gcloud alpha dataplex content remove-iam-policy-binding
(CONTENT : --lake=LAKE --location=LOCATION) --member=PRINCIPAL
--role=ROLE [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(ALPHA) Removes IAM policy binding from a Dataplex Content.
EXAMPLES
To remove an IAM policy binding for the role roles/dataplex.viewer for the
user testuser@gmail.com from a content test-content within lake test-lake
in location us-central1, run:
$ gcloud alpha dataplex content remove-iam-policy-binding \
test-content --project=test-project --location=us-central1 \
--lake=test-lake --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
Content resource - The Content 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 content 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.
CONTENT
ID of the content or fully qualified identifier for the content. To
set the content attribute:
▸ provide the argument content on the command line.
This positional argument must be specified if any of the other
arguments in this group are specified.
--lake=LAKE
The identifier of the Dataplex lake resource. To set the lake
attribute:
▸ provide the argument content on the command line with a fully
specified name;
▸ provide the argument --lake on the command line.
--location=LOCATION
The location of the Dataplex resource. To set the location attribute:
▸ provide the argument content 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 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. This variant is also available:
$ gcloud dataplex content remove-iam-policy-binding

View file

@ -0,0 +1,81 @@
NAME
gcloud alpha dataplex content set-iam-policy - set the IAM policy to a
Dataplex Content as defined in a JSON or YAML file
SYNOPSIS
gcloud alpha dataplex content set-iam-policy
(CONTENT : --lake=LAKE --location=LOCATION) POLICY_FILE
[GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(ALPHA) 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 content test-content within lake
test-lake in location us-central1 and :
$ gcloud alpha dataplex content set-iam-policy test-content \
--project=test-project --location=us-central1 --lake=test-lake \
policy.json
where policy.json is the relative path to the json file.
POSITIONAL ARGUMENTS
Content resource - The Content 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 content 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.
CONTENT
ID of the content or fully qualified identifier for the content. To
set the content attribute:
▸ provide the argument content on the command line.
This positional argument must be specified if any of the other
arguments in this group are specified.
--lake=LAKE
The identifier of the Dataplex lake resource. To set the lake
attribute:
▸ provide the argument content on the command line with a fully
specified name;
▸ provide the argument --lake on the command line.
--location=LOCATION
The location of the Dataplex resource. To set the location attribute:
▸ provide the argument content 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 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. This variant is also available:
$ gcloud dataplex content set-iam-policy

View file

@ -0,0 +1,117 @@
NAME
gcloud alpha dataplex content update - update a Dataplex Content Resource
with the given configurations
SYNOPSIS
gcloud alpha dataplex content update
(CONTENT : --lake=LAKE --location=LOCATION) [--data-text=DATA_TEXT]
[--description=DESCRIPTION] [--labels=[KEY=VALUE,...]] [--path=PATH]
[--validate-only]
[--kernel-type=KERNEL_TYPE | --query-engine=QUERY_ENGINE]
[GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(ALPHA) Update a Dataplex Content Resource with the given configurations.
EXAMPLES
To update a Dataplex content test-content in project test-project within
lake test-lake in location us-central1 and change the description to
Updated Description, run:
$ gcloud alpha dataplex content update test-content \
--project=test-project --location=us-central1 --lake=test-lake \
--description='Updated Description'
POSITIONAL ARGUMENTS
Content resource - The Content to Update a Content 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 content 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.
CONTENT
ID of the content or fully qualified identifier for the content. To
set the content attribute:
▸ provide the argument content on the command line.
This positional argument must be specified if any of the other
arguments in this group are specified.
--lake=LAKE
The identifier of the Dataplex lake resource. To set the lake
attribute:
▸ provide the argument content on the command line with a fully
specified name;
▸ provide the argument --lake on the command line.
--location=LOCATION
The location of the Dataplex resource. To set the location attribute:
▸ provide the argument content on the command line with a fully
specified name;
▸ provide the argument --location on the command line;
▸ set the property dataplex/location.
FLAGS
--data-text=DATA_TEXT
Content data in string format
--description=DESCRIPTION
Description of the Content
--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.
--path=PATH
The path for the Content file, represented as directory structure
--validate-only
Validate the update action, but don't actually perform it.
Sql script or notebook related configurations.
At most one of these can be specified:
Notebook related configurations.
--kernel-type=KERNEL_TYPE
Kernel Type of the notebook. KERNEL_TYPE must be (currently only
one value is supported):
PYTHON3
python3
Sql script related configurations.
--query-engine=QUERY_ENGINE
Query Engine to be used for the Sql Query. QUERY_ENGINE must be
(currently only one value is supported):
SPARK
spark
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. This variant is also available:
$ gcloud dataplex content update