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: Tue Nov 18 10:53:36 UTC 2025

Browse source
This commit is contained in:
Automated 2025-11-18 10:53:36 +00:00
parent 4b21ae6795
commit e1ec13485a
380 changed files with 16045 additions and 783 deletions
Download patch file Download diff file Expand all files Collapse all files

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

@ -152,8 +152,8 @@ OPTIONAL FLAGS
gcloud compute advice calendar-mode --location-policy=us-central1-a=allow,us-central1-b=deny
--region=REGION
Region of the to None. If not specified, you might be prompted to
select a region (interactive mode only).
Region of the resources to get advice on. If not specified, you might
be prompted to select a region (interactive mode only).
To avoid prompting when this flag is omitted, you can set the
compute/region property:

47
gcloud/beta/compute/backend-services/create
View file

@ -43,9 +43,7 @@ SYNOPSIS
[--signed-url-cache-max-age=SIGNED_URL_CACHE_MAX_AGE]
[--subsetting-policy=SUBSETTING_POLICY; default="NONE"]
[--subsetting-subset-size=SUBSETTING_SUBSET_SIZE]
[--timeout=TIMEOUT; default="30s"]
[--tls-settings=[authenticationConfig=AUTHENTICATIONCONFIG],[sni=SNI]]
[--tracking-mode=TRACKING_MODE]
[--timeout=TIMEOUT; default="30s"] [--tracking-mode=TRACKING_MODE]
[--zonal-affinity-spillover=ZONAL_AFFINITY_SPILLOVER]
[--zonal-affinity-spillover-ratio=ZONAL_AFFINITY_SPILLOVER_RATIO]
[--cache-key-query-string-blacklist=[QUERY_STRING,...]
@ -54,7 +52,9 @@ SYNOPSIS
| --custom-metrics-file=[CUSTOM_METRICS,...]]
[--global | --region=REGION]
[--global-health-checks | --health-checks-region=HEALTH_CHECKS_REGION]
[GCLOUD_WIDE_FLAG ...]
[--identity=IDENTITY
| --tls-settings=[authenticationConfig=AUTHENTICATIONCONFIG],
[sni=SNI]] [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(BETA) gcloud beta compute backend-services create creates a backend
@ -742,14 +742,6 @@ FLAGS
The full range of timeout values allowed is 1 - 2,147,483,647 seconds.
--tls-settings=[authenticationConfig=AUTHENTICATIONCONFIG],[sni=SNI]
Configuration for Backend Authenticated TLS and mTLS. May only be
specified when the backend protocol is SSL, HTTPS or HTTP2.
Example: $ gcloud beta compute backend-services create \
--tls-settings='sni=example.com,authenticationConfig=${AUTH_CONF\
IG_NAME}'
--tracking-mode=TRACKING_MODE
Specifies the connection key used for connection tracking. The default
value is PER_CONNECTION. Applicable only for backend service-based
@ -927,6 +919,37 @@ FLAGS
Alternatively, the region can be stored in the environment variable
CLOUDSDK_COMPUTE_REGION.
At most one of these can be specified:
--identity=IDENTITY
Assigns the Managed Identity for the BackendService Workload. Use
this property to configure the load balancer back-end to use
certificates and roots of trust provisioned by the Managed Workload
Identity system. The identity property is the scheme-less SPIFFE ID
to use in the SVID presented by the Load Balancer Workload. The
SPIFFE ID must be a resource starting with the trustDomain property
value, followed by the path to the Managed Workload Identity.
Supported SPIFFE ID format:
//<trust_domain>/ns/<namespace>/sa/<subject> The Trust Domain within
the Managed Identity must refer to a valid Workload Identity Pool.
The TrustConfig and CertificateIssuanceConfig will be inherited from
the Workload Identity Pool. Restrictions: If you set the identity
property, you cannot manually set the following fields:
tlsSettings.sni, tlsSettings.subjectAltNames,
tlsSettings.authenticationConfig. When defining a identity for a
RegionBackendServices, the corresponding Workload Identity Pool must
have a ca_pool configured in the same region. The system will set up
a read-only tlsSettings.authenticationConfig for the Managed
Identity.
--tls-settings=[authenticationConfig=AUTHENTICATIONCONFIG],[sni=SNI]
Configuration for Backend Authenticated TLS and mTLS. May only be
specified when the backend protocol is SSL, HTTPS or HTTP2.
Example: $ gcloud beta compute backend-services create \
--tls-settings='sni=example.com,authenticationConfig=${AUTH_CONF\
IG_NAME}'
GCLOUD WIDE FLAGS
These flags are available to all commands: --access-token-file, --account,
--billing-project, --configuration, --flags-file, --flatten, --format,

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

@ -112,9 +112,10 @@ OPTIONAL FLAGS
compute-optimized-c3d, compute-optimized-h3, compute-optimized-h4d,
general-purpose, general-purpose-c4, general-purpose-c4a,
general-purpose-c4d, general-purpose-e2, general-purpose-n2,
general-purpose-n2d, general-purpose-n4, general-purpose-t2d,
graphics-optimized, memory-optimized, memory-optimized-m3,
memory-optimized-m4, memory-optimized-m4-6tb, memory-optimized-x4-16tb,
general-purpose-n2d, general-purpose-n4, general-purpose-n4d,
general-purpose-t2d, graphics-optimized, graphics-optimized-g4,
memory-optimized, memory-optimized-m3, memory-optimized-m4,
memory-optimized-m4-6tb, memory-optimized-x4-16tb,
memory-optimized-x4-24tb, memory-optimized-x4-32tb,
storage-optimized-z3.

121
gcloud/beta/compute/health-checks/create/grpc-with-tls Normal file
View file

@ -0,0 +1,121 @@
NAME
gcloud beta compute health-checks create grpc-with-tls - create a gRPC with
TLS health check to monitor load balanced instances
SYNOPSIS
gcloud beta compute health-checks create grpc-with-tls NAME
[--check-interval=CHECK_INTERVAL; default="5s"]
[--description=DESCRIPTION] [--enable-logging]
[--grpc-service-name=GRPC_SERVICE_NAME]
[--healthy-threshold=HEALTHY_THRESHOLD; default=2]
[--timeout=TIMEOUT; default="5s"]
[--unhealthy-threshold=UNHEALTHY_THRESHOLD; default=2]
[--global | --region=REGION] [--port=PORT --use-serving-port]
[GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(BETA) gcloud beta compute health-checks create grpc-with-tls is used to
create a non-legacy health check using the gRPC with TLS protocol. You can
use this health check for Google Cloud load balancers or for managed
instance group autohealing. For more information, see the health checks
overview at:
https://cloud.google.com/load-balancing/docs/health-check-concepts
POSITIONAL ARGUMENTS
NAME
Name of the gRPC with TLS health check to create.
FLAGS
--check-interval=CHECK_INTERVAL; default="5s"
How often to perform a health check for an instance. For example,
specifying 10s will run the check every 10 seconds. The default value
is 5s. See $ gcloud topic datetimes for information on duration
formats.
--description=DESCRIPTION
An optional string description for the gRPC with TLS health check.
--enable-logging
Enable logging of health check probe results to Stackdriver. Logging is
disabled by default.
Use --no-enable-logging to disable logging.
--grpc-service-name=GRPC_SERVICE_NAME
An optional gRPC service name string of up to 1024 characters to
include in the gRPC health check request. Only ASCII characters are
allowed.
--healthy-threshold=HEALTHY_THRESHOLD; default=2
The number of consecutive successful health checks before an unhealthy
instance is marked as healthy. The default is 2.
--timeout=TIMEOUT; default="5s"
If Google Compute Engine doesn't receive a healthy response from the
instance by the time specified by the value of this flag, the health
check request is considered a failure. For example, specifying 10s will
cause the check to wait for 10 seconds before considering the request a
failure. The default value is 5s. See $ gcloud topic datetimes for
information on duration formats.
--unhealthy-threshold=UNHEALTHY_THRESHOLD; default=2
The number of consecutive health check failures before a healthy
instance is marked as unhealthy. The default is 2.
At most one of these can be specified:
--global
If set, the gRPC with TLS health check is global.
--region=REGION
Region of the gRPC with TLS health check to create. If not specified,
you might be prompted to select a region (interactive mode only).
To avoid prompting when this flag is omitted, you can set the
compute/region property:
$ gcloud config set compute/region REGION
A list of regions can be fetched by running:
$ gcloud compute regions list
To unset the property, run:
$ gcloud config unset compute/region
Alternatively, the region can be stored in the environment variable
CLOUDSDK_COMPUTE_REGION.
These flags configure the port that the health check monitors.
--port=PORT
The TCP port number that this health check monitors.
--use-serving-port
If given, use the "serving port" for health checks:
▸ When health checking network endpoints in a Network Endpoint
Group, use the port specified with each endpoint.
--use-serving-port must be used when using a Network Endpoint Group
as a backend as this flag specifies the portSpecification option
for a Health Check object.
▸ When health checking other backends, use the port of the backend
service.
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 health-checks create grpc-with-tls
$ gcloud alpha compute health-checks create grpc-with-tls

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

@ -19,6 +19,10 @@ COMMANDS
grpc
(BETA) Create a gRPC health check to monitor load balanced instances.
grpc-with-tls
(BETA) Create a gRPC with TLS health check to monitor load balanced
instances.
http
(BETA) Create a HTTP health check to monitor load balanced instances.

117
gcloud/beta/compute/health-checks/update/grpc-with-tls Normal file
View file

@ -0,0 +1,117 @@
NAME
gcloud beta compute health-checks update grpc-with-tls - update a gRPC with
TLS health check
SYNOPSIS
gcloud beta compute health-checks update grpc-with-tls NAME
[--check-interval=CHECK_INTERVAL] [--description=DESCRIPTION]
[--enable-logging] [--grpc-service-name=GRPC_SERVICE_NAME]
[--healthy-threshold=HEALTHY_THRESHOLD] [--timeout=TIMEOUT]
[--unhealthy-threshold=UNHEALTHY_THRESHOLD]
[--global | --region=REGION] [--port=PORT --use-serving-port]
[GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(BETA) gcloud beta compute health-checks update grpc-with-tls is used to
update an existing gRPC with TLS health check. Only arguments passed in
will be updated on the health check. Other attributes will remain
unaffected.
POSITIONAL ARGUMENTS
NAME
Name of the gRPC with TLS health check to update.
FLAGS
--check-interval=CHECK_INTERVAL
How often to perform a health check for an instance. For example,
specifying 10s will run the check every 10 seconds. See $ gcloud topic
datetimes for information on duration formats.
--description=DESCRIPTION
A textual description for the gRPC with TLS health check. Pass in an
empty string to unset.
--enable-logging
Enable logging of health check probe results to Stackdriver. Logging is
disabled by default.
Use --no-enable-logging to disable logging.
--grpc-service-name=GRPC_SERVICE_NAME
An optional gRPC service name string of up to 1024 characters to
include in the gRPC health check request. Pass in an empty string to
unset. Only ASCII characters are allowed.
--healthy-threshold=HEALTHY_THRESHOLD
The number of consecutive successful health checks before an unhealthy
instance is marked as healthy.
--timeout=TIMEOUT
If Google Compute Engine doesn't receive a healthy response from the
instance by the time specified by the value of this flag, the health
check request is considered a failure. For example, specifying 10s will
cause the check to wait for 10 seconds before considering the request a
failure. See $ gcloud topic datetimes for information on duration
formats.
--unhealthy-threshold=UNHEALTHY_THRESHOLD
The number of consecutive health check failures before a healthy
instance is marked as unhealthy.
At most one of these can be specified:
--global
If set, the gRPC with TLS health check is global.
--region=REGION
Region of the gRPC with TLS health check to update. If not specified,
you might be prompted to select a region (interactive mode only).
To avoid prompting when this flag is omitted, you can set the
compute/region property:
$ gcloud config set compute/region REGION
A list of regions can be fetched by running:
$ gcloud compute regions list
To unset the property, run:
$ gcloud config unset compute/region
Alternatively, the region can be stored in the environment variable
CLOUDSDK_COMPUTE_REGION.
These flags configure the port that the health check monitors.
--port=PORT
The TCP port number that this health check monitors.
--use-serving-port
If given, use the "serving port" for health checks:
▸ When health checking network endpoints in a Network Endpoint
Group, use the port specified with each endpoint.
--use-serving-port must be used when using a Network Endpoint Group
as a backend as this flag specifies the portSpecification option
for a Health Check object.
▸ When health checking other backends, use the port of the backend
service.
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 health-checks update grpc-with-tls
$ gcloud alpha compute health-checks update grpc-with-tls

3
gcloud/beta/compute/health-checks/update/help
View file

@ -19,6 +19,9 @@ COMMANDS
grpc
(BETA) Update a gRPC health check.
grpc-with-tls
(BETA) Update a gRPC with TLS health check.
http
(BETA) Update a HTTP health check.

3
gcloud/beta/compute/help
View file

@ -245,6 +245,9 @@ GROUPS
vpn-tunnels
(BETA) Read and manipulate Compute Engine VPN tunnels.
zone-vm-extension-policies
(BETA) Compute Engine zone VM extension policies.
zones
(BETA) List Compute Engine zones.

3
gcloud/beta/compute/interconnects/attachments/help
View file

@ -23,6 +23,9 @@ GROUPS
groups
(BETA) Create or manipulate interconnect attachment groups.
l2-forwarding
(BETA) Create or manipulate dedicated interconnect attachments.
partner
(BETA) Create or manipulate partner interconnect attachments.

76
gcloud/beta/compute/interconnects/attachments/l2-forwarding/add-mapping Normal file
View file

@ -0,0 +1,76 @@
NAME
gcloud beta compute interconnects attachments l2-forwarding add-mapping -
add new vlan to ip mapping rule to an L2-forwarding attachment
SYNOPSIS
gcloud beta compute interconnects attachments l2-forwarding add-mapping
NAME --vlan-key=VLAN_KEY [--appliance-ip-address=ADDRESSES]
[--appliance-name=APPLIANCE_NAME]
[--inner-vlan-to-appliance-mappings=[innerApplianceIpAddress=INNERAPPLIANCEIPADDRESS],
[innerVlanTags=INNERVLANTAGS]] [--region=REGION]
[GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(BETA) gcloud beta compute interconnects attachments l2-forwarding
add-mapping add new vlan to ip mapping rule to an L2-forwarding attachment.
POSITIONAL ARGUMENTS
NAME
Name of the interconnect attachment to patch.
REQUIRED FLAGS
--vlan-key=VLAN_KEY
Desired VLAN key for L2 forwarding mapping for the attachment. If not
supplied, all mappings will be displayed.
OPTIONAL FLAGS
--appliance-ip-address=ADDRESSES
A single IPv4 or IPv6 address used as the destination IP address for
ingress packets that match on a VLAN tag, but do not match a more
specific inner VLAN tag.
--appliance-name=APPLIANCE_NAME
The name of the L2 appliance mapping rule.
--inner-vlan-to-appliance-mappings=[innerApplianceIpAddress=INNERAPPLIANCEIPADDRESS],[innerVlanTags=INNERVLANTAGS]
A list of mapping rules from inner VLAN tags to IP addresses. If the
inner VLAN is not explicitly mapped to an IP address range, the
applianceIpAddress is used.
--region=REGION
Region of the interconnect attachment to patch. If not specified, you
might be prompted to select a region (interactive mode only).
To avoid prompting when this flag is omitted, you can set the
compute/region property:
$ gcloud config set compute/region REGION
A list of regions can be fetched by running:
$ gcloud compute regions list
To unset the property, run:
$ gcloud config unset compute/region
Alternatively, the region can be stored in the environment variable
CLOUDSDK_COMPUTE_REGION.
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 interconnects attachments l2-forwarding add-mapping
$ gcloud alpha compute interconnects attachments l2-forwarding \
add-mapping

132
gcloud/beta/compute/interconnects/attachments/l2-forwarding/create Normal file
View file

@ -0,0 +1,132 @@
NAME
gcloud beta compute interconnects attachments l2-forwarding create - create
a Compute Engine L2 forwarding interconnect attachment
SYNOPSIS
gcloud beta compute interconnects attachments l2-forwarding create NAME
--geneve-vni=GENEVE_HEADER --interconnect=INTERCONNECT
--network=NETWORK
--tunnel-endpoint-ip-address=TUNNEL_ENDPOINT_IP_ADDRESS
[--bandwidth=BANDWIDTH]
[--default-appliance-ip-address=DEFAULT_APPLIANCE_IP_ADDRESS]
[--description=DESCRIPTION] [--enable-admin] [--mtu=MTU]
[--region=REGION] [--resource-manager-tags=[KEY=VALUE,...]]
[GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(BETA) gcloud beta compute interconnects attachments l2-forwarding create
is used to create a L2 forwarding interconnect attachments. An interconnect
attachment is what binds the underlying connectivity of an interconnect to
a path into and out of the customer's cloud network.
POSITIONAL ARGUMENTS
NAME
Name of the interconnect attachment to create.
REQUIRED FLAGS
--geneve-vni=GENEVE_HEADER
A VNI identier for Geneve header, as defined in
https://datatracker.ietf.org/doc/html/rfc8926, used for L2 forwarding.
--interconnect=INTERCONNECT
The interconnect for the interconnect attachment
--network=NETWORK
The Google Network to use for L2 forwarding.
--tunnel-endpoint-ip-address=TUNNEL_ENDPOINT_IP_ADDRESS
A single IPv4 or IPv6 address. This address will be used as the source
IP address for L2 forwarding packets sent to the appliances, and must
be used as the destination IP address for packets that should be sent
out through this attachment.
OPTIONAL FLAGS
--bandwidth=BANDWIDTH
Provisioned capacity of the attachment. BANDWIDTH must be one of:
50m
50 Mbit/s
100m
100 Mbit/s
200m
200 Mbit/s
300m
300 Mbit/s
400m
400 Mbit/s
500m
500 Mbit/s
1g
1 Gbit/s
2g
2 Gbit/s
5g
5 Gbit/s
10g
10 Gbit/s
20g
20 Gbit/s
50g
50 Gbit/s
100g
100 Gbit/s
--default-appliance-ip-address=DEFAULT_APPLIANCE_IP_ADDRESS
A single IPv4 or IPv6 address used as the default destination IP when
there is no VLAN mapping result found for L2 forwarding. Unset field
indicates the unmatched packet should be dropped.
--description=DESCRIPTION
Human-readable plain-text description of attachment.
--enable-admin
Administrative status of the interconnect attachment. If not provided
on creation, defaults to enabled. When this is enabled, the attachment
is operational and will carry traffic. Use --no-enable-admin to disable
it.
--mtu=MTU
Maximum transmission unit (MTU) is the size of the largest IP packet
passing through this interconnect attachment. Must be one of 1440,
1460, 1500, or 8896. If not specified, the value will default to 1440.
--region=REGION
Region of the interconnect attachment to create. If not specified, you
might be prompted to select a region (interactive mode only).
To avoid prompting when this flag is omitted, you can set the
compute/region property:
$ gcloud config set compute/region REGION
A list of regions can be fetched by running:
$ gcloud compute regions list
To unset the property, run:
$ gcloud config unset compute/region
Alternatively, the region can be stored in the environment variable
CLOUDSDK_COMPUTE_REGION.
--resource-manager-tags=[KEY=VALUE,...]
A comma-separated list of Resource Manager tags to apply to the
interconnect.
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 interconnects attachments l2-forwarding create
$ gcloud alpha compute interconnects attachments l2-forwarding create

63
gcloud/beta/compute/interconnects/attachments/l2-forwarding/describe-mapping Normal file
View file

@ -0,0 +1,63 @@
NAME
gcloud beta compute interconnects attachments l2-forwarding
describe-mapping - describe a Compute Engine L2 forwarding interconnect
attachment
SYNOPSIS
gcloud beta compute interconnects attachments l2-forwarding
describe-mapping NAME --vlan-key=VLAN_KEY [--region=REGION]
[GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(BETA) gcloud beta compute interconnects attachments l2-forwarding
describe-mapping displays all data associated with Compute Engine
interconnect attachment in a project.
POSITIONAL ARGUMENTS
NAME
Name of the interconnect attachment to describe.
REQUIRED FLAGS
--vlan-key=VLAN_KEY
Desired VLAN key for L2 forwarding mapping for the attachment. If not
supplied, all mappings will be displayed.
OPTIONAL FLAGS
--region=REGION
Region of the interconnect attachment to describe. If not specified,
you might be prompted to select a region (interactive mode only).
To avoid prompting when this flag is omitted, you can set the
compute/region property:
$ gcloud config set compute/region REGION
A list of regions can be fetched by running:
$ gcloud compute regions list
To unset the property, run:
$ gcloud config unset compute/region
Alternatively, the region can be stored in the environment variable
CLOUDSDK_COMPUTE_REGION.
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 interconnects attachments l2-forwarding \
describe-mapping
$ gcloud alpha compute interconnects attachments l2-forwarding \
describe-mapping

56
gcloud/beta/compute/interconnects/attachments/l2-forwarding/help Normal file
View file

@ -0,0 +1,56 @@
NAME
gcloud beta compute interconnects attachments l2-forwarding - create or
manipulate dedicated interconnect attachments
SYNOPSIS
gcloud beta compute interconnects attachments l2-forwarding COMMAND
[GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(BETA) Create or manipulate L2 Forwarding Interconnect attachments.
For more information about about interconnect attachments for L2 Forwaring
Interconnect, see the documentation for L2 Forwarding interconnect
attachments
(https://cloud.google.com/network-connectivity/docs/interconnect/how-to/l2-forwarding/creating-l2-attachments).
See also: Interconnect attachments API
(https://cloud.google.com/compute/docs/reference/rest/v1/interconnectAttachments).
GCLOUD WIDE FLAGS
These flags are available to all commands: --help.
Run $ gcloud help for details.
COMMANDS
COMMAND is one of the following:
add-mapping
(BETA) Add new vlan to ip mapping rule to an L2-forwarding attachment.
create
(BETA) Create a Compute Engine L2 forwarding interconnect attachment.
describe-mapping
(BETA) Describe a Compute Engine L2 forwarding interconnect attachment.
list-mapping
(BETA) List Google Compute Engine interconnect attachments.
remove-mapping
(BETA) Remove vlan to ip mapping rule to an L2-forwarding attachment.
update
(BETA) Update a Compute Engine L2 forwarding interconnect attachment.
update-mapping
(BETA) Update vlan to ip mapping rule to an L2-forwarding attachment.
NOTES
This command is currently in beta and might change without notice. These
variants are also available:
$ gcloud compute interconnects attachments l2-forwarding
$ gcloud alpha compute interconnects attachments l2-forwarding

110
gcloud/beta/compute/interconnects/attachments/l2-forwarding/list-mapping Normal file
View file

@ -0,0 +1,110 @@
NAME
gcloud beta compute interconnects attachments l2-forwarding list-mapping -
list Google Compute Engine interconnect attachments
SYNOPSIS
gcloud beta compute interconnects attachments l2-forwarding list-mapping
NAME [--region=REGION] [--filter=EXPRESSION] [--limit=LIMIT]
[--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri]
[GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(BETA) gcloud beta compute interconnects attachments l2-forwarding
list-mapping displays all Google Compute Engine interconnect attachments in
a project.
By default, interconnect attachments from all regions are listed. The
results can be narrowed down using a filter: --filter="region:( REGION ...
)".
EXAMPLES
To list all interconnect attachments in a project in table form, run:
$ gcloud beta compute interconnects attachments l2-forwarding \
list-mapping
To list the URIs of all interconnect attachments in a project, run:
$ gcloud beta compute interconnects attachments l2-forwarding \
list-mapping --uri
To list all interconnect attachments in the us-central1 and europe-west1
regions, run:
$ gcloud beta compute interconnects attachments l2-forwarding \
list-mapping --filter="region:( us-central1 europe-west1 )"
POSITIONAL ARGUMENTS
NAME
Name of the interconnect attachment to describe.
FLAGS
--region=REGION
Region of the interconnect attachment to describe. If not specified,
you might be prompted to select a region (interactive mode only).
To avoid prompting when this flag is omitted, you can set the
compute/region property:
$ gcloud config set compute/region REGION
A list of regions can be fetched by running:
$ gcloud compute regions list
To unset the property, run:
$ gcloud config unset compute/region
Alternatively, the region can be stored in the environment variable
CLOUDSDK_COMPUTE_REGION.
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 compute interconnects attachments l2-forwarding list-mapping
$ gcloud alpha compute interconnects attachments l2-forwarding \
list-mapping

61
gcloud/beta/compute/interconnects/attachments/l2-forwarding/remove-mapping Normal file
View file

@ -0,0 +1,61 @@
NAME
gcloud beta compute interconnects attachments l2-forwarding remove-mapping
- remove vlan to ip mapping rule to an L2-forwarding attachment
SYNOPSIS
gcloud beta compute interconnects attachments l2-forwarding remove-mapping
NAME --vlan-key=VLAN_KEY [--region=REGION] [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(BETA) gcloud beta compute interconnects attachments l2-forwarding
remove-mapping remove vlan to ip mapping rule to an L2-forwarding
attachment.
POSITIONAL ARGUMENTS
NAME
Name of the interconnect attachment to create.
REQUIRED FLAGS
--vlan-key=VLAN_KEY
Desired VLAN key for L2 forwarding mapping for the attachment. If not
supplied, all mappings will be displayed.
OPTIONAL FLAGS
--region=REGION
Region of the interconnect attachment to create. If not specified, you
might be prompted to select a region (interactive mode only).
To avoid prompting when this flag is omitted, you can set the
compute/region property:
$ gcloud config set compute/region REGION
A list of regions can be fetched by running:
$ gcloud compute regions list
To unset the property, run:
$ gcloud config unset compute/region
Alternatively, the region can be stored in the environment variable
CLOUDSDK_COMPUTE_REGION.
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 interconnects attachments l2-forwarding \
remove-mapping
$ gcloud alpha compute interconnects attachments l2-forwarding \
remove-mapping

143
gcloud/beta/compute/interconnects/attachments/l2-forwarding/update Normal file
View file

@ -0,0 +1,143 @@
NAME
gcloud beta compute interconnects attachments l2-forwarding update - update
a Compute Engine L2 forwarding interconnect attachment
SYNOPSIS
gcloud beta compute interconnects attachments l2-forwarding update NAME
[--bandwidth=BANDWIDTH]
[--default-appliance-ip-address=DEFAULT_APPLIANCE_IP_ADDRESS]
[--description=DESCRIPTION] [--enable-admin]
[--geneve-vni=GENEVE_HEADER] [--mtu=MTU] [--region=REGION]
[--update-labels=[KEY=VALUE,...]]
[--clear-labels | --remove-labels=[KEY,...]] [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(BETA) gcloud beta compute interconnects attachments l2-forwarding update
is used to update interconnect attachments. An interconnect attachment is
what binds the underlying connectivity of an interconnect to a path into
and out of the customer's cloud network.
POSITIONAL ARGUMENTS
NAME
Name of the interconnect attachment to patch.
FLAGS
--bandwidth=BANDWIDTH
Provisioned capacity of the attachment. BANDWIDTH must be one of:
50m
50 Mbit/s
100m
100 Mbit/s
200m
200 Mbit/s
300m
300 Mbit/s
400m
400 Mbit/s
500m
500 Mbit/s
1g
1 Gbit/s
2g
2 Gbit/s
5g
5 Gbit/s
10g
10 Gbit/s
20g
20 Gbit/s
50g
50 Gbit/s
100g
100 Gbit/s
--default-appliance-ip-address=DEFAULT_APPLIANCE_IP_ADDRESS
A single IPv4 or IPv6 address used as the default destination IP when
there is no VLAN mapping result found for L2 forwarding. Unset field
indicates the unmatched packet should be dropped.
--description=DESCRIPTION
Human-readable plain-text description of attachment.
--enable-admin
Administrative status of the interconnect attachment. If not provided
on creation, defaults to enabled. When this is enabled, the attachment
is operational and will carry traffic. Use --no-enable-admin to disable
it.
--geneve-vni=GENEVE_HEADER
A VNI identier for Geneve header, as defined in
https://datatracker.ietf.org/doc/html/rfc8926, used for L2 forwarding.
--mtu=MTU
Maximum transmission unit (MTU) is the size of the largest IP packet
passing through this interconnect attachment. Must be one of 1440,
1460, 1500, or 8896. If not specified, the value will default to 1440.
--region=REGION
Region of the interconnect attachment to patch. If not specified, you
might be prompted to select a region (interactive mode only).
To avoid prompting when this flag is omitted, you can set the
compute/region property:
$ gcloud config set compute/region REGION
A list of regions can be fetched by running:
$ gcloud compute regions list
To unset the property, run:
$ gcloud config unset compute/region
Alternatively, the region can be stored in the environment variable
CLOUDSDK_COMPUTE_REGION.
--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:
$ gcloud beta compute interconnects attachments l2-forwarding \
update --clear-labels
To remove all existing labels and create two new labels, foo and baz:
$ gcloud beta compute interconnects attachments l2-forwarding \
update --clear-labels --update-labels foo=bar,baz=qux
--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.
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 interconnects attachments l2-forwarding update
$ gcloud alpha compute interconnects attachments l2-forwarding update

78
gcloud/beta/compute/interconnects/attachments/l2-forwarding/update-mapping Normal file
View file

@ -0,0 +1,78 @@
NAME
gcloud beta compute interconnects attachments l2-forwarding update-mapping
- update vlan to ip mapping rule to an L2-forwarding attachment
SYNOPSIS
gcloud beta compute interconnects attachments l2-forwarding update-mapping
NAME --vlan-key=VLAN_KEY [--appliance-ip-address=ADDRESSES]
[--appliance-name=APPLIANCE_NAME]
[--inner-vlan-to-appliance-mappings=[innerApplianceIpAddress=INNERAPPLIANCEIPADDRESS],
[innerVlanTags=INNERVLANTAGS]] [--region=REGION]
[GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(BETA) gcloud beta compute interconnects attachments l2-forwarding
update-mapping update vlan to ip mapping rule to an L2-forwarding
attachment.
POSITIONAL ARGUMENTS
NAME
Name of the interconnect attachment to create.
REQUIRED FLAGS
--vlan-key=VLAN_KEY
Desired VLAN key for L2 forwarding mapping for the attachment. If not
supplied, all mappings will be displayed.
OPTIONAL FLAGS
--appliance-ip-address=ADDRESSES
A single IPv4 or IPv6 address used as the destination IP address for
ingress packets that match on a VLAN tag, but do not match a more
specific inner VLAN tag.
--appliance-name=APPLIANCE_NAME
The name of the L2 appliance mapping rule.
--inner-vlan-to-appliance-mappings=[innerApplianceIpAddress=INNERAPPLIANCEIPADDRESS],[innerVlanTags=INNERVLANTAGS]
A list of mapping rules from inner VLAN tags to IP addresses. If the
inner VLAN is not explicitly mapped to an IP address range, the
applianceIpAddress is used.
--region=REGION
Region of the interconnect attachment to create. If not specified, you
might be prompted to select a region (interactive mode only).
To avoid prompting when this flag is omitted, you can set the
compute/region property:
$ gcloud config set compute/region REGION
A list of regions can be fetched by running:
$ gcloud compute regions list
To unset the property, run:
$ gcloud config unset compute/region
Alternatively, the region can be stored in the environment variable
CLOUDSDK_COMPUTE_REGION.
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 interconnects attachments l2-forwarding \
update-mapping
$ gcloud alpha compute interconnects attachments l2-forwarding \
update-mapping

13
gcloud/beta/compute/networks/subnets/create
View file

@ -7,6 +7,7 @@ SYNOPSIS
[--description=DESCRIPTION] [--enable-flow-logs]
[--enable-private-ip-google-access]
[--external-ipv6-prefix=EXTERNAL_IPV6_PREFIX]
[--internal-ipv6-prefix=INTERNAL_IPV6_PREFIX]
[--ip-collection=IP_COLLECTION] [--ipv6-access-type=IPV6_ACCESS_TYPE]
[--logging-aggregation-interval=LOGGING_AGGREGATION_INTERVAL]
[--logging-filter-expr=LOGGING_FILTER_EXPR]
@ -63,10 +64,20 @@ OPTIONAL FLAGS
For example, --external-ipv6-prefix=2600:1901:0:0:0:0:0:0/64
--internal-ipv6-prefix=INTERNAL_IPV6_PREFIX
The /64 internal IPv6 CIDR range to assign to this subnet. The range
must be associated with an IPv6 BYOIP sub-prefix that is defined by the
--ip-collection flag. If you specify --ip-collection but not
--internal-ipv6-prefix, a random /64 range is allocated from the
sub-prefix.
For example, --internal-ipv6-prefix 2600:1901:0:0:0:0:0:0/64
--ip-collection=IP_COLLECTION
Resource reference to a public delegated prefix. The
PublicDelegatedPrefix must be a sub-prefix in
EXTERNAL_IPV6_SUBNETWORK_CREATION mode.
EXTERNAL_IPV6_SUBNETWORK_CREATION or INTERNAL_IPV6_SUBNETWORK_CREATION
mode.
--ipv6-access-type=IPV6_ACCESS_TYPE
IPv6 access type can be specified only when the subnet is created, or

13
gcloud/beta/compute/networks/subnets/update
View file

@ -7,6 +7,7 @@ SYNOPSIS
[--add-secondary-ranges-with-reserved-internal-range=RANGE_NAME=INTERNAL_RANGE_URL,
[...]] [--drain-timeout=DRAIN_TIMEOUT; default="0s"]
[--external-ipv6-prefix=EXTERNAL_IPV6_PREFIX]
[--internal-ipv6-prefix=INTERNAL_IPV6_PREFIX]
[--ip-collection=IP_COLLECTION] [--ipv6-access-type=IPV6_ACCESS_TYPE]
[--logging-aggregation-interval=LOGGING_AGGREGATION_INTERVAL]
[--logging-filter-expr=LOGGING_FILTER_EXPR]
@ -67,10 +68,20 @@ FLAGS
For example, --external-ipv6-prefix=2600:1901:0:0:0:0:0:0/64
--internal-ipv6-prefix=INTERNAL_IPV6_PREFIX
The /64 internal IPv6 CIDR range to assign to this subnet. The range
must be associated with an IPv6 BYOIP sub-prefix that is defined by the
--ip-collection flag. If you specify --ip-collection but not
--internal-ipv6-prefix, a random /64 range is allocated from the
sub-prefix.
For example, --internal-ipv6-prefix 2600:1901:0:0:0:0:0:0/64
--ip-collection=IP_COLLECTION
Resource reference to a public delegated prefix. The
PublicDelegatedPrefix must be a sub-prefix in
EXTERNAL_IPV6_SUBNETWORK_CREATION mode.
EXTERNAL_IPV6_SUBNETWORK_CREATION or INTERNAL_IPV6_SUBNETWORK_CREATION
mode.
--ipv6-access-type=IPV6_ACCESS_TYPE
IPv6 access type can be specified only when the subnet is created, or

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

@ -1,11 +1,12 @@
NAME
gcloud beta compute public-advertised-prefixes create - create a public
advertised prefix in the Beta release track
gcloud beta compute public-advertised-prefixes create - creates a Compute
Engine public advertised prefix
SYNOPSIS
gcloud beta compute public-advertised-prefixes create NAME --range=RANGE
[--description=DESCRIPTION] [--dns-verification-ip=DNS_VERIFICATION_IP]
[--pdp-scope=PDP_SCOPE] [GCLOUD_WIDE_FLAG ...]
[--ipv6-access-type=IPV6_ACCESS_TYPE] [--pdp-scope=PDP_SCOPE]
[GCLOUD_WIDE_FLAG ...]
EXAMPLES
To create a public advertised prefix:
@ -36,6 +37,10 @@ OPTIONAL FLAGS
IP address to use for verification. It must be within the IP range
specified in --range.
--ipv6-access-type=IPV6_ACCESS_TYPE
Specifies the IPv6 access type of the public advertised prefix.
IPV6_ACCESS_TYPE must be one of: internal, external.
--pdp-scope=PDP_SCOPE
Specifies how child public delegated prefix will be scoped. PDP_SCOPE
must be one of: GLOBAL, REGIONAL.

2
gcloud/beta/compute/public-advertised-prefixes/help
View file

@ -18,7 +18,7 @@ COMMANDS
COMMAND is one of the following:
create
(BETA) Create a public advertised prefix in the Beta release track.
(BETA) Creates a Compute Engine public advertised prefix.
delete
(BETA) Deletes a Compute Engine public advertised prefix.

2
gcloud/beta/compute/public-delegated-prefixes/create
View file

@ -49,7 +49,7 @@ OPTIONAL FLAGS
--mode=MODE
Specifies the mode of this IPv6 PDP. MODE must be one of: delegation,
external-ipv6-forwarding-rule-creation,
external-ipv6-subnetwork-creation.
external-ipv6-subnetwork-creation, internal-ipv6-subnetwork-creation.
At most one of these can be specified:

2
gcloud/beta/compute/public-delegated-prefixes/delegated-sub-prefixes/create
View file

@ -58,7 +58,7 @@ OPTIONAL FLAGS
--mode=MODE
Specifies the mode of this IPv6 PDP. MODE must be one of: delegation,
external-ipv6-forwarding-rule-creation,
external-ipv6-subnetwork-creation.
external-ipv6-subnetwork-creation, internal-ipv6-subnetwork-creation.
--range=RANGE
IPv4 range from this public delegated prefix that should be delegated,

138
gcloud/beta/compute/zone-vm-extension-policies/create Normal file
View file

@ -0,0 +1,138 @@
NAME
gcloud beta compute zone-vm-extension-policies create - create a Compute
Engine zone VM extension policy
SYNOPSIS
gcloud beta compute zone-vm-extension-policies create NAME
--extensions=EXTENSION_NAME,[...] [--config=KEY=VALUE,[KEY=VALUE,...]]
[--config-from-file=KEY=FILE_PATH,[...]] [--description=DESCRIPTION]
[--inclusion-labels=INCLUSION_LABELS]
[--priority=PRIORITY; default=1000]
[--version=KEY=VALUE,[KEY=VALUE,...]] [--zone=ZONE]
[GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(BETA) Create a Compute Engine zone VM extension policy.
EXAMPLES
To create a zone VM extension policy, run:
$ gcloud beta compute zone-vm-extension-policies create \
test-policy-name --description="test policy" \
--extensions=extension1,extension2 \
--version=extension1=version1,extension2=version2 \
--config=extension1="config1",extension2="config2" \
--inclusion-labels=env=prod \
--inclusion-labels=env=preprod,workload=load-test \
--priority=1000
Available extensions:
ops-agent
google-cloud-sap-extension
google-cloud-workload-extension
POSITIONAL ARGUMENTS
NAME
Name of the zone vm extension policy to create.
REQUIRED FLAGS
--extensions=EXTENSION_NAME,[...]
One or more extensions to be added to the policy.
OPTIONAL FLAGS
--config=KEY=VALUE,[KEY=VALUE,...]
A comma separated key:value list where the key is the extension name
and the value is the desired config for the given extension. The
extension name must be one of the extensions specified in the
--extensions flag.
E.g. --config=filestore='filestore config',ops-agent='ops agent config'
Raises: ArgumentTypeError: If the extension name is not specified in
the --extensions flag.
--config-from-file=KEY=FILE_PATH,[...]
Same as --config except that the value for the entry will be read from
a local file. The extension name must be one of the extensions
specified in the --extensions flag.
It is an error to specify the same extension in both --config and
--config-from-file.
--description=DESCRIPTION
An optional textual description for the this extension policy.
--inclusion-labels=INCLUSION_LABELS
A list of inclusion labels to select the target VMs.
The expected format for a single selector is "key1=value1,key2=value2".
A VM is selected if it has ALL the inclusion labels.
When the option is specified multiple times, it assumes a logical OR
between the selectors.
For example, if the inclusion labels are ["env=prod,workload=frontend",
"workload=backend"], the following VMs will be selected:
◆ VM1: env=prod, workload=frontend, something=else
◆ VM2: env=prod, workload=backend But not:
◆ VM3: env=prod
If not specified, ALL VMs in the zone will be selected.
--priority=PRIORITY; default=1000
The priority of the policy. Lower the number, higher the priority. When
two policies tries to apply the same extension, the one with the higher
priority takes precedence. If the priority is the same, the one with
the more recent update timestamp takes precedence. When a policy is
deleted, the extension would remain installed on the VM if a lower
priority policy still applies.
Range from 0 to 65535. Default is 1000.
--version=KEY=VALUE,[KEY=VALUE,...]
A comma separated key:value list where the key is the extension name
and the value is the desired version for the given extension. The
extension name must be one of the extensions specified in the
--extensions flag. If no version is specified for an extension, the
latest version will be used and will be upgraded automatically.
E.g. --version=filestore=123ABC,ops-agent=456DEF
Raises: ArgumentTypeError: If the extension name is not specified in
the --extensions flag.
--zone=ZONE
Zone of the zone vm extension policy to create. If not specified and
the compute/zone property isn't set, you might be prompted to select a
zone (interactive mode only).
To avoid prompting when this flag is omitted, you can set the
compute/zone property:
$ gcloud config set compute/zone ZONE
A list of zones can be fetched by running:
$ gcloud compute zones list
To unset the property, run:
$ gcloud config unset compute/zone
Alternatively, the zone can be stored in the environment variable
CLOUDSDK_COMPUTE_ZONE.
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. This
variant is also available:
$ gcloud alpha compute zone-vm-extension-policies create

57
gcloud/beta/compute/zone-vm-extension-policies/delete Normal file
View file

@ -0,0 +1,57 @@
NAME
gcloud beta compute zone-vm-extension-policies delete - delete a Compute
Engine zone VM extension policy
SYNOPSIS
gcloud beta compute zone-vm-extension-policies delete NAME [--zone=ZONE]
[GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(BETA) Delete a Compute Engine zone VM extension policy.
EXAMPLES
To delete a zone VM extension policy, run:
$ gcloud beta compute zone-vm-extension-policies delete \
test-policy-name
POSITIONAL ARGUMENTS
NAME
Name of the zone vm extension policy to delete.
FLAGS
--zone=ZONE
Zone of the zone vm extension policy to delete. If not specified and
the compute/zone property isn't set, you might be prompted to select a
zone (interactive mode only).
To avoid prompting when this flag is omitted, you can set the
compute/zone property:
$ gcloud config set compute/zone ZONE
A list of zones can be fetched by running:
$ gcloud compute zones list
To unset the property, run:
$ gcloud config unset compute/zone
Alternatively, the zone can be stored in the environment variable
CLOUDSDK_COMPUTE_ZONE.
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. This
variant is also available:
$ gcloud alpha compute zone-vm-extension-policies delete

57
gcloud/beta/compute/zone-vm-extension-policies/describe Normal file
View file

@ -0,0 +1,57 @@
NAME
gcloud beta compute zone-vm-extension-policies describe - describe a
Compute Engine zone VM extension policy
SYNOPSIS
gcloud beta compute zone-vm-extension-policies describe NAME [--zone=ZONE]
[GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(BETA) Describe a Compute Engine zone VM extension policy.
EXAMPLES
To describe a zone VM extension policy, run:
$ gcloud beta compute zone-vm-extension-policies describe \
test-policy-name
POSITIONAL ARGUMENTS
NAME
Name of the zone vm extension policy to describe.
FLAGS
--zone=ZONE
Zone of the zone vm extension policy to describe. If not specified and
the compute/zone property isn't set, you might be prompted to select a
zone (interactive mode only).
To avoid prompting when this flag is omitted, you can set the
compute/zone property:
$ gcloud config set compute/zone ZONE
A list of zones can be fetched by running:
$ gcloud compute zones list
To unset the property, run:
$ gcloud config unset compute/zone
Alternatively, the zone can be stored in the environment variable
CLOUDSDK_COMPUTE_ZONE.
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. This
variant is also available:
$ gcloud alpha compute zone-vm-extension-policies describe

40
gcloud/beta/compute/zone-vm-extension-policies/help Normal file
View file

@ -0,0 +1,40 @@
NAME
gcloud beta compute zone-vm-extension-policies - compute Engine zone VM
extension policies
SYNOPSIS
gcloud beta compute zone-vm-extension-policies COMMAND
[GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(BETA) Compute Engine zone VM extension policies.
GCLOUD WIDE FLAGS
These flags are available to all commands: --help.
Run $ gcloud help for details.
COMMANDS
COMMAND is one of the following:
create
(BETA) Create a Compute Engine zone VM extension policy.
delete
(BETA) Delete a Compute Engine zone VM extension policy.
describe
(BETA) Describe a Compute Engine zone VM extension policy.
list
(BETA) List Compute Engine zone VM extension policies.
update
(BETA) Update a Compute Engine zone VM extension policy.
NOTES
This command is currently in beta and might change without notice. This
variant is also available:
$ gcloud alpha compute zone-vm-extension-policies

67
gcloud/beta/compute/zone-vm-extension-policies/list Normal file
View file

@ -0,0 +1,67 @@
NAME
gcloud beta compute zone-vm-extension-policies list - list Compute Engine
zone VM extension policies
SYNOPSIS
gcloud beta compute zone-vm-extension-policies list --zone=ZONE
[--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE]
[--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(BETA) List Compute Engine zone VM extension policies.
EXAMPLES
To list all zone VM extension policy, run:
$ gcloud beta compute zone-vm-extension-policies list --zone=<zone>
REQUIRED FLAGS
--zone=ZONE
The zone to list the extension policies from.
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. This
variant is also available:
$ gcloud alpha compute zone-vm-extension-policies list

133
gcloud/beta/compute/zone-vm-extension-policies/update Normal file
View file

@ -0,0 +1,133 @@
NAME
gcloud beta compute zone-vm-extension-policies update - update a Compute
Engine zone VM extension policy
SYNOPSIS
gcloud beta compute zone-vm-extension-policies update NAME
--extensions=EXTENSION_NAME,[...] [--config=KEY=VALUE,[KEY=VALUE,...]]
[--config-from-file=KEY=FILE_PATH,[...]] [--description=DESCRIPTION]
[--inclusion-labels=INCLUSION_LABELS]
[--priority=PRIORITY; default=1000]
[--version=KEY=VALUE,[KEY=VALUE,...]] [--zone=ZONE]
[GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(BETA) Update a Compute Engine zone VM extension policy.
EXAMPLES
To update a zone VM extension policy, run:
$ gcloud beta compute zone-vm-extension-policies update \
test-policy-name --description="test policy" \
--extensions=extension1,extension2 \
--version=extension1=version1,extension2=version2 \
--config=extension1="config1",extension2="config2" \
--inclusion-labels=env=prod \
--inclusion-labels=env=preprod,workload=load-test \
--priority=1000
POSITIONAL ARGUMENTS
NAME
Name of the zone vm extension policy to update.
REQUIRED FLAGS
--extensions=EXTENSION_NAME,[...]
One or more extensions to be added to the policy.
OPTIONAL FLAGS
--config=KEY=VALUE,[KEY=VALUE,...]
A comma separated key:value list where the key is the extension name
and the value is the desired config for the given extension. The
extension name must be one of the extensions specified in the
--extensions flag.
E.g. --config=filestore='filestore config',ops-agent='ops agent config'
Raises: ArgumentTypeError: If the extension name is not specified in
the --extensions flag.
--config-from-file=KEY=FILE_PATH,[...]
Same as --config except that the value for the entry will be read from
a local file. The extension name must be one of the extensions
specified in the --extensions flag.
It is an error to specify the same extension in both --config and
--config-from-file.
--description=DESCRIPTION
An optional textual description for the this extension policy.
--inclusion-labels=INCLUSION_LABELS
A list of inclusion labels to select the target VMs.
The expected format for a single selector is "key1=value1,key2=value2".
A VM is selected if it has ALL the inclusion labels.
When the option is specified multiple times, it assumes a logical OR
between the selectors.
For example, if the inclusion labels are ["env=prod,workload=frontend",
"workload=backend"], the following VMs will be selected:
◆ VM1: env=prod, workload=frontend, something=else
◆ VM2: env=prod, workload=backend But not:
◆ VM3: env=prod
If not specified, ALL VMs in the zone will be selected.
--priority=PRIORITY; default=1000
The priority of the policy. Lower the number, higher the priority. When
two policies tries to apply the same extension, the one with the higher
priority takes precedence. If the priority is the same, the one with
the more recent update timestamp takes precedence. When a policy is
deleted, the extension would remain installed on the VM if a lower
priority policy still applies.
Range from 0 to 65535. Default is 1000.
--version=KEY=VALUE,[KEY=VALUE,...]
A comma separated key:value list where the key is the extension name
and the value is the desired version for the given extension. The
extension name must be one of the extensions specified in the
--extensions flag. If no version is specified for an extension, the
latest version will be used and will be upgraded automatically.
E.g. --version=filestore=123ABC,ops-agent=456DEF
Raises: ArgumentTypeError: If the extension name is not specified in
the --extensions flag.
--zone=ZONE
Zone of the zone vm extension policy to update. If not specified and
the compute/zone property isn't set, you might be prompted to select a
zone (interactive mode only).
To avoid prompting when this flag is omitted, you can set the
compute/zone property:
$ gcloud config set compute/zone ZONE
A list of zones can be fetched by running:
$ gcloud compute zones list
To unset the property, run:
$ gcloud config unset compute/zone
Alternatively, the zone can be stored in the environment variable
CLOUDSDK_COMPUTE_ZONE.
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. This
variant is also available:
$ gcloud alpha compute zone-vm-extension-policies update