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

gcloud: Wed Mar 6 09:53:10 UTC 2024

Browse source
This commit is contained in:
Automated 2024-03-06 09:53:10 +00:00
parent 37dd57701a
commit 7f632e0c5d
115 changed files with 5800 additions and 308 deletions
Download patch file Download diff file Expand all files Collapse all files

5
gcloud/beta/artifacts/docker/upgrade/help
View file

@ -25,5 +25,8 @@ COMMANDS
Artifact Registry upgrade.
NOTES
This command is currently in beta and might change without notice.
This command is currently in beta and might change without notice. This
variant is also available:
$ gcloud artifacts docker upgrade

3
gcloud/beta/bigtable/help
View file

@ -33,6 +33,9 @@ GROUPS
operations
(BETA) Manage Cloud Bigtable operations.
tables
(BETA) Query Cloud Bigtable tables.
NOTES
This command is currently in beta and might change without notice. These
variants are also available:

15
gcloud/beta/bigtable/instances/tables/create
View file

@ -6,7 +6,8 @@ SYNOPSIS
gcloud beta bigtable instances tables create (TABLE : --instance=INSTANCE)
--column-families=[COLUMN_FAMILIES,...]
[--change-stream-retention-period=CHANGE_STREAM_RETENTION_PERIOD]
[--deletion-protection] [--splits=[SPLITS,...]] [GCLOUD_WIDE_FLAG ...]
[--deletion-protection] [--enable-automated-backup]
[--splits=[SPLITS,...]] [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(BETA) Create a new Cloud Bigtable table.
@ -59,6 +60,14 @@ EXAMPLES
--instance=my-instance --column-families="my-family" \
--no-deletion-protection
To create a table my-table with automated backup policy
(retention_period=72h, frequency=24h) enabled in instance my-instance with
a column family my-family, run:
$ gcloud beta bigtable instances tables create my-table \
--instance=my-instance --column-families="my-family" \
--enable-automated-backup
POSITIONAL ARGUMENTS
Table resource - Cloud Bigtable table to create. The arguments in this
group can be used to specify the attributes of this resource. (NOTE) Some
@ -107,6 +116,10 @@ OPTIONAL FLAGS
--deletion-protection
Once specified, the table is deletion protected.
--enable-automated-backup
Once set, enables the default automated backup policy
(retention_period=72h, frequency=24h) for the table.
--splits=[SPLITS,...]
Row keys where the table should initially be split. For example:
car,key

21
gcloud/beta/bigtable/instances/tables/update
View file

@ -4,7 +4,8 @@ NAME
SYNOPSIS
gcloud beta bigtable instances tables update (TABLE : --instance=INSTANCE)
[--async] [--deletion-protection]
[--async] [--deletion-protection] [--disable-automated-backup]
[--enable-automated-backup]
[--change-stream-retention-period=CHANGE_STREAM_RETENTION_PERIOD
| --clear-change-stream-retention-period] [GCLOUD_WIDE_FLAG ...]
@ -34,6 +35,17 @@ EXAMPLES
$ gcloud beta bigtable instances tables update my-table \
--instance=my-instance --clear-change-stream-retention-period
To enable default automated backup policy (retention_period=72h,
frequency=24h), run:
$ gcloud beta bigtable instances tables update my-table \
--instance=my-instance --enable-automated-backup
To disable automated backup: run:
$ gcloud beta bigtable instances tables update my-table \
--instance=my-instance --disable-automated-backup
POSITIONAL ARGUMENTS
Table resource - Cloud Bigtable table to update. The arguments in this
group can be used to specify the attributes of this resource. (NOTE) Some
@ -73,6 +85,13 @@ FLAGS
--deletion-protection
Once specified, the table is deletion protected.
--disable-automated-backup
Once set, disables automated backup policy for the table.
--enable-automated-backup
Once set, enables the default automated backup policy
(retention_period=72h, frequency=24h) for the table.
At most one of these can be specified:
--change-stream-retention-period=CHANGE_STREAM_RETENTION_PERIOD

146
gcloud/beta/bigtable/tables/add-iam-policy-binding Normal file
View file

@ -0,0 +1,146 @@
NAME
gcloud beta bigtable tables add-iam-policy-binding - add an IAM policy
binding to a Cloud Bigtable table
SYNOPSIS
gcloud beta bigtable tables add-iam-policy-binding
(TABLE : --instance=INSTANCE) --member=PRINCIPAL --role=ROLE
[--condition=[KEY=VALUE,...]
| --condition-from-file=CONDITION_FROM_FILE] [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(BETA) Add an IAM policy binding to a Cloud Bigtable table. One binding
consists of a member, a role, and an optional condition.
EXAMPLES
To add an IAM policy binding for the role of 'roles/editor' for the user
'test-user@gmail.com' with table 'my-table' in instance 'my-instance', run:
$ gcloud beta bigtable tables add-iam-policy-binding my-table \
--instance='my-instance' --member='user:test-user@gmail.com' \
--role='roles/editor'
To add an IAM policy binding which expires at the end of the year 2019 for
the role of 'roles/bigtable.admin' and the user 'test-user@gmail.com' with
table 'my-table' in instance 'my-instance', run:
$ gcloud beta bigtable tables add-iam-policy-binding my-table \
--instance='my-instance' --member='user:test-user@gmail.com' \
--role='roles/bigtable.admin' \
--condition='expression=request.time <
timestamp("2020-01-01T00:00:00Z"),title=expires_end_of_2019,descrip\
tion=Expires at midnight on 2019-12-31'
See https://cloud.google.com/iam/docs/managing-policies for details of
policy role and member types.
POSITIONAL ARGUMENTS
Table resource - Cloud Bigtable table to add the 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 table 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.
TABLE
ID of the table or fully qualified identifier for the table.
To set the table attribute:
▸ provide the argument table on the command line.
This positional argument must be specified if any of the other
arguments in this group are specified.
--instance=INSTANCE
Name of the Cloud Bigtable instance.
To set the instance attribute:
▸ provide the argument table on the command line with a fully
specified name;
▸ provide the argument --instance on the command line.
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.
OPTIONAL FLAGS
At most one of these can be specified:
--condition=[KEY=VALUE,...]
A condition to include in the binding. When the condition is
explicitly specified as None (--condition=None), a binding without a
condition is added. When the condition is specified and is not None,
--role cannot be a basic role. Basic roles are roles/editor,
roles/owner, and roles/viewer. For more on conditions, refer to the
conditions overview guide:
https://cloud.google.com/iam/docs/conditions-overview
When using the --condition flag, include the following key-value
pairs:
expression
(Required) Condition expression that evaluates to True or False.
This uses a subset of Common Expression Language syntax.
If the condition expression includes a comma, use a different
delimiter to separate the key-value pairs. Specify the delimiter
before listing the key-value pairs. For example, to specify a
colon (:) as the delimiter, do the following:
--condition=^:^title=TITLE:expression=EXPRESSION. For more
information, see
https://cloud.google.com/sdk/gcloud/reference/topic/escaping.
title
(Required) A short string describing the purpose of the
expression.
description
(Optional) Additional description for the expression.
--condition-from-file=CONDITION_FROM_FILE
Path to a local JSON or YAML file that defines the condition. To see
available fields, see the help for --condition.
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 bigtableadmin/v2 API. The full documentation for this
API can be found at: https://cloud.google.com/bigtable/
NOTES
This command is currently in beta and might change without notice. These
variants are also available:
$ gcloud bigtable tables add-iam-policy-binding
$ gcloud alpha bigtable tables add-iam-policy-binding

145
gcloud/beta/bigtable/tables/create Normal file
View file

@ -0,0 +1,145 @@
NAME
gcloud beta bigtable tables create - create a new Cloud Bigtable table
SYNOPSIS
gcloud beta bigtable tables create (TABLE : --instance=INSTANCE)
--column-families=[COLUMN_FAMILIES,...]
[--change-stream-retention-period=CHANGE_STREAM_RETENTION_PERIOD]
[--deletion-protection] [--enable-automated-backup]
[--splits=[SPLITS,...]] [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(BETA) Create a new Cloud Bigtable table.
EXAMPLES
To create a table my-table in instance my-instance with a column family
my-family, run:
$ gcloud beta bigtable tables create my-table \
--instance=my-instance --column-families="my-family"
To create a table that has a column family named my-instance, a garbage
collection policy that lets data expire after 864,000 seconds, and initial
table splits on row keys car and key, run:
$ gcloud beta bigtable tables create my-table \
--instance=my-instance \
--column-families="my-family:maxage=864000s" --splits=car,key
To create a table my-table in instance my-instance that lets data in column
family my-family1 expire after 10 days and keeps a maximum of 5 cells per
column in column family my-family-2 if the data is less than 5 days old,
run:
$ gcloud beta bigtable tables create my-table \
--instance=my-instance \
--column-families="my-family-1:maxage=10d,my-family-2:maxversion\
s=5||maxage=5d"
To create a table my-table that has one column family my-family that lets
data expire after 10 days, and to enable a change stream for the table to
be kept for 7 days, run:
$ gcloud beta bigtable tables create my-table \
--instance=my-instance \
--column-families="my-family:maxage=10d" \
--change-stream-retention-period=7d
To create a deletion-protected table my-table in instance my-instance with
a column family my-family, run:
$ gcloud beta bigtable tables create my-table \
--instance=my-instance --column-families="my-family" \
--deletion-protection
To create a table my-table without deletion protection in instance
my-instance with a column family my-family, run:
$ gcloud beta bigtable tables create my-table \
--instance=my-instance --column-families="my-family" \
--no-deletion-protection
To create a table my-table with automated backup policy
(retention_period=72h, frequency=24h) enabled in instance my-instance with
a column family my-family, run:
$ gcloud beta bigtable tables create my-table \
--instance=my-instance --column-families="my-family" \
--enable-automated-backup
POSITIONAL ARGUMENTS
Table resource - Cloud Bigtable table 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 table 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.
TABLE
ID of the table or fully qualified identifier for the table.
To set the table attribute:
▸ provide the argument table on the command line.
This positional argument must be specified if any of the other
arguments in this group are specified.
--instance=INSTANCE
Name of the Cloud Bigtable instance.
To set the instance attribute:
▸ provide the argument table on the command line with a fully
specified name;
▸ provide the argument --instance on the command line.
REQUIRED FLAGS
--column-families=[COLUMN_FAMILIES,...]
A double-quote (") wrapped list of family name and corresponding
garbage collection rules concatenated by :, where the rules are
optional. For example: \
"family_1,family_2:maxage=5d&&maxversions=2,family_3:maxage=10d||maxversions=5"
OPTIONAL FLAGS
--change-stream-retention-period=CHANGE_STREAM_RETENTION_PERIOD
The length of time to retain change stream data for the table, in the
range of [1 day, 7 days]. Acceptable units are days (d), hours (h),
minutes (m), and seconds (s). Passing in a value for this option
enables a change stream for the table. Examples: 5d or 48h.
--deletion-protection
Once specified, the table is deletion protected.
--enable-automated-backup
Once set, enables the default automated backup policy
(retention_period=72h, frequency=24h) for the table.
--splits=[SPLITS,...]
Row keys where the table should initially be split. For example:
car,key
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 bigtableadmin/v2 API. The full documentation for this
API can be found at: https://cloud.google.com/bigtable/
NOTES
This command is currently in beta and might change without notice. These
variants are also available:
$ gcloud bigtable tables create
$ gcloud alpha bigtable tables create

66
gcloud/beta/bigtable/tables/delete Normal file
View file

@ -0,0 +1,66 @@
NAME
gcloud beta bigtable tables delete - delete a Cloud Bigtable table
SYNOPSIS
gcloud beta bigtable tables delete (TABLE : --instance=INSTANCE)
[GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(BETA) Delete a Cloud Bigtable table.
EXAMPLES
To delete the table my-table in instance my-instance, run:
$ gcloud beta bigtable tables delete my-table --instance=my-instance
POSITIONAL ARGUMENTS
Table resource - Cloud Bigtable table 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 table 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.
TABLE
ID of the table or fully qualified identifier for the table.
To set the table attribute:
▸ provide the argument table on the command line.
This positional argument must be specified if any of the other
arguments in this group are specified.
--instance=INSTANCE
Name of the Cloud Bigtable instance.
To set the instance attribute:
▸ provide the argument table on the command line with a fully
specified name;
▸ provide the argument --instance on the command line.
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 bigtableadmin/v2 API. The full documentation for this
API can be found at: https://cloud.google.com/bigtable/
NOTES
This command is currently in beta and might change without notice. These
variants are also available:
$ gcloud bigtable tables delete
$ gcloud alpha bigtable tables delete

87
gcloud/beta/bigtable/tables/describe Normal file
View file

@ -0,0 +1,87 @@
NAME
gcloud beta bigtable tables describe - retrieve information about a table
SYNOPSIS
gcloud beta bigtable tables describe (TABLE : --instance=INSTANCE)
[--view=VIEW; default="schema"] [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(BETA) Retrieve information about a table.
EXAMPLES
To describe a table, run:
$ gcloud beta bigtable tables describe TABLE_NAME \
--instance=INSTANCE_NAME
POSITIONAL ARGUMENTS
Table resource - Cloud Bigtable table to describe. 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 table 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.
TABLE
ID of the table or fully qualified identifier for the table.
To set the table attribute:
▸ provide the argument table on the command line.
This positional argument must be specified if any of the other
arguments in this group are specified.
--instance=INSTANCE
Name of the Cloud Bigtable instance.
To set the instance attribute:
▸ provide the argument table on the command line with a fully
specified name;
▸ provide the argument --instance on the command line.
FLAGS
--view=VIEW; default="schema"
The view to be applied to the returned table's fields. VIEW must be one
of:
encryption
Only populates name and fields related to the table's encryption
status.
full
Populates all fields.
name
Only populates name.
replication
Only populates name and fields related to the table's replication.
schema
Only populates name and fields related to the table's schema.
stats
Only populates name and fields related to the table's statistics
(e.g. TableStats and ColumnFamilyStats).
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 bigtableadmin/v2 API. The full documentation for this
API can be found at: https://cloud.google.com/bigtable/
NOTES
This command is currently in beta and might change without notice. These
variants are also available:
$ gcloud bigtable tables describe
$ gcloud alpha bigtable tables describe

99
gcloud/beta/bigtable/tables/get-iam-policy Normal file
View file

@ -0,0 +1,99 @@
NAME
gcloud beta bigtable tables get-iam-policy - get an IAM policy on a Cloud
Bigtable table
SYNOPSIS
gcloud beta bigtable tables get-iam-policy (TABLE : --instance=INSTANCE)
[--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE]
[--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(BETA) Get an IAM policy on a Cloud Bigtable table.
EXAMPLES
To get the IAM policy on the table 'my-table' in instance 'my-instance',
run:
$ gcloud beta bigtable tables get-iam-policy my-table \
--instance='my-instance'
See https://cloud.google.com/iam/docs/managing-policies for more
information.
POSITIONAL ARGUMENTS
Table resource - Cloud Bigtable table to get the IAM policy for. 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 table 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.
TABLE
ID of the table or fully qualified identifier for the table.
To set the table attribute:
▸ provide the argument table on the command line.
This positional argument must be specified if any of the other
arguments in this group are specified.
--instance=INSTANCE
Name of the Cloud Bigtable instance.
To set the instance attribute:
▸ provide the argument table on the command line with a fully
specified name;
▸ provide the argument --instance on the command line.
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 bigtableadmin/v2 API. The full documentation for this
API can be found at: https://cloud.google.com/bigtable/
NOTES
This command is currently in beta and might change without notice. These
variants are also available:
$ gcloud bigtable tables get-iam-policy
$ gcloud alpha bigtable tables get-iam-policy

58
gcloud/beta/bigtable/tables/help Normal file
View file

@ -0,0 +1,58 @@
NAME
gcloud beta bigtable tables - query Cloud Bigtable tables
SYNOPSIS
gcloud beta bigtable tables COMMAND [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(BETA) Query Cloud Bigtable tables.
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
(BETA) Add an IAM policy binding to a Cloud Bigtable table.
create
(BETA) Create a new Cloud Bigtable table.
delete
(BETA) Delete a Cloud Bigtable table.
describe
(BETA) Retrieve information about a table.
get-iam-policy
(BETA) Get an IAM policy on a Cloud Bigtable table.
list
(BETA) List existing Bigtable instance tables.
remove-iam-policy-binding
(BETA) Remove an IAM policy binding from a Cloud Bigtable table.
restore
(BETA) Restore a Cloud Bigtable backup to a new table.
set-iam-policy
(BETA) Set an IAM policy on a Cloud Bigtable table.
undelete
(BETA) Undelete a previously deleted Cloud Bigtable table.
update
(BETA) Update an existing Cloud Bigtable table.
NOTES
This command is currently in beta and might change without notice. These
variants are also available:
$ gcloud bigtable tables
$ gcloud alpha bigtable tables

68
gcloud/beta/bigtable/tables/list Normal file
View file

@ -0,0 +1,68 @@
NAME
gcloud beta bigtable tables list - list existing Bigtable instance tables
SYNOPSIS
gcloud beta bigtable tables list --instances=[INSTANCE,...]
[--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE]
[--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...]
EXAMPLES
To list all tables in an instance, run:
$ gcloud beta bigtable tables list --instances=INSTANCE_NAME
To list all tables in several instances, run: $ gcloud beta bigtable tables list \
--instances=INSTANCE_NAME1,INSTANCE_NAME2
REQUIRED FLAGS
--instances=[INSTANCE,...]
ID of the instances.
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.
NOTES
This command is currently in beta and might change without notice. These
variants are also available:
$ gcloud bigtable tables list
$ gcloud alpha bigtable tables list

151
gcloud/beta/bigtable/tables/remove-iam-policy-binding Normal file
View file

@ -0,0 +1,151 @@
NAME
gcloud beta bigtable tables remove-iam-policy-binding - remove an IAM
policy binding from a Cloud Bigtable table
SYNOPSIS
gcloud beta bigtable tables remove-iam-policy-binding
(TABLE : --instance=INSTANCE) --member=PRINCIPAL --role=ROLE
[--all | --condition=[KEY=VALUE,...]
| --condition-from-file=CONDITION_FROM_FILE] [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(BETA) Remove an IAM policy binding from a Cloud Bigtable table. One
binding consists of a member, a role, and an optional condition.
EXAMPLES
To remove an IAM policy binding for the role of 'roles/editor' for the user
'test-user@gmail.com' with table 'my-table' in instance 'my-instance', run:
$ gcloud beta bigtable tables remove-iam-policy-binding my-table \
--instance='my-instance' --member='user:test-user@gmail.com' \
--role='roles/editor'
To remove an IAM policy binding which expires at the end of the year 2019
for the role of 'roles/bigtable.admin' and the user 'test-user@gmail.com'
with table 'my-table' in instance 'my-instance', run:
$ gcloud beta bigtable tables remove-iam-policy-binding my-table \
--instance='my-instance' --member='user:test-user@gmail.com' \
--role='roles/bigtable.admin' \
--condition='expression=request.time <
timestamp("2020-01-01T00:00:00Z"),title=expires_end_of_2019,descrip\
tion=Expires at midnight on 2019-12-31'
See https://cloud.google.com/iam/docs/managing-policies for details of
policy role and member types.
POSITIONAL ARGUMENTS
Table resource - Cloud Bigtable table to remove the 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 table 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.
TABLE
ID of the table or fully qualified identifier for the table.
To set the table attribute:
▸ provide the argument table on the command line.
This positional argument must be specified if any of the other
arguments in this group are specified.
--instance=INSTANCE
Name of the Cloud Bigtable instance.
To set the instance attribute:
▸ provide the argument table on the command line with a fully
specified name;
▸ provide the argument --instance on the command line.
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.
OPTIONAL FLAGS
At most one of these can be specified:
--all
Remove all bindings with this role and principal, irrespective of any
conditions.
--condition=[KEY=VALUE,...]
The condition of the binding that you want to remove. When the
condition is explicitly specified as None (--condition=None), a
binding without a condition is removed. Otherwise, only a binding
with a condition that exactly matches the specified condition
(including the optional description) is removed. For more on
conditions, refer to the conditions overview guide:
https://cloud.google.com/iam/docs/conditions-overview
When using the --condition flag, include the following key-value
pairs:
expression
(Required) Condition expression that evaluates to True or False.
This uses a subset of Common Expression Language syntax.
If the condition expression includes a comma, use a different
delimiter to separate the key-value pairs. Specify the delimiter
before listing the key-value pairs. For example, to specify a
colon (:) as the delimiter, do the following:
--condition=^:^title=TITLE:expression=EXPRESSION. For more
information, see
https://cloud.google.com/sdk/gcloud/reference/topic/escaping.
title
(Required) A short string describing the purpose of the
expression.
description
(Optional) Additional description for the expression.
--condition-from-file=CONDITION_FROM_FILE
Path to a local JSON or YAML file that defines the condition. To see
available fields, see the help for --condition.
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 bigtableadmin/v2 API. The full documentation for this
API can be found at: https://cloud.google.com/bigtable/
NOTES
This command is currently in beta and might change without notice. These
variants are also available:
$ gcloud bigtable tables remove-iam-policy-binding
$ gcloud alpha bigtable tables remove-iam-policy-binding

123
gcloud/beta/bigtable/tables/restore Normal file
View file

@ -0,0 +1,123 @@
NAME
gcloud beta bigtable tables restore - restore a Cloud Bigtable backup to a
new table
SYNOPSIS
gcloud beta bigtable tables restore
(--destination=DESTINATION
: --destination-instance=DESTINATION_INSTANCE)
(--source=SOURCE
: --source-cluster=SOURCE_CLUSTER --source-instance=SOURCE_INSTANCE)
[--async] [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(BETA) This command restores a Cloud Bigtable backup to a new table.
EXAMPLES
To restore table 'table2' from backup 'backup1', run:
$ gcloud beta bigtable tables restore --source-instance=instance1 \
--source-cluster=cluster1 --source=backup1 \
--destination-instance=instance1 --destination=table2
To restore table 'table2' from backup 'backup1' in a different project,
run:
$ gcloud beta bigtable tables restore \
--source=projects/project1/instances/instance1/clusters/\
cluster1/backups/backup1 \
--destination=projects/project2/instances/instance2/tables/\
table2
REQUIRED FLAGS
Table resource - The destination to restore 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 --destination 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.
--destination=DESTINATION
ID of the table or fully qualified identifier for the table.
To set the destination attribute:
▸ provide the argument --destination on the command line.
This flag argument must be specified if any of the other arguments in
this group are specified.
--destination-instance=DESTINATION_INSTANCE
Name of the Cloud Bigtable instance.
To set the instance attribute:
▸ provide the argument --destination on the command line with a
fully specified name;
▸ provide the argument --destination-instance on the command line;
▸ provide the argument --source-instance on the command line.
Backup resource - The source to restore 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 --source 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.
--source=SOURCE
ID of the backup or fully qualified identifier for the backup.
To set the source attribute:
▸ provide the argument --source on the command line.
This flag argument must be specified if any of the other arguments in
this group are specified.
--source-cluster=SOURCE_CLUSTER
Name of the Cloud Bigtable cluster.
To set the cluster attribute:
▸ provide the argument --source on the command line with a fully
specified name;
▸ provide the argument --source-cluster on the command line.
--source-instance=SOURCE_INSTANCE
Name of the Cloud Bigtable instance.
To set the instance attribute:
▸ provide the argument --source on the command line with a fully
specified name;
▸ provide the argument --source-instance on the command line;
▸ provide the argument --destination-instance on the command line.
OPTIONAL FLAGS
--async
Return immediately, without waiting for the operation in progress to
complete.
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 beta and might change without notice. These
variants are also available:
$ gcloud bigtable tables restore
$ gcloud alpha bigtable tables restore

79
gcloud/beta/bigtable/tables/set-iam-policy Normal file
View file

@ -0,0 +1,79 @@
NAME
gcloud beta bigtable tables set-iam-policy - set an IAM policy on a Cloud
Bigtable table
SYNOPSIS
gcloud beta bigtable tables set-iam-policy (TABLE : --instance=INSTANCE)
POLICY_FILE [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(BETA) Set an IAM policy on a Cloud Bigtable table.
EXAMPLES
To set the IAM policy from file 'my-policy' on the table 'my-table' in
instance 'my-instance', run:
$ gcloud beta bigtable tables set-iam-policy my-table \
--instance='my-instance' my-policy
See https://cloud.google.com/iam/docs/managing-policies for more
information.
POSITIONAL ARGUMENTS
Table resource - Cloud Bigtable table to set the IAM policy on. 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 table 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.
TABLE
ID of the table or fully qualified identifier for the table.
To set the table attribute:
▸ provide the argument table on the command line.
This positional argument must be specified if any of the other
arguments in this group are specified.
--instance=INSTANCE
Name of the Cloud Bigtable instance.
To set the instance attribute:
▸ provide the argument table on the command line with a fully
specified name;
▸ provide the argument --instance on the command line.
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.
API REFERENCE
This command uses the bigtableadmin/v2 API. The full documentation for this
API can be found at: https://cloud.google.com/bigtable/
NOTES
This command is currently in beta and might change without notice. These
variants are also available:
$ gcloud bigtable tables set-iam-policy
$ gcloud alpha bigtable tables set-iam-policy

73
gcloud/beta/bigtable/tables/undelete Normal file
View file

@ -0,0 +1,73 @@
NAME
gcloud beta bigtable tables undelete - undelete a previously deleted Cloud
Bigtable table
SYNOPSIS
gcloud beta bigtable tables undelete (TABLE : --instance=INSTANCE)
[--async] [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(BETA) Undelete a previously deleted Cloud Bigtable table.
EXAMPLES
To undelete the table my-table in instance my-instance, run:
$ gcloud beta bigtable tables undelete my-table \
--instance=my-instance
POSITIONAL ARGUMENTS
Table resource - Cloud Bigtable table to undelete. 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 table 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.
TABLE
ID of the table or fully qualified identifier for the table.
To set the table attribute:
▸ provide the argument table on the command line.
This positional argument must be specified if any of the other
arguments in this group are specified.
--instance=INSTANCE
Name of the Cloud Bigtable instance.
To set the instance attribute:
▸ provide the argument table on the command line with a fully
specified name;
▸ provide the argument --instance on the command line.
FLAGS
--async
Return immediately, without waiting for the operation in progress to
complete.
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 bigtableadmin/v2 API. The full documentation for this
API can be found at: https://cloud.google.com/bigtable/
NOTES
This command is currently in beta and might change without notice. These
variants are also available:
$ gcloud bigtable tables undelete
$ gcloud alpha bigtable tables undelete

126
gcloud/beta/bigtable/tables/update Normal file
View file

@ -0,0 +1,126 @@
NAME
gcloud beta bigtable tables update - update an existing Cloud Bigtable
table
SYNOPSIS
gcloud beta bigtable tables update (TABLE : --instance=INSTANCE) [--async]
[--deletion-protection] [--disable-automated-backup]
[--enable-automated-backup]
[--change-stream-retention-period=CHANGE_STREAM_RETENTION_PERIOD
| --clear-change-stream-retention-period] [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(BETA) Update an existing new Cloud Bigtable table with the specified
configuration.
EXAMPLES
To enable deletion protection, run:
$ gcloud beta bigtable tables update my-table \
--instance=my-instance --deletion-protection
To disable deletion protection, run:
$ gcloud beta bigtable tables update my-table \
--instance=my-instance --no-deletion-protection
To enable a change stream with a retention period of 1 day, or to update
your table's change stream retention period to 1 day, run:
$ gcloud beta bigtable tables update my-table \
--instance=my-instance --change-stream-retention-period=1d
To disable a change stream, run:
$ gcloud beta bigtable tables update my-table \
--instance=my-instance --clear-change-stream-retention-period
To enable default automated backup policy (retention_period=72h,
frequency=24h), run:
$ gcloud beta bigtable tables update my-table \
--instance=my-instance --enable-automated-backup
To disable automated backup: run:
$ gcloud beta bigtable tables update my-table \
--instance=my-instance --disable-automated-backup
POSITIONAL ARGUMENTS
Table resource - Cloud Bigtable table 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 table 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.
TABLE
ID of the table or fully qualified identifier for the table.
To set the table attribute:
▸ provide the argument table on the command line.
This positional argument must be specified if any of the other
arguments in this group are specified.
--instance=INSTANCE
Name of the Cloud Bigtable instance.
To set the instance attribute:
▸ provide the argument table on the command line with a fully
specified name;
▸ provide the argument --instance on the command line.
FLAGS
--async
Return immediately, without waiting for the operation in progress to
complete.
--deletion-protection
Once specified, the table is deletion protected.
--disable-automated-backup
Once set, disables automated backup policy for the table.
--enable-automated-backup
Once set, enables the default automated backup policy
(retention_period=72h, frequency=24h) for the table.
At most one of these can be specified:
--change-stream-retention-period=CHANGE_STREAM_RETENTION_PERIOD
The length of time to retain change stream data for the table, in the
range of [1 day, 7 days]. Acceptable units are days (d), hours (h),
minutes (m), and seconds (s). If not already specified, enables a
change stream for the table. Examples: 5d or 48h.
--clear-change-stream-retention-period
This disables the change stream and eventually removes the change
stream data.
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 bigtableadmin/v2 API. The full documentation for this
API can be found at: https://cloud.google.com/bigtable/
NOTES
This command is currently in beta and might change without notice. These
variants are also available:
$ gcloud bigtable tables update
$ gcloud alpha bigtable tables update

74
gcloud/beta/composer/environments/update
View file

@ -11,6 +11,9 @@ SYNOPSIS
| --environment-size=ENVIRONMENT_SIZE | --node-count=NODE_COUNT
| --web-server-machine-type=WEB_SERVER_MACHINE_TYPE
| --airflow-version=AIRFLOW_VERSION | --image-version=IMAGE_VERSION
| --maintenance-window-end=MAINTENANCE_WINDOW_END
--maintenance-window-recurrence=MAINTENANCE_WINDOW_RECURRENCE
--maintenance-window-start=MAINTENANCE_WINDOW_START
| --disable-cloud-data-lineage-integration
| --enable-cloud-data-lineage-integration
| --disable-master-authorized-networks
@ -21,9 +24,6 @@ SYNOPSIS
--snapshot-creation-schedule=SNAPSHOT_CREATION_SCHEDULE
--snapshot-location=SNAPSHOT_LOCATION
--snapshot-schedule-timezone=SNAPSHOT_SCHEDULE_TIMEZONE
| --maintenance-window-end=MAINTENANCE_WINDOW_END
--maintenance-window-recurrence=MAINTENANCE_WINDOW_RECURRENCE
--maintenance-window-start=MAINTENANCE_WINDOW_START
| --max-workers=MAX_WORKERS --min-workers=MIN_WORKERS
--scheduler-count=SCHEDULER_COUNT --scheduler-cpu=SCHEDULER_CPU
--scheduler-memory=SCHEDULER_MEMORY
@ -164,6 +164,43 @@ REQUIRED FLAGS
Composer version. The resolved versions are stored in the upgraded
environment.
Group of arguments for setting the maintenance window value during
update.
At most one of these can be specified:
Group of arguments for setting the maintenance window value.
--maintenance-window-end=MAINTENANCE_WINDOW_END
End time of the mantenance window in the form of the full date.
Only the time of the day is used as a reference for an ending
time of the window with a provided recurrence. Specified date
must take place after the one specified as a start date, the
difference between will be used as a length of a single
maintenance window. See $ gcloud topic datetimes for information
on time formats.
This flag argument must be specified if any of the other
arguments in this group are specified.
--maintenance-window-recurrence=MAINTENANCE_WINDOW_RECURRENCE
An RFC 5545 RRULE, specifying how the maintenance window will
recur. The minimum requirement for the length of the maintenance
window is 12 hours a week. Only FREQ=DAILY and FREQ=WEEKLY rules
are supported.
This flag argument must be specified if any of the other
arguments in this group are specified.
--maintenance-window-start=MAINTENANCE_WINDOW_START
Start time of the mantenance window in the form of the full date.
Only the time of the day is used as a reference for a starting
time of the window with a provided recurrence. See $ gcloud topic
datetimes for information on time formats.
This flag argument must be specified if any of the other
arguments in this group are specified.
Group of arguments for setting Cloud Data Lineage integration
configuration in Composer 2.
@ -239,37 +276,6 @@ REQUIRED FLAGS
This flag argument must be specified if any of the other
arguments in this group are specified.
Group of arguments for setting the maintenance window value.
--maintenance-window-end=MAINTENANCE_WINDOW_END
End time of the mantenance window in the form of the full date.
Only the time of the day is used as a reference for an ending time
of the window with a provided recurrence. Specified date must take
place after the one specified as a start date, the difference
between will be used as a length of a single maintenance window.
See $ gcloud topic datetimes for information on time formats.
This flag argument must be specified if any of the other arguments
in this group are specified.
--maintenance-window-recurrence=MAINTENANCE_WINDOW_RECURRENCE
An RFC 5545 RRULE, specifying how the maintenance window will
recur. The minimum requirement for the length of the maintenance
window is 12 hours a week. Only FREQ=DAILY and FREQ=WEEKLY rules
are supported.
This flag argument must be specified if any of the other arguments
in this group are specified.
--maintenance-window-start=MAINTENANCE_WINDOW_START
Start time of the mantenance window in the form of the full date.
Only the time of the day is used as a reference for a starting time
of the window with a provided recurrence. See $ gcloud topic
datetimes for information on time formats.
This flag argument must be specified if any of the other arguments
in this group are specified.
Group of arguments for setting workloads configuration in Composer 2.X
or greater (--scheduler-count flag is available for Composer 1.X as
well).

5
gcloud/beta/compute/commitments/create
View file

@ -103,8 +103,9 @@ OPTIONAL FLAGS
accelerator-optimized-a3, compute-optimized, compute-optimized-c2d,
compute-optimized-c3, compute-optimized-c3d, compute-optimized-h3,
general-purpose, general-purpose-e2, general-purpose-n2,
general-purpose-n2d, general-purpose-t2d, graphics-optimized,
memory-optimized, memory-optimized-m3, storage-optimized-z3.
general-purpose-n2d, general-purpose-n4, general-purpose-t2d,
graphics-optimized, memory-optimized, memory-optimized-m3,
storage-optimized-z3.
Manage the reservations to be created with the commitment.

13
gcloud/beta/compute/public-advertised-prefixes/create
View file

@ -5,7 +5,8 @@ NAME
SYNOPSIS
gcloud beta compute public-advertised-prefixes create NAME
--dns-verification-ip=DNS_VERIFICATION_IP --range=RANGE
[--description=DESCRIPTION] [GCLOUD_WIDE_FLAG ...]
[--description=DESCRIPTION] [--pdp-scope=PDP_SCOPE]
[GCLOUD_WIDE_FLAG ...]
EXAMPLES
To create a public advertised prefix:
@ -14,6 +15,12 @@ EXAMPLES
my-public-advertised-prefix --range=120.120.10.0/24 \
--dns-verification-ip=120.120.10.15
To create a v2 public advertised prefix:
$ gcloud beta compute public-advertised-prefixes create \
my-v2-public-advertised-prefix --range=120.120.10.0/24 \
--dns-verification-ip=120.120.10.15 --pdp-scope=REGIONAL
POSITIONAL ARGUMENTS
NAME
Name of the public advertised prefix to operate on.
@ -30,6 +37,10 @@ OPTIONAL FLAGS
--description=DESCRIPTION
Description of this public advertised prefix.
--pdp-scope=PDP_SCOPE
Specifies how child public delegated prefix will be scoped. PDP_SCOPE
must be one of: GLOBAL, REGIONAL.
GCLOUD WIDE FLAGS
These flags are available to all commands: --access-token-file, --account,
--billing-project, --configuration, --flags-file, --flatten, --format,

27
gcloud/beta/compute/public-advertised-prefixes/update
View file

@ -3,7 +3,8 @@ NAME
Engine public advertised prefix
SYNOPSIS
gcloud beta compute public-advertised-prefixes update NAME --status=STATUS
gcloud beta compute public-advertised-prefixes update NAME
(--announce-prefix | --status=STATUS | --withdraw-prefix)
[GCLOUD_WIDE_FLAG ...]
EXAMPLES
@ -12,14 +13,32 @@ EXAMPLES
$ gcloud beta compute public-advertised-prefixes update my-pap \
--status=ptr-configured
To announce a public advertised prefix:
$ gcloud beta compute public-advertised-prefixes update my-pap \
--announce-prefix
To withdraw a public advertised prefix:
$ gcloud beta compute public-advertised-prefixes update my-pap \
--withdraw-prefix
POSITIONAL ARGUMENTS
NAME
Name of the public advertised prefix to operate on.
REQUIRED FLAGS
--status=STATUS
The status of public advertised prefix. STATUS must be (only one value
is supported): ptr-configured.
Exactly one of these must be specified:
--announce-prefix
Specify if the prefix will be announced. Default is false.
--status=STATUS
The status of public advertised prefix. STATUS must be (only one
value is supported): ptr-configured.
--withdraw-prefix
Specify if the prefix will be withdrawn. Default is false.
GCLOUD WIDE FLAGS
These flags are available to all commands: --access-token-file, --account,

3
gcloud/beta/compute/public-delegated-prefixes/help
View file

@ -35,6 +35,9 @@ COMMANDS
list
(BETA) List Google Compute Engine public delegated prefixes.
update
(BETA) Updates a Compute Engine public delegated prefix.
NOTES
This command is currently in beta and might change without notice. These
variants are also available:

54
gcloud/beta/compute/public-delegated-prefixes/update Normal file
View file

@ -0,0 +1,54 @@
NAME
gcloud beta compute public-delegated-prefixes update - updates a Compute
Engine public delegated prefix
SYNOPSIS
gcloud beta compute public-delegated-prefixes update NAME
(--announce-prefix | --withdraw-prefix) [--region=REGION]
[GCLOUD_WIDE_FLAG ...]
EXAMPLES
To announce a regional v2 public delegated prefix:
$ gcloud beta compute public-delegated-prefixes update my-pdp \
--announce-prefix --region=us-central1
To withdraw a regional v2 public delegated prefix:
$ gcloud beta compute public-delegated-prefixes update my-pdp \
--withdraw-prefix --region=us-central1
POSITIONAL ARGUMENTS
NAME
Name of the public delegated prefix to operate on.
REQUIRED FLAGS
Exactly one of these must be specified:
--announce-prefix
Specify if the prefix will be announced. Default is false.
--withdraw-prefix
Specify if the prefix will be withdrawn. Default is false.
OPTIONAL FLAGS
--region=REGION
Region of the public delegated prefix to operate on. Overrides the
default compute/region property value for this command invocation.
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 beta and might change without notice. These
variants are also available:
$ gcloud compute public-delegated-prefixes update
$ gcloud alpha compute public-delegated-prefixes update

5
gcloud/beta/container/binauthz/attestors/create
View file

@ -7,12 +7,15 @@ SYNOPSIS
: --attestation-authority-note-project=ATTESTATION_AUTHORITY_NOTE_PROJECT)
[--description=DESCRIPTION] [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(BETA) Create an Attestor.
EXAMPLES
To create an Attestor with an existing Note projects/my_proj/notes/my_note:
$ gcloud beta container binauthz attestors create my_new_attestor \
--attestation-authority-note=my_note \
--attestation-authority-note-project=my_proj \
--attestation-authority-note-project=my_proj
POSITIONAL ARGUMENTS
Attestor resource - The attestor to be created. This represents a Cloud

13
gcloud/beta/container/clusters/update
View file

@ -20,10 +20,11 @@ SYNOPSIS
| --enable-l4-ilb-subsetting | --enable-legacy-authorization
| --enable-logging-monitoring-system-only
| --enable-master-authorized-networks | --enable-master-global-access
| --enable-network-policy | --enable-pod-security-policy
| --enable-private-endpoint | --enable-secret-manager
| --enable-service-externalips | --enable-shielded-nodes
| --enable-stackdriver-kubernetes | --enable-vertical-pod-autoscaling
| --enable-multi-networking | --enable-network-policy
| --enable-pod-security-policy | --enable-private-endpoint
| --enable-secret-manager | --enable-service-externalips
| --enable-shielded-nodes | --enable-stackdriver-kubernetes
| --enable-vertical-pod-autoscaling
| --fleet-project=PROJECT_ID_OR_NUMBER | --gateway-api=GATEWAY_API
| --generate-password | --identity-provider=IDENTITY_PROVIDER
| --in-transit-encryption=IN_TRANSIT_ENCRYPTION
@ -358,6 +359,10 @@ REQUIRED FLAGS
endpoint from any Google Cloud region or on-premises environment
regardless of the private cluster's region.
--enable-multi-networking
Enables multi-networking on the cluster. Multi-networking is disabled
by default.
--enable-network-policy
Enable network policy enforcement for this cluster. If you are
enabling network policy on an existing cluster the network policy

31
gcloud/beta/dataflow/jobs/update-options
View file

@ -5,7 +5,9 @@ NAME
SYNOPSIS
gcloud beta dataflow jobs update-options JOB_ID
[--max-num-workers=MAX_NUM_WORKERS] [--min-num-workers=MIN_NUM_WORKERS]
[--region=REGION_ID] [GCLOUD_WIDE_FLAG ...]
[--region=REGION_ID] [--unset-worker-utilization-hint]
[--worker-utilization-hint=WORKER_UTILIZATION_HINT]
[GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(BETA) This command can modify properties of running Dataflow jobs.
@ -13,8 +15,10 @@ DESCRIPTION
supported.
Adjust the autoscaling settings for Streaming Engine Dataflow jobs by
providing at-least one of --min-num-workers or --max-num-workers (or both).
Allow a few minutes for the changes to take effect.
providing at-least one of --min-num-workers or --max-num-workers or
--worker-utilization-hint (or all 3), or --unset-worker-utilization-hint
(which cannot be run at the same time as --worker-utilization-hint but
works with the others). Allow a few minutes for the changes to take effect.
Note that autoscaling settings can only be modified on-the-fly for
Streaming Engine jobs. Attempts to modify batch job or Streaming Appliance
@ -34,6 +38,18 @@ EXAMPLES
$ gcloud beta dataflow jobs update-options --max-num-workers=20
Adjust the hint of target worker utilization to 70% for horizontal
autoscaling:
$ gcloud beta dataflow jobs update-options \
--worker-utilization-hint=0.7
"Unset" worker utilization hint so that horizontal scaling will rely on its
default CPU utilization target:
$ gcloud beta dataflow jobs update-options \
--unset-worker-utilization-hint
POSITIONAL ARGUMENTS
JOB_ID
Job ID to operate on.
@ -50,6 +66,15 @@ FLAGS
--region=REGION_ID
Region ID of the job's regional endpoint. Defaults to 'us-central1'.
--unset-worker-utilization-hint
Unset --worker-utilization-hint. This causes the job autoscaling to
fall back to internal tunings if they exist, or otherwise use the
default hint value.
--worker-utilization-hint=WORKER_UTILIZATION_HINT
Target CPU utilization for autoscaling, ranging from 0.1 to 0.9. Only
supported for streaming-engine jobs with autoscaling enabled.
GCLOUD WIDE FLAGS
These flags are available to all commands: --access-token-file, --account,
--billing-project, --configuration, --flags-file, --flatten, --format,

22
gcloud/beta/filestore/instances/create
View file

@ -114,7 +114,9 @@ REQUIRED FLAGS
▫ 1TB-9.75TB in 256GB increments or its multiples.
▫ 10TB-100TB in 2.5TB increments or its multiples.
▸ ENTERPRISE: 1TB-10TB in 256GB increments or its multiples.
▸ REGIONAL: 1TB-9.75TB in 256GB increments or its multiples.
▸ REGIONAL: 1TB-100TB:
▫ 1TB-9.75TB in 256GB increments or its multiples.
▫ 10TB-100TB in 2.5TB increments or its multiples.
name
The desired logical name of the volume.
@ -164,15 +166,15 @@ REQUIRED FLAGS
A list of security flavors that are allowed to be used during mount
command in NFSv4.1 filestore instances. The security flavors
supported are:
◆ SECURITY_FLAVOR_UNSPECIFIED: SecurityFlavor not set. Defaults to
AUTH_SYS.
◆ AUTH_SYS: The user's UNIX user-id and group-ids are passed in the
clear.
◆ KRB5: The end-user authentication is done using Kerberos V5.
◆ KRB5I: KRB5 plus integrity protection (data packets are tamper
proof).
◆ KRB5P: KRB5I plus privacy protection (data packets are tamper
proof and encrypted).
▫ SECURITY_FLAVOR_UNSPECIFIED: SecurityFlavor not set. Defaults
to AUTH_SYS.
▫ AUTH_SYS: The user's UNIX user-id and group-ids are passed in
the clear.
▫ KRB5: The end-user authentication is done using Kerberos V5.
▫ KRB5I: KRB5 plus integrity protection (data packets are
tamper proof).
▫ KRB5P: KRB5I plus privacy protection (data packets are tamper
proof and encrypted).
source-backup
The name of the backup to restore from.

26
gcloud/beta/filestore/instances/update
View file

@ -171,7 +171,9 @@ FLAGS
▫ 1TB-9.75TB in 256GB increments or its multiples.
▫ 10TB-100TB in 2.5TB increments or its multiples.
▸ ENTERPRISE: 1TB-10TB in 256GB increments or its multiples.
▸ REGIONAL: 1TB-9.75TB in 256GB increments or its multiples.
▸ REGIONAL: 1TB-100TB:
▫ 1TB-9.75TB in 256GB increments or its multiples.
▫ 10TB-100TB in 2.5TB increments or its multiples.
name
The desired logical name of the volume.
@ -221,18 +223,18 @@ FLAGS
A list of security flavors that are allowed to be used during
mount command in NFSv4.1 filestore instances. The security
flavors supported are:
◆ SECURITY_FLAVOR_UNSPECIFIED: SecurityFlavor not set. Defaults to
AUTH_SYS.
◆ AUTH_SYS: The user's UNIX user-id and group-ids are passed in the
clear.
◆ KRB5: The end-user authentication is done using Kerberos V5.
◆ KRB5I: KRB5 plus integrity protection (data packets are tamper
proof).
◆ KRB5P: KRB5I plus privacy protection (data packets are tamper proof
and encrypted).
▫ SECURITY_FLAVOR_UNSPECIFIED: SecurityFlavor not set. Defaults
to AUTH_SYS.
▫ AUTH_SYS: The user's UNIX user-id and group-ids are passed in
the clear.
▫ KRB5: The end-user authentication is done using Kerberos V5.
▫ KRB5I: KRB5 plus integrity protection (data packets are
tamper proof).
▫ KRB5P: KRB5I plus privacy protection (data packets are tamper
proof and encrypted).
This flag argument must be specified if any of the other arguments in this
group are specified.
This flag argument must be specified if any of the other
arguments in this group are specified.
--clear-nfs-export-options
Clears the NfsExportOptions. Must specify --file-share flag if

2
gcloud/beta/functions/deploy
View file

@ -112,8 +112,6 @@ FLAGS
If not provided, the function will use the project's default service
account for Cloud Build.
Only applicable when the --gen2 flag is provided.
--concurrency=CONCURRENCY
Set the maximum number of concurrent requests allowed per container
instance. Leave concurrency unspecified to receive the server default

123
gcloud/beta/network-security/firewall-endpoint-associations/update
View file

@ -6,7 +6,7 @@ SYNOPSIS
gcloud beta network-security firewall-endpoint-associations update
(FIREWALL_ENDPOINT_ASSOCIATION : --zone=ZONE) [--async]
[--max-wait=MAX_WAIT; default="60m"]
[--update-labels=[KEY=VALUE,...] --clear-labels
[--disabled | --update-labels=[KEY=VALUE,...] --clear-labels
| --remove-labels=[KEY,...] --no-tls-inspection-policy
| [--tls-inspection-policy=TLS_INSPECTION_POLICY
: --tls-inspection-policy-project=TLS_INSPECTION_POLICY_PROJECT
@ -84,78 +84,89 @@ FLAGS
specified. See $ gcloud topic datetimes for information on time
formats.
--update-labels=[KEY=VALUE,...]
List of label KEY=VALUE pairs to update. If a label exists, its value
is modified. Otherwise, a new label is created.
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:
--clear-labels
Remove all labels. If --update-labels is also specified then
--clear-labels is applied first.
For example, to remove all labels:
--disabled
Disable a firewall endpoint association. To enable a disabled
association, use:
$ gcloud beta network-security firewall-endpoint-associations \
update --clear-labels
update MY-ASSOCIATION --no-disabled
To remove all existing labels and create two new labels, foo and baz:
--update-labels=[KEY=VALUE,...]
List of label KEY=VALUE pairs to update. If a label exists, its value
is modified. Otherwise, a new label is created.
$ gcloud beta network-security firewall-endpoint-associations \
update --clear-labels --update-labels foo=bar,baz=qux
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.
--remove-labels=[KEY,...]
List of label keys to remove. If a label does not exist it is
silently ignored. If --update-labels is also specified then
--update-labels is applied first.
At most one of these can be specified:
At most one of these can be specified:
--clear-labels
Remove all labels. If --update-labels is also specified then
--clear-labels is applied first.
--no-tls-inspection-policy
Remove TLS inspection policy from this association.
For example, to remove all labels:
TLS Inspection Policy resource - Path to TLS Inspection Policy
configuration to use for intercepting TLS-encrypted traffic in this
network. The arguments in this group can be used to specify the
attributes of this resource.
$ gcloud beta network-security firewall-endpoint-associations \
update --clear-labels
--tls-inspection-policy=TLS_INSPECTION_POLICY
ID of the TLS Inspection Policy or fully qualified identifier for
the TLS Inspection Policy.
To remove all existing labels and create two new labels, foo and
baz:
To set the tls_inspection_policy attribute:
▫ provide the argument --tls-inspection-policy on the command
line.
$ gcloud beta network-security firewall-endpoint-associations \
update --clear-labels --update-labels foo=bar,baz=qux
This flag argument must be specified if any of the other arguments
in this group are specified.
--remove-labels=[KEY,...]
List of label keys to remove. If a label does not exist it is
silently ignored. If --update-labels is also specified then
--update-labels is applied first.
--tls-inspection-policy-project=TLS_INSPECTION_POLICY_PROJECT
Project of the TLS Inspection Policy.
At most one of these can be specified:
To set the tls-inspection-policy-project attribute:
▫ provide the argument --tls-inspection-policy on the command
line with a fully specified name;
▫ provide the argument --tls-inspection-policy-project on the
command line;
▫ provide the argument --project on the command line;
▫ provide the argument FIREWALL_ENDPOINT_ASSOCIATION on the
command line with a fully specified name.
--no-tls-inspection-policy
Remove TLS inspection policy from this association.
--tls-inspection-policy-region=TLS_INSPECTION_POLICY_REGION
Region of the TLS Inspection Policy. NOTE: TLS Inspection Policy
needs to be in the same region as Firewall Plus endpoint resource.
TLS Inspection Policy resource - Path to TLS Inspection Policy
configuration to use for intercepting TLS-encrypted traffic in this
network. The arguments in this group can be used to specify the
attributes of this resource.
To set the tls-inspection-policy-region attribute:
▫ provide the argument --tls-inspection-policy on the command
line with a fully specified name;
▫ provide the argument --tls-inspection-policy-region on the
command line.
--tls-inspection-policy=TLS_INSPECTION_POLICY
ID of the TLS Inspection Policy or fully qualified identifier for
the TLS Inspection Policy.
To set the tls_inspection_policy attribute:
◇ provide the argument --tls-inspection-policy on the command
line.
This flag argument must be specified if any of the other
arguments in this group are specified.
--tls-inspection-policy-project=TLS_INSPECTION_POLICY_PROJECT
Project of the TLS Inspection Policy.
To set the tls-inspection-policy-project attribute:
◇ provide the argument --tls-inspection-policy on the command
line with a fully specified name;
◇ provide the argument --tls-inspection-policy-project on the
command line;
◇ provide the argument --project on the command line;
◇ provide the argument FIREWALL_ENDPOINT_ASSOCIATION on the
command line with a fully specified name.
--tls-inspection-policy-region=TLS_INSPECTION_POLICY_REGION
Region of the TLS Inspection Policy. NOTE: TLS Inspection Policy
needs to be in the same region as Firewall Plus endpoint
resource.
To set the tls-inspection-policy-region attribute:
◇ provide the argument --tls-inspection-policy on the command
line with a fully specified name;
◇ provide the argument --tls-inspection-policy-region on the
command line.
GCLOUD WIDE FLAGS
These flags are available to all commands: --access-token-file, --account,

9
gcloud/beta/run/deploy
View file

@ -28,8 +28,8 @@ SYNOPSIS
--[no-]default-url --description=DESCRIPTION
--execution-environment=EXECUTION_ENVIRONMENT
--remove-containers=[CONTAINER,...] --revision-suffix=REVISION_SUFFIX
--[no-]session-affinity --vpc-connector=VPC_CONNECTOR
--vpc-egress=VPC_EGRESS
--service-min-instances=SERVICE_MIN_INSTANCES --[no-]session-affinity
--vpc-connector=VPC_CONNECTOR --vpc-egress=VPC_EGRESS
--add-cloudsql-instances=[CLOUDSQL-INSTANCES,...]
| --clear-cloudsql-instances
| --remove-cloudsql-instances=[CLOUDSQL-INSTANCES,...]
@ -460,6 +460,11 @@ FLAGS
[--revision-suffix=v1] for a service named 'helloworld', would lead
to a revision named 'helloworld-v1'.
--service-min-instances=SERVICE_MIN_INSTANCES
The minimum number of container instances for this Service to run or
'default' to remove any minimum. These instances will be divided
among all Revisions receiving a percentage of traffic.
--[no-]session-affinity
Whether to enable session affinity for connections to the service.
Use --session-affinity to enable and --no-session-affinity to

9
gcloud/beta/run/services/update
View file

@ -23,8 +23,8 @@ SYNOPSIS
--[no-]cpu-throttling --[no-]default-url
--execution-environment=EXECUTION_ENVIRONMENT
--remove-containers=[CONTAINER,...] --revision-suffix=REVISION_SUFFIX
--[no-]session-affinity --vpc-connector=VPC_CONNECTOR
--vpc-egress=VPC_EGRESS
--service-min-instances=SERVICE_MIN_INSTANCES --[no-]session-affinity
--vpc-connector=VPC_CONNECTOR --vpc-egress=VPC_EGRESS
--add-cloudsql-instances=[CLOUDSQL-INSTANCES,...]
| --clear-cloudsql-instances
| --remove-cloudsql-instances=[CLOUDSQL-INSTANCES,...]
@ -343,6 +343,11 @@ FLAGS
[--revision-suffix=v1] for a service named 'helloworld', would lead
to a revision named 'helloworld-v1'.
--service-min-instances=SERVICE_MIN_INSTANCES
The minimum number of container instances for this Service to run or
'default' to remove any minimum. These instances will be divided
among all Revisions receiving a percentage of traffic.
--[no-]session-affinity
Whether to enable session affinity for connections to the service.
Use --session-affinity to enable and --no-session-affinity to

6
gcloud/beta/workstations/configs/create
View file

@ -141,11 +141,11 @@ FLAGS
address.
--disable-ssh-to-vm
Default value is False. If set, workstations will disable SSH
connections to the root VM.
Default value is False. If set, workstations disable SSH connections to
the root VM.
--disable-tcp-connections
Default value is false. If set, workstations will not allow plain TCP
Default value is false. If set, workstations don't allow plain TCP
connections.
--enable-audit-agent

12
gcloud/beta/workstations/configs/update
View file

@ -248,22 +248,18 @@ FLAGS
At most one of these can be specified:
--disable-ssh-to-vm
Default value is False. If set, workstations will enable SSH
connections to the root VM.
If set, workstations disable SSH connections to the root VM.
--enable-ssh-to-vm
Default value is False. If set, workstations will enable SSH
connections to the root VM.
If set, workstations enable SSH connections to the root VM.
At most one of these can be specified:
--disable-tcp-connections
Default value is false. If set, workstations will allow plain TCP
connections.
If set, workstations don't allow plain TCP connections.
--enable-tcp-connections
Default value is false. If set, workstations will allow plain TCP
connections.
If set, workstations allow plain TCP connections.
GCLOUD WIDE FLAGS
These flags are available to all commands: --access-token-file, --account,