imjasonh/gcloud-help
1
0
Fork 0
mirror of https://github.com/imjasonh/gcloud-help synced 2026-07-18 06:47:12 +00:00
Code Activity

gcloud: Thu Oct 30 11:14:52 UTC 2025

Browse source
This commit is contained in:
Automated 2025-10-30 11:14:52 +00:00
parent a763c0bf0a
commit 4b21ae6795
132 changed files with 2511 additions and 503 deletions
Download patch file Download diff file Expand all files Collapse all files

5
gcloud/beta/ai/endpoints/deploy-model
View file

@ -81,8 +81,9 @@ OPTIONAL FLAGS
The type of the accelerator. Choices are 'nvidia-a100-80gb',
'nvidia-b200', 'nvidia-gb200', 'nvidia-h100-80gb',
'nvidia-h100-mega-80gb', 'nvidia-h200-141gb', 'nvidia-l4',
'nvidia-tesla-a100', 'nvidia-tesla-k80', 'nvidia-tesla-p100',
'nvidia-tesla-p4', 'nvidia-tesla-t4', 'nvidia-tesla-v100'.
'nvidia-rtx-pro-6000', 'nvidia-tesla-a100', 'nvidia-tesla-k80',
'nvidia-tesla-p100', 'nvidia-tesla-p4', 'nvidia-tesla-t4',
'nvidia-tesla-v100'.
count
The number of accelerators to attach to each machine running the

27
gcloud/beta/bigtable/materialized-views/describe
View file

@ -4,17 +4,35 @@ NAME
SYNOPSIS
gcloud beta bigtable materialized-views describe
(MATERIALIZED_VIEW : --instance=INSTANCE) [GCLOUD_WIDE_FLAG ...]
(MATERIALIZED_VIEW : --instance=INSTANCE)
[--view=VIEW; default="schema"] [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(BETA) Describe an existing Bigtable materialized view.
EXAMPLES
To view a materialized view's description, run:
To get back information related to a view's schema (for example,
description), run:
$ gcloud beta bigtable materialized-views describe \
my-materialized-view-id --instance=my-instance-id --view=schema
or (because schema is the default view) simply:
$ gcloud beta bigtable materialized-views describe \
my-materialized-view-id --instance=my-instance-id
To get back information related to the view's replication state, run:
$ gcloud beta bigtable materialized-views describe \
my-materialized-view-id --instance=my-instance-id \
--view=replication
To get back all information for the view, run:
$ gcloud beta bigtable materialized-views describe \
my-materialized-view-id --instance=my-instance-id --view=full
POSITIONAL ARGUMENTS
Materialized view resource - The materialized view to describe. The
arguments in this group can be used to specify the attributes of this
@ -47,6 +65,11 @@ POSITIONAL ARGUMENTS
fully specified name;
▸ provide the argument --instance on the command line.
FLAGS
--view=VIEW; default="schema"
Specifies what type of information to return about the view. VIEW must
be one of: full, replication, schema.
GCLOUD WIDE FLAGS
These flags are available to all commands: --access-token-file, --account,
--billing-project, --configuration, --flags-file, --flatten, --format,

20
gcloud/beta/bigtable/materialized-views/list
View file

@ -4,8 +4,9 @@ NAME
SYNOPSIS
gcloud beta bigtable materialized-views list --instance=INSTANCE
[--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE]
[--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...]
[--view=VIEW; default="schema"] [--filter=EXPRESSION] [--limit=LIMIT]
[--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri]
[GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(BETA) List existing Bigtable materialized views.
@ -16,6 +17,16 @@ EXAMPLES
$ gcloud beta bigtable materialized-views list \
--instance=my-instance-id
You may also specify what information to return by supplying the --view
flag, such as:
$ gcloud beta bigtable materialized-views list \
--instance=my-instance-id --view=schema
Currently, only the schema view is supported for this command. This is the
default view, and it returns information about the schemas of your
materialized views.
REQUIRED FLAGS
Instance resource - The instance to list materialized views for. This
represents a Cloud resource. (NOTE) Some attributes are not given
@ -35,6 +46,11 @@ REQUIRED FLAGS
To set the instance attribute:
▸ provide the argument --instance on the command line.
FLAGS
--view=VIEW; default="schema"
Specifies what type of information to return about the view. VIEW must
be one of: full, replication, schema.
LIST COMMAND FLAGS
--filter=EXPRESSION
Apply a Boolean filter EXPRESSION to each resource item to be listed.

21
gcloud/beta/composer/environments/create
View file

@ -23,8 +23,9 @@ SYNOPSIS
[--cloud-sql-ipv4-cidr=CLOUD_SQL_IPV4_CIDR
--composer-network-ipv4-cidr=COMPOSER_NETWORK_IPV4_CIDR
--connection-subnetwork=CONNECTION_SUBNETWORK
--connection-type=CONNECTION_TYPE --enable-private-endpoint
--enable-private-environment --enable-privately-used-public-ips
--connection-type=CONNECTION_TYPE --disable-private-environment
--enable-private-endpoint --enable-private-environment
--enable-privately-used-public-ips
--master-ipv4-cidr=MASTER_IPV4_CIDR
--web-server-ipv4-cidr=WEB_SERVER_IPV4_CIDR]
[--cluster-ipv4-cidr=CLUSTER_IPV4_CIDR
@ -306,6 +307,12 @@ FLAGS
CONNECTION_TYPE must be one of: connection-type-unspecified,
private-service-connect, vpc-peering.
--disable-private-environment
Enables internet connection for Composer components.
When used with Composer 2, this means the environment cluster is
created with public IP addresses on the cluster nodes.
--enable-private-endpoint
Environment cluster is managed using the private IP address of the
master API endpoint. Therefore access to the master endpoint must be
@ -318,13 +325,11 @@ FLAGS
specified.
--enable-private-environment
Environment cluster is created with no public IP addresses on the
cluster nodes.
Disables internet connection from any Composer component.
If not specified, cluster nodes will be assigned public IP addresses.
When used with Composer 3, disable internet connection from any
Composer component.
When used with Composer 2, the environment cluster is created with no
public IP addresses on the cluster nodes. If not specified, cluster
nodes will be assigned public IP addresses.
When used with Composer 1.x, cannot be specified unless
--enable-ip-alias is also specified.

15
gcloud/beta/compute/advice/calendar-mode
View file

@ -6,7 +6,8 @@ SYNOPSIS
gcloud beta compute advice calendar-mode
([--chip-count=CHIP_COUNT --tpu-version=TPU_VERSION
: --workload-type=WORKLOAD_TYPE]
| --machine-type=MACHINE_TYPE --vm-count=VM_COUNT)
| [--machine-type=MACHINE_TYPE --vm-count=VM_COUNT
: --local-ssd=[interface=INTERFACE],[size=SIZE]])
[--duration-range=[max=MAX],[min=MIN]]
[--end-time-range=[from=FROM],[to=TO]]
[--location-policy=[ZONE=POLICY,...]] [--region=REGION]
@ -49,6 +50,8 @@ REQUIRED FLAGS
--tpu-version=TPU_VERSION
The version of Cloud TPU to reserve. TPU_VERSION must be one of:
TPU7X
Cloud TPU v7x
V5E
Cloud TPU v5e Lite
V5P
@ -90,6 +93,16 @@ REQUIRED FLAGS
This flag argument must be specified if any of the other arguments
in this group are specified.
--local-ssd=[interface=INTERFACE],[size=SIZE]
Manage the size and the interface of local SSD to use. See
https://cloud.google.com/compute/docs/disks/local-ssd for more
information.
interface
The kind of disk interface exposed to the VM for this SSD. The
only valid value is nvme.
size
The size of the local SSD in base-2 GB.
OPTIONAL FLAGS
--duration-range=[max=MAX],[min=MIN]
A duration range for the duration of the Future Reservation. Defined as

58
gcloud/beta/compute/backend-buckets/add-iam-policy-binding
View file

@ -4,7 +4,8 @@ NAME
SYNOPSIS
gcloud beta compute backend-buckets add-iam-policy-binding BACKEND_BUCKET
--member=PRINCIPAL --role=ROLE [GCLOUD_WIDE_FLAG ...]
--member=PRINCIPAL --role=ROLE [--global | --region=REGION]
[GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(BETA) Add an IAM policy binding to a Compute Engine backend bucket.
@ -12,34 +13,35 @@ DESCRIPTION
EXAMPLES
To add an IAM policy binding for the role of
'compute.loadBalancerServiceUser' for the user 'test-user@gmail.com' with
backend bucket 'my-backend-bucket' run:
backend bucket 'my-backend-bucket' and region 'REGION', run:
$ gcloud beta compute backend-buckets add-iam-policy-binding \
my-backend-bucket --member='user:test-user@gmail.com' \
--role='roles/compute.loadBalancerServiceUser'
my-backend-bucket --region=REGION \
--member='user:test-user@gmail.com' \
--role='roles/compute.loadBalancerServiceUser'
To add an IAM policy binding for the role of
'compute.loadBalancerServiceUser' for the user 'test-user@gmail.com' with
global backend bucket 'my-backend-bucket', run either of the following:
$ gcloud beta compute backend-buckets add-iam-policy-binding \
my-backend-bucket --global --member='user:test-user@gmail.com' \
--role='roles/compute.loadBalancerServiceUser'
$ gcloud beta compute backend-buckets add-iam-policy-binding \
my-backend-bucket --member='user:test-user@gmail.com' \
--role='roles/compute.loadBalancerServiceUser'
See https://cloud.google.com/iam/docs/managing-policies for details of
policy role and member types.
POSITIONAL ARGUMENTS
Backend bucket resource - The backend bucket for which to add the IAM
policy to. This represents a Cloud resource. (NOTE) Some attributes are
not given arguments in this group but can be set in other ways.
BACKEND_BUCKET
ID of the backend bucket or fully qualified identifier for the backend
bucket.
To set the project attribute:
◆ provide the argument backend_bucket 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.
BACKEND_BUCKET
ID of the backend bucket or fully qualified identifier for the
backend bucket.
To set the backend_bucket attribute:
▸ provide the argument backend_bucket on the command line.
To set the backend_bucket attribute:
+ provide the argument backend_bucket on the command line.
REQUIRED FLAGS
--member=PRINCIPAL
@ -62,6 +64,16 @@ REQUIRED FLAGS
for a custom role, such as
organizations/{ORGANIZATION_ID}/roles/logging.viewer.
OPTIONAL FLAGS
At most one of these can be specified:
--global
If set, the backend bucket is global.
--region=REGION
Region of the backend bucket 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,
@ -71,8 +83,8 @@ GCLOUD WIDE FLAGS
Run $ gcloud help for details.
API REFERENCE
This command uses the compute/beta API. The full documentation for this API
can be found at: https://cloud.google.com/compute/
This command uses the compute API. The full documentation for this API can
be found at: https://cloud.google.com/compute/
NOTES
This command is currently in beta and might change without notice. These

28
gcloud/beta/compute/backend-buckets/create
View file

@ -17,13 +17,28 @@ SYNOPSIS
[--[no-]request-coalescing] [--resource-manager-tags=[KEY=VALUE,...]]
[--serve-while-stale=SERVE_WHILE_STALE]
[--signed-url-cache-max-age=SIGNED_URL_CACHE_MAX_AGE]
[GCLOUD_WIDE_FLAG ...]
[--global | --region=REGION] [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(BETA) gcloud beta compute backend-buckets create is used to create backend
buckets. Backend buckets define Google Cloud Storage buckets that can serve
content. URL maps define which requests are sent to which backend buckets.
To create a global backend bucket, run either of the following:
$ gcloud beta compute backend-buckets create my-backend-bucket
--gcs-bucket-name gcs-bucket-1
--global
$ gcloud beta compute backend-buckets create my-backend-bucket
--gcs-bucket-name gcs-bucket-1
To create a regional backend bucket, run the following:
$ gcloud beta compute backend-buckets create my-backend-bucket
--gcs-bucket-name gcs-bucket-1
--region=us-central1
POSITIONAL ARGUMENTS
BACKEND_BUCKET_NAME
Name of the backend bucket to create.
@ -163,7 +178,7 @@ OPTIONAL FLAGS
The load balancing scheme of the backend bucket. If left blank, the
backend bucket will be compatible with Global External Application Load
Balancer or Classic Application Load Balancer. LOAD_BALANCING_SCHEME
must be (only one value is supported): INTERNAL_MANAGED.
must be one of: INTERNAL_MANAGED, EXTERNAL_MANAGED.
--max-ttl=MAX_TTL
Specifies the maximum allowed TTL for cached content served by this
@ -294,6 +309,15 @@ OPTIONAL FLAGS
This flag only affects signed URL requests.
At most one of these can be specified:
--global
If set, the backend bucket is global.
--region=REGION
Region of the backend bucket to create. 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,

28
gcloud/beta/compute/backend-buckets/delete
View file

@ -3,16 +3,42 @@ NAME
SYNOPSIS
gcloud beta compute backend-buckets delete BACKEND_BUCKET_NAME
[BACKEND_BUCKET_NAME ...] [GCLOUD_WIDE_FLAG ...]
[BACKEND_BUCKET_NAME ...] [--global | --region=REGION]
[GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(BETA) gcloud beta compute backend-buckets delete deletes one or more
backend buckets.
To delete a global backend bucket, run either of the following:
$ gcloud beta compute backend-buckets delete my-backend-bucket
--gcs-bucket-name gcs-bucket-1
--global
$ gcloud beta compute backend-buckets delete my-backend-bucket
--gcs-bucket-name gcs-bucket-1
To delete a regional backend bucket, run the following:
$ gcloud beta compute backend-buckets delete my-backend-bucket
--gcs-bucket-name gcs-bucket-1
--region=us-central1
POSITIONAL ARGUMENTS
BACKEND_BUCKET_NAME [BACKEND_BUCKET_NAME ...]
Names of the backend buckets to delete.
FLAGS
At most one of these can be specified:
--global
If set, the backend buckets are global.
--region=REGION
Region of the backend buckets to delete. 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,

27
gcloud/beta/compute/backend-buckets/describe
View file

@ -3,16 +3,41 @@ NAME
SYNOPSIS
gcloud beta compute backend-buckets describe BACKEND_BUCKET_NAME
[GCLOUD_WIDE_FLAG ...]
[--global | --region=REGION] [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(BETA) gcloud beta compute backend-buckets describe displays all data
associated with a backend bucket in a project.
To describe a global backend bucket, run either of the following:
$ gcloud beta compute backend-buckets describe my-backend-bucket
--gcs-bucket-name gcs-bucket-1
--global
$ gcloud beta compute backend-buckets describe my-backend-bucket
--gcs-bucket-name gcs-bucket-1
To describe a regional backend bucket, run the following:
$ gcloud beta compute backend-buckets describe my-backend-bucket
--gcs-bucket-name gcs-bucket-1
--region=us-central1
POSITIONAL ARGUMENTS
BACKEND_BUCKET_NAME
Name of the backend bucket to describe.
FLAGS
At most one of these can be specified:
--global
If set, the backend bucket is global.
--region=REGION
Region of the backend bucket to describe. 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,

45
gcloud/beta/compute/backend-buckets/get-iam-policy
View file

@ -4,8 +4,8 @@ NAME
SYNOPSIS
gcloud beta compute backend-buckets get-iam-policy BACKEND_BUCKET
[--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE]
[--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...]
[--global | --region=REGION] [--filter=EXPRESSION] [--limit=LIMIT]
[--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(BETA) gcloud beta compute backend-buckets get-iam-policy displays the IAM
@ -16,30 +16,37 @@ DESCRIPTION
set-iam-policy for additional details.
EXAMPLES
To print the IAM policy for a given backend bucket, run:
To print the IAM policy for a given regional backend bucket, run:
$ gcloud beta compute backend-buckets get-iam-policy \
my-backend-bucket --region=REGION
To print the IAM policy for a given global backend bucket, run either of
the following:
$ gcloud beta compute backend-buckets get-iam-policy \
my-backend-bucket --global
$ gcloud beta compute backend-buckets get-iam-policy \
my-backend-bucket
POSITIONAL ARGUMENTS
Backend bucket resource - The network to display the IAM policy for. This
represents a Cloud resource. (NOTE) Some attributes are not given
arguments in this group but can be set in other ways.
BACKEND_BUCKET
ID of the backend bucket or fully qualified identifier for the backend
bucket.
To set the project attribute:
◆ provide the argument backend_bucket on the command line with a fully
specified name;
◆ provide the argument --project on the command line;
◆ set the property core/project.
To set the backend_bucket attribute:
+ provide the argument backend_bucket on the command line.
This must be specified.
FLAGS
At most one of these can be specified:
BACKEND_BUCKET
ID of the backend bucket or fully qualified identifier for the
backend bucket.
--global
If set, the backend bucket is global.
To set the backend_bucket attribute:
▸ provide the argument backend_bucket on the command line.
--region=REGION
Region of the backend bucket to operate on. Overrides the default
compute/region property value for this command invocation.
LIST COMMAND FLAGS
--filter=EXPRESSION
@ -76,8 +83,8 @@ GCLOUD WIDE FLAGS
Run $ gcloud help for details.
API REFERENCE
This command uses the compute/beta API. The full documentation for this API
can be found at: https://cloud.google.com/compute/
This command uses the compute API. The full documentation for this API can
be found at: https://cloud.google.com/compute/
NOTES
This command is currently in beta and might change without notice. These

15
gcloud/beta/compute/backend-buckets/list
View file

@ -4,9 +4,9 @@ NAME
SYNOPSIS
gcloud beta compute backend-buckets list [NAME ...]
[--regexp=REGEXP, -r REGEXP] [--filter=EXPRESSION] [--limit=LIMIT]
[--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri]
[GCLOUD_WIDE_FLAG ...]
[--regexp=REGEXP, -r REGEXP] [--global | --regions=[REGION,...]]
[--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE]
[--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(BETA) gcloud beta compute backend-buckets list displays all Google Compute
@ -37,6 +37,15 @@ FLAGS
Flag --regexp is deprecated. Use --filter="name~'REGEXP'" instead.
At most one of these can be specified:
--global
If provided, only global resources are shown.
--regions=[REGION,...]
If provided, only regional resources are shown. If arguments are
provided, only resources from the given regions are shown.
LIST COMMAND FLAGS
--filter=EXPRESSION
Apply a Boolean filter EXPRESSION to each resource item to be listed.

58
gcloud/beta/compute/backend-buckets/remove-iam-policy-binding
View file

@ -4,7 +4,8 @@ NAME
SYNOPSIS
gcloud beta compute backend-buckets remove-iam-policy-binding
BACKEND_BUCKET --member=PRINCIPAL --role=ROLE [GCLOUD_WIDE_FLAG ...]
BACKEND_BUCKET --member=PRINCIPAL --role=ROLE
[--global | --region=REGION] [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(BETA) Remove an IAM policy binding from a Compute Engine backend bucket.
@ -12,34 +13,35 @@ DESCRIPTION
EXAMPLES
To remove an IAM policy binding for the role of
'roles/compute.loadBalancerServiceUser' for the user 'test-user@gmail.com'
with backend bucket 'my-backend-bucket' run:
with backend bucket 'my-backend-bucket' and region 'REGION', run:
$ gcloud beta compute backend-buckets remove-iam-policy-binding \
my-backend-bucket --member='user:test-user@gmail.com' \
--role='roles/compute.loadBalancerServiceUser'
my-backend-bucket --region=REGION \
--member='user:test-user@gmail.com' \
--role='roles/compute.loadBalancerServiceUser'
To remove an IAM policy binding for the role of
'roles/compute.loadBalancerServiceUser' for the user 'test-user@gmail.com'
with globalbackend bucket 'my-backend-bucket', run either of the following:
$ gcloud beta compute backend-buckets remove-iam-policy-binding \
my-backend-bucket --global --member='user:test-user@gmail.com' \
--role='roles/compute.loadBalancerServiceUser'
$ gcloud beta compute backend-buckets remove-iam-policy-binding \
my-backend-bucket --member='user:test-user@gmail.com' \
--role='roles/compute.loadBalancerServiceUser'
See https://cloud.google.com/iam/docs/managing-policies for details of
policy role and member types.
POSITIONAL ARGUMENTS
Backend bucket resource - The backend bucket for which to remove the IAM
policy from. This represents a Cloud resource. (NOTE) Some attributes are
not given arguments in this group but can be set in other ways.
BACKEND_BUCKET
ID of the backend bucket or fully qualified identifier for the backend
bucket.
To set the project attribute:
◆ provide the argument backend_bucket 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.
BACKEND_BUCKET
ID of the backend bucket or fully qualified identifier for the
backend bucket.
To set the backend_bucket attribute:
▸ provide the argument backend_bucket on the command line.
To set the backend_bucket attribute:
+ provide the argument backend_bucket on the command line.
REQUIRED FLAGS
--member=PRINCIPAL
@ -63,6 +65,16 @@ REQUIRED FLAGS
--role=ROLE
The role to remove the principal from.
OPTIONAL FLAGS
At most one of these can be specified:
--global
If set, the backend bucket is global.
--region=REGION
Region of the backend bucket 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,
@ -72,8 +84,8 @@ GCLOUD WIDE FLAGS
Run $ gcloud help for details.
API REFERENCE
This command uses the compute/beta API. The full documentation for this API
can be found at: https://cloud.google.com/compute/
This command uses the compute API. The full documentation for this API can
be found at: https://cloud.google.com/compute/
NOTES
This command is currently in beta and might change without notice. These

52
gcloud/beta/compute/backend-buckets/set-iam-policy
View file

@ -4,16 +4,24 @@ NAME
SYNOPSIS
gcloud beta compute backend-buckets set-iam-policy BACKEND_BUCKET
POLICY_FILE [GCLOUD_WIDE_FLAG ...]
POLICY_FILE [--global | --region=REGION] [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(BETA) Sets the IAM policy for the given backend bucket as defined in a
JSON or YAML file.
EXAMPLES
The following command reads an IAM policy defined in a JSON file called
'policy.json' and sets it for the backend bucket called
'my-backend-bucket':
The following command will read an IAM policy defined in a JSON file
'policy.json' and set it for the regionalbackend bucket my-backend-bucket:
$ gcloud beta compute backend-buckets set-iam-policy \
my-backend-bucket policy.json --region=REGION
The following commands will read an IAM policy defined in a JSON file
'policy.json' and set it for the global backend bucket my-backend-bucket:
$ gcloud beta compute backend-buckets set-iam-policy \
my-backend-bucket policy.json --global
$ gcloud beta compute backend-buckets set-iam-policy \
my-backend-bucket policy.json
@ -22,24 +30,12 @@ EXAMPLES
policy file format and contents.
POSITIONAL ARGUMENTS
Backend bucket resource - The backend bucket to set the IAM policy for.
This represents a Cloud resource. (NOTE) Some attributes are not given
arguments in this group but can be set in other ways.
BACKEND_BUCKET
ID of the backend bucket or fully qualified identifier for the backend
bucket.
To set the project attribute:
◆ provide the argument backend_bucket 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.
BACKEND_BUCKET
ID of the backend bucket or fully qualified identifier for the
backend bucket.
To set the backend_bucket attribute:
▸ provide the argument backend_bucket on the command line.
To set the backend_bucket attribute:
+ provide the argument backend_bucket on the command line.
POLICY_FILE
Path to a local JSON or YAML formatted file containing a valid policy.
@ -48,6 +44,16 @@ POSITIONAL ARGUMENTS
JSON or YAML file conforming to the structure of a Policy
(https://cloud.google.com/iam/reference/rest/v1/Policy).
FLAGS
At most one of these can be specified:
--global
If set, the backend bucket is global.
--region=REGION
Region of the backend bucket to setIamPolicy. 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,
@ -57,8 +63,8 @@ GCLOUD WIDE FLAGS
Run $ gcloud help for details.
API REFERENCE
This command uses the compute/beta API. The full documentation for this API
can be found at: https://cloud.google.com/compute/
This command uses the compute API. The full documentation for this API can
be found at: https://cloud.google.com/compute/
NOTES
This command is currently in beta and might change without notice. These

26
gcloud/beta/compute/backend-buckets/update
View file

@ -16,7 +16,7 @@ SYNOPSIS
[--custom-response-header=CUSTOM_RESPONSE_HEADER
| --no-custom-response-headers]
[--default-ttl=DEFAULT_TTL | --no-default-ttl]
[--max-ttl=MAX_TTL | --no-max-ttl]
[--global | --region=REGION] [--max-ttl=MAX_TTL | --no-max-ttl]
[--[no-]negative-caching | --no-negative-caching-policies
| --negative-caching-policy=[[CODE=TTL],...]]
[--serve-while-stale=SERVE_WHILE_STALE | --no-serve-while-stale]
@ -26,6 +26,21 @@ DESCRIPTION
(BETA) gcloud beta compute backend-buckets update is used to update backend
buckets.
To delete a global backend bucket, run either of the following:
$ gcloud beta compute backend-buckets update my-backend-bucket
--no-enable-cdn
--global
$ gcloud beta compute backend-buckets update my-backend-bucket
--no-enable-cdn
To delete a regional backend bucket, run the following:
$ gcloud beta compute backend-buckets update my-backend-bucket \
--region=us-central1
--no-enable-cdn
POSITIONAL ARGUMENTS
BACKEND_BUCKET_NAME
Name of the backend bucket to update.
@ -223,6 +238,15 @@ FLAGS
--no-default-ttl
Clears default TTL value.
At most one of these can be specified:
--global
If set, the backend bucket is global.
--region=REGION
Region of the backend bucket to update. Overrides the default
compute/region property value for this command invocation.
At most one of these can be specified:
--max-ttl=MAX_TTL

4
gcloud/beta/compute/composite-health-checks/create
View file

@ -6,7 +6,7 @@ SYNOPSIS
gcloud beta compute composite-health-checks create
(COMPOSITE_HEALTH_CHECK : --region=REGION)
--health-destination=HEALTH_DESTINATION
--health-sources=[HEALTH_SOURCES,...] [--async]
--health-sources=HEALTH_SOURCES,[...] [--async]
[--description=DESCRIPTION] [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
@ -60,7 +60,7 @@ REQUIRED FLAGS
CompositeHealthCheck (cross-region deployment for INTERNAL_MANAGED is
not supported). Can be mutated.
--health-sources=[HEALTH_SOURCES,...]
--health-sources=HEALTH_SOURCES,[...]
URLs to the HealthSource resources whose results are AND'ed. I.e. the
aggregated result is HEALTHY only if all sources are HEALTHY. Must have
at least 1. Must not have more than 10. Must be regional and in the

4
gcloud/beta/compute/composite-health-checks/update
View file

@ -6,7 +6,7 @@ SYNOPSIS
gcloud beta compute composite-health-checks update
(COMPOSITE_HEALTH_CHECK : --region=REGION)
(--description=DESCRIPTION --health-destination=HEALTH_DESTINATION
--health-sources=[HEALTH_SOURCES,...]) [--async]
--health-sources=HEALTH_SOURCES,[...]) [--async]
[GCLOUD_WIDE_FLAG ...]
DESCRIPTION
@ -65,7 +65,7 @@ REQUIRED FLAGS
region as the CompositeHealthCheck (cross-region deployment for
INTERNAL_MANAGED is not supported). Can be mutated.
--health-sources=[HEALTH_SOURCES,...]
--health-sources=HEALTH_SOURCES,[...]
URLs to the HealthSource resources whose results are AND'ed. I.e. the
aggregated result is HEALTHY only if all sources are HEALTHY. Must
have at least 1. Must not have more than 10. Must be regional and in

2
gcloud/beta/compute/future-reservations/create
View file

@ -120,6 +120,8 @@ REQUIRED FLAGS
--tpu-version=TPU_VERSION
The version of Cloud TPU to reserve. TPU_VERSION must be one of:
TPU7X
Cloud TPU v7x
V5E
Cloud TPU v5e Lite
V5P

4
gcloud/beta/compute/health-sources/create
View file

@ -4,7 +4,7 @@ NAME
SYNOPSIS
gcloud beta compute health-sources create (HEALTH_SOURCE : --region=REGION)
--health-aggregation-policy=HEALTH_AGGREGATION_POLICY
--sources=[SOURCES,...] [--async] [--description=DESCRIPTION]
--sources=SOURCES,[SOURCES,...] [--async] [--description=DESCRIPTION]
[--source-type=SOURCE_TYPE; default="backend-service"]
[GCLOUD_WIDE_FLAG ...]
@ -57,7 +57,7 @@ REQUIRED FLAGS
URL to the health aggregation policy resource. Must be set. Must be
regional and in the same region as the HealthSource. Can be mutated.
--sources=[SOURCES,...]
--sources=SOURCES,[SOURCES,...]
URLs to the source resources. Must be size 1. Must be a BackendService
if the sourceType is BACKEND_SERVICE. The BackendService must have load
balancing scheme INTERNAL or INTERNAL_MANAGED and must be regional and

4
gcloud/beta/compute/health-sources/update
View file

@ -5,7 +5,7 @@ SYNOPSIS
gcloud beta compute health-sources update (HEALTH_SOURCE : --region=REGION)
(--description=DESCRIPTION
--health-aggregation-policy=HEALTH_AGGREGATION_POLICY
--sources=[SOURCES,...]) [--async] [GCLOUD_WIDE_FLAG ...]
--sources=SOURCES,[SOURCES,...]) [--async] [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(BETA) Update a health source.
@ -61,7 +61,7 @@ REQUIRED FLAGS
URL to the health aggregation policy resource. Must be set. Must be
regional and in the same region as the HealthSource. Can be mutated.
--sources=[SOURCES,...]
--sources=SOURCES,[SOURCES,...]
URLs to the source resources. Must be size 1. Must be a
BackendService if the sourceType is BACKEND_SERVICE. The
BackendService must have load balancing scheme INTERNAL or

23
gcloud/beta/compute/service-attachments/update
View file

@ -5,7 +5,7 @@ NAME
SYNOPSIS
gcloud beta compute service-attachments update NAME
[--connection-preference=CONNECTION_PREFERENCE]
[--consumer-accept-list=[PROJECT_OR_NETWORK=LIMIT,...]]
[--consumer-accept-list=[PROJECT_OR_NETWORK_OR_ENDPOINT=LIMIT,...]]
[--consumer-reject-list=[REJECT_LIST,...]] [--description=DESCRIPTION]
[--[no-]enable-proxy-protocol]
[--nat-subnets=NAT_SUBNETS,[NAT_SUBNETS,...]]
@ -51,21 +51,22 @@ FLAGS
Only accept connection requests from consumers with the approval of
the service provider.
--consumer-accept-list=[PROJECT_OR_NETWORK=LIMIT,...]
Specifies which consumer projects or networks are allowed to connect to
the service attachment. Each project or network has a connection limit.
A given service attachment can manage connections at either the project
or network level. Therefore, both the accept and reject lists for a
given service attachment must contain either only projects or only
networks.
--consumer-accept-list=[PROJECT_OR_NETWORK_OR_ENDPOINT=LIMIT,...]
Specifies which consumer projects/networks/endpoints are allowed to
connect to the service attachment. Each project or network has a
connection limit. For endpoints, the connection limit is optional. Both
the accept and reject lists for a given service attachment must contain
either only one of projects, networks or endpoints.
For example, --consumer-accept-list myProjectId1=20 accepts a consumer
project myProjectId1 with connection limit 20; --consumer-accept-list
projects/myProjectId1/global/networks/myNet1=20 accepts a consumer
network myNet1 with connection limit 20
network myNet1 with connection limit 20 --consumer-accept-list
projects/myProjectId1/regions/myRegion1/forwardingRules/8167352512 also
accepts a consumer endpoint with ID 8167352512.
◆ PROJECT_OR_NETWORK - Consumer project ID, project number or network
URL.
◆ PROJECT_OR_NETWORK_OR_ENDPOINT - Consumer project ID/number or
network URL orendpoint URL.
◆ CONNECTION_LIMIT - The maximum number of allowed connections.
--consumer-reject-list=[REJECT_LIST,...]

9
gcloud/beta/compute/ssl-policies/create
View file

@ -47,11 +47,13 @@ FLAGS
TLS 1.1.
1.2
TLS 1.2.
1.3
TLS 1.3.
--profile=PROFILE; default="COMPATIBLE"
SSL policy profile. Changing profile from CUSTOM to
COMPATIBLE|MODERN|RESTRICTED will clear the custom-features field.
PROFILE must be one of:
COMPATIBLE|MODERN|RESTRICTED|FIPS_202205 will clear the custom-features
field. PROFILE must be one of:
COMPATIBLE
Compatible profile. Allows the broadest set of clients, even those
@ -64,6 +66,9 @@ FLAGS
gcloud compute ssl-policies list-available-features
FIPS_202205
FIPS_202205 profile. Supports a reduced set of SSL features,
intended to meet stricter compliance requirements.
MODERN
Modern profile. Supports a wide set of SSL features, allowing
modern clients to negotiate SSL.

9
gcloud/beta/compute/ssl-policies/update
View file

@ -44,11 +44,13 @@ FLAGS
TLS 1.1.
1.2
TLS 1.2.
1.3
TLS 1.3.
--profile=PROFILE
SSL policy profile. Changing profile from CUSTOM to
COMPATIBLE|MODERN|RESTRICTED will clear the custom-features field.
PROFILE must be one of:
COMPATIBLE|MODERN|RESTRICTED|FIPS_202205 will clear the custom-features
field. PROFILE must be one of:
COMPATIBLE
Compatible profile. Allows the broadest set of clients, even those
@ -61,6 +63,9 @@ FLAGS
gcloud compute ssl-policies list-available-features
FIPS_202205
FIPS_202205 profile. Supports a reduced set of SSL features,
intended to meet stricter compliance requirements.
MODERN
Modern profile. Supports a wide set of SSL features, allowing
modern clients to negotiate SSL.

3
gcloud/beta/config/get
View file

@ -137,6 +137,9 @@ AVAILABLE PROPERTIES
Token used to route traces of service requests for investigation of
issues. This token will be provided by Google support.
universe_domain
Sets the domain of the universe to use for API requests.
user_output_enabled
True, by default. If False, messages to the user and command output
on both standard output and standard error will be suppressed.

3
gcloud/beta/config/help
View file

@ -169,6 +169,9 @@ AVAILABLE PROPERTIES
Token used to route traces of service requests for investigation of
issues. This token will be provided by Google support.
universe_domain
Sets the domain of the universe to use for API requests.
user_output_enabled
True, by default. If False, messages to the user and command output
on both standard output and standard error will be suppressed.

3
gcloud/beta/config/list
View file

@ -181,6 +181,9 @@ AVAILABLE PROPERTIES
Token used to route traces of service requests for investigation of
issues. This token will be provided by Google support.
universe_domain
Sets the domain of the universe to use for API requests.
user_output_enabled
True, by default. If False, messages to the user and command output
on both standard output and standard error will be suppressed.

3
gcloud/beta/config/set
View file

@ -184,6 +184,9 @@ AVAILABLE PROPERTIES
Token used to route traces of service requests for investigation of
issues. This token will be provided by Google support.
universe_domain
Sets the domain of the universe to use for API requests.
user_output_enabled
True, by default. If False, messages to the user and command output
on both standard output and standard error will be suppressed.

3
gcloud/beta/config/unset
View file

@ -145,6 +145,9 @@ AVAILABLE PROPERTIES
Token used to route traces of service requests for investigation of
issues. This token will be provided by Google support.
universe_domain
Sets the domain of the universe to use for API requests.
user_output_enabled
True, by default. If False, messages to the user and command output
on both standard output and standard error will be suppressed.

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

@ -70,7 +70,8 @@ SYNOPSIS
--fleet-project=PROJECT_ID_OR_NUMBER
--membership-type=MEMBERSHIP_TYPE --unset-membership-type
| --clear-maintenance-window | --remove-maintenance-exclusion=NAME
| [--add-maintenance-exclusion-end=TIME_STAMP
| [(--add-maintenance-exclusion-end=TIME_STAMP
| --add-maintenance-exclusion-until-end-of-support)
: --add-maintenance-exclusion-name=NAME
--add-maintenance-exclusion-scope=SCOPE
--add-maintenance-exclusion-start=TIME_STAMP]
@ -1090,14 +1091,6 @@ REQUIRED FLAGS
--add-maintenance-exclusion-end=2000-12-31T23:59:59 \
--add-maintenance-exclusion-scope=no_upgrades
--add-maintenance-exclusion-end=TIME_STAMP
End time of the exclusion window. Must take place after the start
time. 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.
--add-maintenance-exclusion-name=NAME
A descriptor for the exclusion that can be used to remove it. If
not specified, it will be autogenerated.
@ -1113,6 +1106,17 @@ REQUIRED FLAGS
not specified, the current time will be used. See $ gcloud topic
datetimes for information on time formats.
Exactly one of these must be specified:
--add-maintenance-exclusion-end=TIME_STAMP
End time of the exclusion window. Must take place after the
start time. See $ gcloud topic datetimes for information on
time formats.
--add-maintenance-exclusion-until-end-of-support
End time of the exclusion window is the end of the cluster's
support.
Set a flexible maintenance window by specifying a window that recurs
per an RFC 5545 RRULE. Non-emergency maintenance will occur in the
recurring windows.

19
gcloud/beta/container/fleet/clusterupgrade/create
View file

@ -22,6 +22,11 @@ EXAMPLES
FLAGS
--default-upgrade-soaking=DEFAULT_UPGRADE_SOAKING
Note: This flag only applies to Rollout Sequencing v1, not Rollout
Sequencing v2 (which uses custom stages). If using Rollout Sequencing
v1 and this flag is not provided, a default value of 7 days will be
used.
Configures the default soaking duration for each upgrade propagating
through the current fleet to become "COMPLETE". Soaking begins after
all clusters in the fleet are on the target version, or after 30 days
@ -47,16 +52,16 @@ FLAGS
Upgrade soaking override.
Defines a specific soaking time override for a particular upgrade
propagating through the current fleet that supercedes the default
soaking duration configured by `--default-upgrade-soaking`.
Defines a specific soaking time override for a particular upgrade
propagating through the current fleet that supercedes the default soaking
duration configured by --default-upgrade-soaking.
To set an upgrade soaking override of 12 hours for the upgrade with
name, `k8s_control_plane`, and version, `1.23.1-gke.1000`, run:
To set an upgrade soaking override of 12 hours for the upgrade with name,
k8s_control_plane, and version, 1.23.1-gke.1000, run:
$ gcloud beta container fleet clusterupgrade create \
--add-upgrade-soaking-override=12h \
--upgrade-selector=name="k8s_control_plane",\
--add-upgrade-soaking-override=12h \
--upgrade-selector=name="k8s_control_plane",\
version="1.23.1-gke.1000"
--add-upgrade-soaking-override=ADD_UPGRADE_SOAKING_OVERRIDE

19
gcloud/beta/container/fleet/clusterupgrade/update
View file

@ -23,6 +23,11 @@ EXAMPLES
FLAGS
--default-upgrade-soaking=DEFAULT_UPGRADE_SOAKING
Note: This flag only applies to Rollout Sequencing v1, not Rollout
Sequencing v2 (which uses custom stages). If using Rollout Sequencing
v1 and this flag is not provided, a default value of 7 days will be
used.
Configures the default soaking duration for each upgrade propagating
through the current fleet to become "COMPLETE". Soaking begins after
all clusters in the fleet are on the target version, or after 30 days
@ -53,16 +58,16 @@ FLAGS
Upgrade soaking override.
Defines a specific soaking time override for a particular upgrade
propagating through the current fleet that supercedes the default
soaking duration configured by `--default-upgrade-soaking`.
Defines a specific soaking time override for a particular upgrade
propagating through the current fleet that supercedes the default
soaking duration configured by --default-upgrade-soaking.
To set an upgrade soaking override of 12 hours for the upgrade with
name, `k8s_control_plane`, and version, `1.23.1-gke.1000`, run:
To set an upgrade soaking override of 12 hours for the upgrade with
name, k8s_control_plane, and version, 1.23.1-gke.1000, run:
$ gcloud beta container fleet clusterupgrade update \
--add-upgrade-soaking-override=12h \
--upgrade-selector=name="k8s_control_plane",\
--add-upgrade-soaking-override=12h \
--upgrade-selector=name="k8s_control_plane",\
version="1.23.1-gke.1000"
--add-upgrade-soaking-override=ADD_UPGRADE_SOAKING_OVERRIDE

19
gcloud/beta/container/hub/clusterupgrade/create
View file

@ -22,6 +22,11 @@ EXAMPLES
FLAGS
--default-upgrade-soaking=DEFAULT_UPGRADE_SOAKING
Note: This flag only applies to Rollout Sequencing v1, not Rollout
Sequencing v2 (which uses custom stages). If using Rollout Sequencing
v1 and this flag is not provided, a default value of 7 days will be
used.
Configures the default soaking duration for each upgrade propagating
through the current fleet to become "COMPLETE". Soaking begins after
all clusters in the fleet are on the target version, or after 30 days
@ -47,16 +52,16 @@ FLAGS
Upgrade soaking override.
Defines a specific soaking time override for a particular upgrade
propagating through the current fleet that supercedes the default
soaking duration configured by `--default-upgrade-soaking`.
Defines a specific soaking time override for a particular upgrade
propagating through the current fleet that supercedes the default soaking
duration configured by --default-upgrade-soaking.
To set an upgrade soaking override of 12 hours for the upgrade with
name, `k8s_control_plane`, and version, `1.23.1-gke.1000`, run:
To set an upgrade soaking override of 12 hours for the upgrade with name,
k8s_control_plane, and version, 1.23.1-gke.1000, run:
$ gcloud beta container hub clusterupgrade create \
--add-upgrade-soaking-override=12h \
--upgrade-selector=name="k8s_control_plane",\
--add-upgrade-soaking-override=12h \
--upgrade-selector=name="k8s_control_plane",\
version="1.23.1-gke.1000"
--add-upgrade-soaking-override=ADD_UPGRADE_SOAKING_OVERRIDE

19
gcloud/beta/container/hub/clusterupgrade/update
View file

@ -23,6 +23,11 @@ EXAMPLES
FLAGS
--default-upgrade-soaking=DEFAULT_UPGRADE_SOAKING
Note: This flag only applies to Rollout Sequencing v1, not Rollout
Sequencing v2 (which uses custom stages). If using Rollout Sequencing
v1 and this flag is not provided, a default value of 7 days will be
used.
Configures the default soaking duration for each upgrade propagating
through the current fleet to become "COMPLETE". Soaking begins after
all clusters in the fleet are on the target version, or after 30 days
@ -53,16 +58,16 @@ FLAGS
Upgrade soaking override.
Defines a specific soaking time override for a particular upgrade
propagating through the current fleet that supercedes the default
soaking duration configured by `--default-upgrade-soaking`.
Defines a specific soaking time override for a particular upgrade
propagating through the current fleet that supercedes the default
soaking duration configured by --default-upgrade-soaking.
To set an upgrade soaking override of 12 hours for the upgrade with
name, `k8s_control_plane`, and version, `1.23.1-gke.1000`, run:
To set an upgrade soaking override of 12 hours for the upgrade with
name, k8s_control_plane, and version, 1.23.1-gke.1000, run:
$ gcloud beta container hub clusterupgrade update \
--add-upgrade-soaking-override=12h \
--upgrade-selector=name="k8s_control_plane",\
--add-upgrade-soaking-override=12h \
--upgrade-selector=name="k8s_control_plane",\
version="1.23.1-gke.1000"
--add-upgrade-soaking-override=ADD_UPGRADE_SOAKING_OVERRIDE

11
gcloud/beta/container/node-pools/create
View file

@ -9,6 +9,7 @@ SYNOPSIS
gpu-partition-size=GPU_PARTITION_SIZE,
gpu-sharing-strategy=GPU_SHARING_STRATEGY,
max-shared-clients-per-gpu=MAX_SHARED_CLIENTS_PER_GPU],...]]
[--accelerator-network-profile=ACCELERATOR_NETWORK_PROFILE]
[--additional-node-network=[network=NETWORK_NAME,
subnetwork=SUBNETWORK_NAME,...]]
[--additional-pod-network=[subnetwork=SUBNETWORK_NAME,
@ -146,6 +147,16 @@ FLAGS
(Optional) The max number of containers allowed to share each GPU
on the node. This field is used together with gpu-sharing-strategy.
--accelerator-network-profile=ACCELERATOR_NETWORK_PROFILE
Accelerator Network Profile that will be used by the node pool.
Currently only the auto value is supported. A compatible Accelerator
machine type needs to be specified with the --machine-type flag. An
Accelerator Network Profiles will be created if it does not exist.
ACCELERATOR_NETWORK_PROFILE must be (only one value is supported):
auto.
--additional-node-network=[network=NETWORK_NAME,subnetwork=SUBNETWORK_NAME,...]
Attach an additional network interface to each node in the pool. This
parameter can be specified up to 7 times.

15
gcloud/beta/dns/project-info/describe
View file

@ -3,7 +3,8 @@ NAME
for a project
SYNOPSIS
gcloud beta dns project-info describe PROJECT_ID [GCLOUD_WIDE_FLAG ...]
gcloud beta dns project-info describe PROJECT_ID [--location=LOCATION]
[GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(BETA) This command displays Cloud DNS related information for your project
@ -14,10 +15,22 @@ EXAMPLES
$ gcloud beta dns project-info describe my_project_id
To display Cloud DNS related information for your project in us-east1-c,
run:
$ gcloud beta dns project-info describe my_project_id \
--location=us-east1-c
POSITIONAL ARGUMENTS
PROJECT_ID
The identifier for the project you want DNS related info for.
FLAGS
--location=LOCATION
Specifies the desired service location the request is sent to. Defaults
to Cloud DNS global service. Use --location=global if you want to
target the global service.
GCLOUD WIDE FLAGS
These flags are available to all commands: --access-token-file, --account,
--billing-project, --configuration, --flags-file, --flatten, --format,

48
gcloud/beta/eventarc/pipelines/create
View file

@ -14,10 +14,10 @@ SYNOPSIS
[oauth_token_authentication_scope=OAUTH_TOKEN_AUTHENTICATION_SCOPE],
[output_payload_format_json=OUTPUT_PAYLOAD_FORMAT_JSON],
[output_payload_format_avro_schema_definition=OUTPUT_PAYLOAD_FORMAT_AVRO_SCHEMA_DEFINITION],
[output_payload_format_protobuf_schema_definition=OUTPUT_PAYLOAD_FORMAT_PROTOBUF_SCHEMA_DEFINITION]|[...]
[output_payload_format_protobuf_schema_definition=OUTPUT_PAYLOAD_FORMAT_PROTOBUF_SCHEMA_DEFINITION]#[...]
[--async] [--crypto-key=CRYPTO_KEY] [--labels=[KEY=VALUE,...]]
[--logging-config=LOGGING_CONFIG]
[--mediations=[transformation_template=TRANSFORMATION_TEMPLATE|...]]
[--mediations=[transformation_template=TRANSFORMATION_TEMPLATE#...]]
[--input-payload-format-avro-schema-definition=INPUT_PAYLOAD_FORMAT_AVRO_SCHEMA_DEFINITION | --input-payload-format-json=INPUT_PAYLOAD_FORMAT_JSON | --input-payload-format-protobuf-schema-definition=INPUT_PAYLOAD_FORMAT_PROTOBUF_SCHEMA_DEFINITION]
[--max-retry-attempts=MAX_RETRY_ATTEMPTS
--max-retry-delay=MAX_RETRY_DELAY --min-retry-delay=MIN_RETRY_DELAY]
@ -28,13 +28,12 @@ DESCRIPTION
EXAMPLES
To create a new pipeline my-pipeline in location us-central1 with its
destination targeting HTTP endpoint URI 'https://example-endpoint.com' and
network attachment 'my-network-attachment', run:
destination targeting HTTP endpoint URI 'https://example-endpoint.com',
run:
$ gcloud beta eventarc pipelines create my-pipeline \
--location=us-central1 \
--destinations=http_endpoint_uri='https://example-endpoint.com',\
network_attachment=my-network-attachment
--destinations=http_endpoint_uri='https://example-endpoint.com'
To create a new pipeline my-pipeline in location us-central1 with an HTTP
endpoint URI destination and a message binding template, run:
@ -43,8 +42,7 @@ EXAMPLES
--location=us-central1 \
--destinations=http_endpoint_uri='https://example-endpoint.com',\
http_endpoint_message_binding_template='{"headers":
{"new-header-key":
"new-header-value"}}',network_attachment=my-network-attachment
{"new-header-key": "new-header-value"}}'
To create a new pipeline my-pipeline in location us-central1 with a Cloud
Workflow destination my-workflow, run:
@ -80,7 +78,6 @@ EXAMPLES
$ gcloud beta eventarc pipelines create my-pipeline \
--location=us-central1 \
--destinations=http_endpoint_uri='https://example-endpoint.com',\
network_attachment=my-network-attachment,\
google_oidc_authentication_service_account=example-service-account@e\
xample-project.gserviceaccount.iam.com
@ -92,7 +89,6 @@ EXAMPLES
$ gcloud beta eventarc pipelines create my-pipeline \
--location=us-central1 \
--destinations=http_endpoint_uri='https://example-endpoint.com',\
network_attachment=my-network-attachment,\
google_oidc_authentication_service_account=example-service-account@e\
xample-project.gserviceaccount.iam.com,\
google_oidc_authentication_audience='https://example.com'
@ -105,7 +101,6 @@ EXAMPLES
$ gcloud beta eventarc pipelines create my-pipeline \
--location=us-central1 \
--destinations=http_endpoint_uri='https://example-endpoint.com',\
network_attachment=my-network-attachment,\
oauth_token_authentication_service_account=example-service-account@e\
xample-project.gserviceaccount.iam.com
@ -118,7 +113,6 @@ EXAMPLES
$ gcloud beta eventarc pipelines create my-pipeline \
--location=us-central1 \
--destinations=http_endpoint_uri='https://example-endpoint.com',\
network_attachment=my-network-attachment,\
oauth_token_authentication_service_account=example-service-account@e\
xample-project.gserviceaccount.iam.com,\
oauth_token_authentication_scope='https://www.googleapis.com/auth/cl\
@ -131,7 +125,6 @@ EXAMPLES
$ gcloud beta eventarc pipelines create my-pipeline \
--location=us-central1 \
--destinations=http_endpoint_uri='https://example-endpoint.com',\
network_attachment=my-network-attachment,\
output_payload_format_json= --input-payload-format-json=
To create a new pipeline my-pipeline in location us-central1 with an HTTP
@ -141,7 +134,6 @@ EXAMPLES
$ gcloud beta eventarc pipelines create my-pipeline \
--location=us-central1 \
--destinations=http_endpoint_uri='https://example-endpoint.com',\
network_attachment=my-network-attachment,\
output_payload_format_avro_schema_definition='{"type": "record",
"name": "my_record", "fields": [{"name": "my_field", "type":
"string"}]}' \
@ -156,7 +148,6 @@ EXAMPLES
$ gcloud beta eventarc pipelines create my-pipeline \
--location=us-central1 \
--destinations=http_endpoint_uri='https://example-endpoint.com',\
network_attachment=my-network-attachment,\
output_payload_format_protobuf_schema_definition='syntax =
"proto3"; message Location { string home_address = 1; }' \
--input-payload-format-protobuf-schema-definition='syntax =
@ -168,10 +159,9 @@ EXAMPLES
$ gcloud beta eventarc pipelines create my-pipeline \
--location=us-central1 \
--destinations=http_endpoint_uri='https://example-endpoint.com',\
network_attachment=my-network-attachment \
--mediations=transformation_template='message.removeFields(["dat\
a.credit_card_number","data.ssn"])'
--destinations=http_endpoint_uri='https://example-endpoint.com'-\
-mediations=transformation_template='message.removeFields(["data.cre\
dit_card_number","data.ssn"])'
To create a new pipeline my-pipeline in location us-central1 with an HTTP
endpoint URI destination https://example-endpoint.com and a INFO level
@ -179,8 +169,8 @@ EXAMPLES
$ gcloud beta eventarc pipelines create my-pipeline \
--location=us-central1 \
--destinations=http_endpoint_uri='https://example-endpoint.com',\
network_attachment=my-network-attachment --logging_config=INFO
--destinations=http_endpoint_uri='https://example-endpoint.com'-\
-logging_config=INFO
To create a new pipeline my-pipeline in location us-central1 with an HTTP
endpoint URI destination https://example-endpoint.com and a custom retry
@ -188,9 +178,8 @@ EXAMPLES
$ gcloud beta eventarc pipelines create my-pipeline \
--location=us-central1 \
--destinations=http_endpoint_uri='https://example-endpoint.com',\
network_attachment=my-network-attachment --max-retry-attempts=10 \
--min-retry-delay=2s --max-retry-delay=64s
--destinations=http_endpoint_uri='https://example-endpoint.com' \
--max-retry-attempts=10 --min-retry-delay=2s --max-retry-delay=64s
To create a new pipeline my-pipeline in location us-central1 with an HTTP
endpoint URI destination https://example-endpoint.com and a Cloud KMS
@ -198,10 +187,9 @@ EXAMPLES
$ gcloud beta eventarc pipelines create my-pipeline \
--location=us-central1 \
--destinations=http_endpoint_uri='https://example-endpoint.com',\
network_attachment=my-network-attachment \
--crypto-key=projects/PROJECT_ID/locations/KMS_LOCATION/\
keyRings/KEYRING/cryptoKeys/KEY
--destinations=http_endpoint_uri='https://example-endpoint.com' \
--crypto-key=projects/PROJECT_ID/locations/KMS_LOCATION/keyRings/\
KEYRING/cryptoKeys/KEY
POSITIONAL ARGUMENTS
Pipeline resource - The pipeline to create. The arguments in this group
@ -238,7 +226,7 @@ POSITIONAL ARGUMENTS
▸ set the property eventarc/location.
REQUIRED FLAGS
--destinations=[http_endpoint_uri=URI],[http_endpoint_message_binding_template=HTTP_ENDPOINT_MESSAGE_BINDING_TEMPLATE],[workflow=WORKFLOW],[message_bus=MESSAGE_BUS],[pubsub_topic=PUBSUB_TOPIC],[project=PROJECT],[location=LOCATION],[network_attachment=NETWORK_ATTACHMENT],[google_oidc_authentication_service_account=GOOGLE_OIDC_AUTHENTICATION_SERVICE_ACCOUNT],[google_oidc_authentication_audience=GOOGLE_OIDC_AUTHENTICATION_AUDIENCE],[oauth_token_authentication_service_account=OAUTH_TOKEN_AUTHENTICATION_SERVICE_ACCOUNT],[oauth_token_authentication_scope=OAUTH_TOKEN_AUTHENTICATION_SCOPE],[output_payload_format_json=OUTPUT_PAYLOAD_FORMAT_JSON],[output_payload_format_avro_schema_definition=OUTPUT_PAYLOAD_FORMAT_AVRO_SCHEMA_DEFINITION],[output_payload_format_protobuf_schema_definition=OUTPUT_PAYLOAD_FORMAT_PROTOBUF_SCHEMA_DEFINITION]|[...]
--destinations=[http_endpoint_uri=URI],[http_endpoint_message_binding_template=HTTP_ENDPOINT_MESSAGE_BINDING_TEMPLATE],[workflow=WORKFLOW],[message_bus=MESSAGE_BUS],[pubsub_topic=PUBSUB_TOPIC],[project=PROJECT],[location=LOCATION],[network_attachment=NETWORK_ATTACHMENT],[google_oidc_authentication_service_account=GOOGLE_OIDC_AUTHENTICATION_SERVICE_ACCOUNT],[google_oidc_authentication_audience=GOOGLE_OIDC_AUTHENTICATION_AUDIENCE],[oauth_token_authentication_service_account=OAUTH_TOKEN_AUTHENTICATION_SERVICE_ACCOUNT],[oauth_token_authentication_scope=OAUTH_TOKEN_AUTHENTICATION_SCOPE],[output_payload_format_json=OUTPUT_PAYLOAD_FORMAT_JSON],[output_payload_format_avro_schema_definition=OUTPUT_PAYLOAD_FORMAT_AVRO_SCHEMA_DEFINITION],[output_payload_format_protobuf_schema_definition=OUTPUT_PAYLOAD_FORMAT_PROTOBUF_SCHEMA_DEFINITION]#[...]
The pipeline's destinations. This flag can be repeated to add more
destinations to the list. Currently, only one destination is supported
per pipeline. A destination is specified in a dict format. For more
@ -550,7 +538,7 @@ OPTIONAL FLAGS
The logging config of the pipeline. LOGGING_CONFIG must be one of:
NONE, DEBUG, INFO, NOTICE, WARNING, ERROR, CRITICAL, ALERT, EMERGENCY.
--mediations=[transformation_template=TRANSFORMATION_TEMPLATE|...]
--mediations=[transformation_template=TRANSFORMATION_TEMPLATE#...]
The different ways to modify the pipeline. Currently, only one
mediation is supported per pipeline.

8
gcloud/beta/eventarc/pipelines/update
View file

@ -15,9 +15,9 @@ SYNOPSIS
[oauth_token_authentication_scope=OAUTH_TOKEN_AUTHENTICATION_SCOPE],
[output_payload_format_json=OUTPUT_PAYLOAD_FORMAT_JSON],
[output_payload_format_avro_schema_definition=OUTPUT_PAYLOAD_FORMAT_AVRO_SCHEMA_DEFINITION],
[output_payload_format_protobuf_schema_definition=OUTPUT_PAYLOAD_FORMAT_PROTOBUF_SCHEMA_DEFINITION]|[...]]
[output_payload_format_protobuf_schema_definition=OUTPUT_PAYLOAD_FORMAT_PROTOBUF_SCHEMA_DEFINITION]#[...]]
[--logging-config=LOGGING_CONFIG]
[--mediations=[transformation_template=TRANSFORMATION_TEMPLATE|...]]
[--mediations=[transformation_template=TRANSFORMATION_TEMPLATE#...]]
[--update-labels=[KEY=VALUE,...]]
[--clear-crypto-key | --crypto-key=CRYPTO_KEY]
[--clear-labels | --remove-labels=[KEY,...]]
@ -78,7 +78,7 @@ FLAGS
Return immediately, without waiting for the operation in progress to
complete.
--destinations=[http_endpoint_uri=URI],[http_endpoint_message_binding_template=HTTP_ENDPOINT_MESSAGE_BINDING_TEMPLATE],[workflow=WORKFLOW],[message_bus=MESSAGE_BUS],[pubsub_topic=PUBSUB_TOPIC],[project=PROJECT],[location=LOCATION],[network_attachment=NETWORK_ATTACHMENT],[google_oidc_authentication_service_account=GOOGLE_OIDC_AUTHENTICATION_SERVICE_ACCOUNT],[google_oidc_authentication_audience=GOOGLE_OIDC_AUTHENTICATION_AUDIENCE],[oauth_token_authentication_service_account=OAUTH_TOKEN_AUTHENTICATION_SERVICE_ACCOUNT],[oauth_token_authentication_scope=OAUTH_TOKEN_AUTHENTICATION_SCOPE],[output_payload_format_json=OUTPUT_PAYLOAD_FORMAT_JSON],[output_payload_format_avro_schema_definition=OUTPUT_PAYLOAD_FORMAT_AVRO_SCHEMA_DEFINITION],[output_payload_format_protobuf_schema_definition=OUTPUT_PAYLOAD_FORMAT_PROTOBUF_SCHEMA_DEFINITION]|[...]
--destinations=[http_endpoint_uri=URI],[http_endpoint_message_binding_template=HTTP_ENDPOINT_MESSAGE_BINDING_TEMPLATE],[workflow=WORKFLOW],[message_bus=MESSAGE_BUS],[pubsub_topic=PUBSUB_TOPIC],[project=PROJECT],[location=LOCATION],[network_attachment=NETWORK_ATTACHMENT],[google_oidc_authentication_service_account=GOOGLE_OIDC_AUTHENTICATION_SERVICE_ACCOUNT],[google_oidc_authentication_audience=GOOGLE_OIDC_AUTHENTICATION_AUDIENCE],[oauth_token_authentication_service_account=OAUTH_TOKEN_AUTHENTICATION_SERVICE_ACCOUNT],[oauth_token_authentication_scope=OAUTH_TOKEN_AUTHENTICATION_SCOPE],[output_payload_format_json=OUTPUT_PAYLOAD_FORMAT_JSON],[output_payload_format_avro_schema_definition=OUTPUT_PAYLOAD_FORMAT_AVRO_SCHEMA_DEFINITION],[output_payload_format_protobuf_schema_definition=OUTPUT_PAYLOAD_FORMAT_PROTOBUF_SCHEMA_DEFINITION]#[...]
The pipeline's destinations. This flag can be repeated to add more
destinations to the list. Currently, only one destination is supported
per pipeline. A destination is specified in a dict format. For more
@ -372,7 +372,7 @@ FLAGS
The logging config of the pipeline. LOGGING_CONFIG must be one of:
NONE, DEBUG, INFO, NOTICE, WARNING, ERROR, CRITICAL, ALERT, EMERGENCY.
--mediations=[transformation_template=TRANSFORMATION_TEMPLATE|...]
--mediations=[transformation_template=TRANSFORMATION_TEMPLATE#...]
The different ways to modify the pipeline. Currently, only one
mediation is supported per pipeline.

5
gcloud/beta/iam/workforce-pools/providers/scim-tenants/create
View file

@ -6,7 +6,7 @@ SYNOPSIS
gcloud beta iam workforce-pools providers scim-tenants create
(SCIM_TENANT : --location=LOCATION
--provider=PROVIDER --workforce-pool=WORKFORCE_POOL)
[--claim-mapping=[KEY=VALUE,...]] [--description=DESCRIPTION]
--claim-mapping=[KEY=VALUE,...] [--description=DESCRIPTION]
[--display-name=DISPLAY_NAME] [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
@ -85,10 +85,11 @@ POSITIONAL ARGUMENTS
specified name;
▸ provide the argument --workforce-pool on the command line.
FLAGS
REQUIRED FLAGS
--claim-mapping=[KEY=VALUE,...]
A comma-separated list of KEY=VALUE pairs defining attribute mappings.
OPTIONAL FLAGS
--description=DESCRIPTION
Optional, user-specified description for the SCIM tenant (max 256
characters).

3
gcloud/beta/network-management/vpc-flow-logs-configs/query-org-vpc-flow-logs-configs
View file

@ -18,7 +18,8 @@ EXAMPLES
To fetch all the organization-level VPC Flow Logs configurations associated
with the project, run:
$ gcloud beta network-management vpc-flow-logs-configs \ query-org-vpc-flow-logs-configs --location=global
$ gcloud beta network-management vpc-flow-logs-configs \
query-org-vpc-flow-logs-configs --location=global
REQUIRED FLAGS
Location resource - The parent resource of the VpcFlowLogsConfig,

4
gcloud/beta/network-management/vpc-flow-logs-configs/show-effective-flow-logs-configs
View file

@ -19,8 +19,8 @@ EXAMPLES
in project my-project, run:
$ gcloud beta network-management vpc-flow-logs-configs \
show-effective-flow-logs-configs --location=global \
--resource="projects/my-project/global/networks/my-network"
show-effective-flow-logs-configs --location=global \
--resource="projects/my-project/global/networks/my-network"
REQUIRED FLAGS
Location resource - The parent resource of the VpcFlowLogsConfig,

62
gcloud/beta/network-security/mirroring-endpoint-groups/create
View file

@ -5,8 +5,8 @@ NAME
SYNOPSIS
gcloud beta network-security mirroring-endpoint-groups create
(MIRRORING_ENDPOINT_GROUP : --location=LOCATION)
(--mirroring-deployment-group=MIRRORING_DEPLOYMENT_GROUP
: --mirroring-deployment-group-location=MIRRORING_DEPLOYMENT_GROUP_LOCATION)
([--mirroring-deployment-group=MIRRORING_DEPLOYMENT_GROUP
: --mirroring-deployment-group-location=MIRRORING_DEPLOYMENT_GROUP_LOCATION])
[--async] [--description=DESCRIPTION] [--labels=[KEY=VALUE,...]]
[--max-wait=MAX_WAIT; default="20m"] [GCLOUD_WIDE_FLAG ...]
@ -81,41 +81,41 @@ POSITIONAL ARGUMENTS
▸ provide the argument --location on the command line.
REQUIRED FLAGS
Mirroring deployment group resource - Mirroring Deployment Group. 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 --mirroring-deployment-group on the command line
with a fully specified name;
◆ provide the argument --project on the command line;
◆ set the property core/project.
This must be specified.
--mirroring-deployment-group=MIRRORING_DEPLOYMENT_GROUP
ID of the mirroring deployment group or fully qualified identifier
for the mirroring deployment group.
Mirroring deployment group resource - Mirroring Deployment Group. 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 id attribute:
▸ provide the argument --mirroring-deployment-group on the command
line.
To set the project attribute:
▸ provide the argument --mirroring-deployment-group on the command
line with a fully specified name;
▸ provide the argument --project on the command line;
▸ set the property core/project.
This flag argument must be specified if any of the other arguments in
this group are specified.
--mirroring-deployment-group=MIRRORING_DEPLOYMENT_GROUP
ID of the mirroring deployment group or fully qualified identifier
for the mirroring deployment group.
--mirroring-deployment-group-location=MIRRORING_DEPLOYMENT_GROUP_LOCATION
Location of the mirroring deployment group.
To set the id attribute:
▫ provide the argument --mirroring-deployment-group on the
command line.
To set the location attribute:
▸ provide the argument --mirroring-deployment-group on the command
line with a fully specified name;
▸ provide the argument --mirroring-deployment-group-location on the
command line;
▸ provide the argument --location on the command line;
▸ provide the argument MIRRORING_ENDPOINT_GROUP on the command line
with a fully specified name.
This flag argument must be specified if any of the other arguments
in this group are specified.
--mirroring-deployment-group-location=MIRRORING_DEPLOYMENT_GROUP_LOCATION
Location of the mirroring deployment group.
To set the location attribute:
▫ provide the argument --mirroring-deployment-group on the
command line with a fully specified name;
▫ provide the argument --mirroring-deployment-group-location on
the command line;
▫ provide the argument --location on the command line;
▫ provide the argument MIRRORING_ENDPOINT_GROUP on the command
line with a fully specified name.
OPTIONAL FLAGS
--async

6
gcloud/beta/services/disable
View file

@ -53,8 +53,10 @@ GCLOUD WIDE FLAGS
Run $ gcloud help for details.
NOTES
This command is currently in beta and might change without notice. This
variant is also available:
This command is currently in beta and might change without notice. These
variants are also available:
$ gcloud services disable
$ gcloud alpha services disable

6
gcloud/beta/services/enable
View file

@ -48,8 +48,10 @@ GCLOUD WIDE FLAGS
Run $ gcloud help for details.
NOTES
This command is currently in beta and might change without notice. This
variant is also available:
This command is currently in beta and might change without notice. These
variants are also available:
$ gcloud services enable
$ gcloud alpha services enable

20
gcloud/beta/services/groups/help Normal file
View file

@ -0,0 +1,20 @@
NAME
gcloud beta services groups - view service group information
SYNOPSIS
gcloud beta services groups COMMAND [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(BETA) View service group information.
GCLOUD WIDE FLAGS
These flags are available to all commands: --help.
Run $ gcloud help for details.
NOTES
This command is currently in beta and might change without notice. This
variant is also available:
$ gcloud alpha services groups

6
gcloud/beta/services/help
View file

@ -32,6 +32,9 @@ GROUPS
api-keys
(BETA) Manage API keys.
groups
(BETA) View service group information.
identity
(BETA) Manage service identity.
@ -41,6 +44,9 @@ GROUPS
peered-dns-domains
(BETA) Peered DNS domains for various private service connections.
policies
(BETA) Get/update consumer policies and get the effective policy.
vpc-peerings
(BETA) VPC Peerings to various services.

6
gcloud/beta/services/list
View file

@ -77,8 +77,10 @@ GCLOUD WIDE FLAGS
Run $ gcloud help for details.
NOTES
This command is currently in beta and might change without notice. This
variant is also available:
This command is currently in beta and might change without notice. These
variants are also available:
$ gcloud services list
$ gcloud alpha services list

21
gcloud/beta/services/policies/help Normal file
View file

@ -0,0 +1,21 @@
NAME
gcloud beta services policies - get/update consumer policies and get the
effective policy
SYNOPSIS
gcloud beta services policies COMMAND [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(BETA) Get/update consumer policies and get the effective policy.
GCLOUD WIDE FLAGS
These flags are available to all commands: --help.
Run $ gcloud help for details.
NOTES
This command is currently in beta and might change without notice. This
variant is also available:
$ gcloud alpha services policies

5
gcloud/beta/workbench/instances/create
View file

@ -27,6 +27,7 @@ SYNOPSIS
default="cloud-notebooks-managed"]
--custom-gpu-driver-path=CUSTOM_GPU_DRIVER_PATH --install-gpu-driver
--data-disk-encryption=DATA_DISK_ENCRYPTION
--data-disk-resource-policies=[RESOURCE_POLICIES,...]
--data-disk-size=DATA_DISK_SIZE --data-disk-type=DATA_DISK_TYPE
[--data-disk-kms-key=DATA_DISK_KMS_KEY
: --data-disk-encryption-key-keyring=DATA_DISK_ENCRYPTION_KEY_KEYRING
@ -295,6 +296,10 @@ FLAGS
Disk encryption method used on the data disk, defaults to GMEK.
DATA_DISK_ENCRYPTION must be one of: GMEK, CMEK.
--data-disk-resource-policies=[RESOURCE_POLICIES,...]
Resource policies to apply to the data disk. Format:
projects/{project}/regions/{region}/resourcePolicies/{policy}.
--data-disk-size=DATA_DISK_SIZE
Size of data disk in GB attached to this instance, up to a maximum
of 64000 GB (64 TB). The minimum recommended value is 100 GB. If