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

gcloud: Wed Mar 26 10:55:24 UTC 2025

This commit is contained in:
Automated 2025-03-26 10:55:24 +00:00
parent e555fef0aa
commit be9483c980
310 changed files with 9868 additions and 540 deletions

View file

@ -14,6 +14,8 @@ SYNOPSIS
[--balancing-mode=BALANCING_MODE] [--capacity-scaler=CAPACITY_SCALER]
[--description=DESCRIPTION] [--failover]
[--max-utilization=MAX_UTILIZATION] [--preference=PREFERENCE]
[--custom-metrics=[CUSTOM_METRICS,...]
| --custom-metrics-file=[CUSTOM_METRICS,...]]
[--global | --region=REGION]
[--max-connections=MAX_CONNECTIONS
| --max-connections-per-endpoint=MAX_CONNECTIONS_PER_ENDPOINT
@ -253,6 +255,80 @@ OPTIONAL FLAGS
Backends with this preference setting are used up to their capacity
limits first, while optimizing overall network latency.
At most one of these can be specified:
--custom-metrics=[CUSTOM_METRICS,...]
List of custom metrics that are used for CUSTOM_METRICS balancing
mode and WEIGHTED_ROUND_ROBIN locality load balancing policy.
Example:
$ gcloud compute backend-services add-backend \
--custom-metrics='name=my-signal,maxUtilization=0.8,dryRun=true'
$ gcloud compute backend-services add-backend \
--custom-metrics='name=my-signal,maxUtilization=0.8,dryRun=true'\
--custom-metrics='name=my-signal2,maxUtilization=0.2'
$ gcloud compute backend-services add-backend \
--custom-metrics='[{"name" : "my-signal", "maxUtilization" :
0.8, "dryRun" : true}, {"name" : "my-signal2", "maxUtilization" :
0.1}]'
Sets custom_metrics value.
dryRun
Sets dryRun value.
maxUtilization
Sets maxUtilization value.
name
Required, Sets name value.
Shorthand Example:
--custom-metrics=dryRun=boolean,maxUtilization=float,name=string --custom-metrics=dryRun=boolean,maxUtilization=float,name=string
JSON Example:
--custom-metrics='[{"dryRun": boolean, "maxUtilization": float, "name": "string"}]'
File Example:
--custom-metrics=path_to_file.(yaml|json)
--custom-metrics-file=[CUSTOM_METRICS,...]
File path to json file with custom metrics that are used for
CUSTOM_METRICS balancing mode and WEIGHTED_ROUND_ROBIN locality load
balancing policy.
Example:
$ gcloud compute backend-services add-backend \
--custom-metrics-file='customMetric.json'
Sets custom_metrics_file value.
dryRun
Sets dryRun value.
maxUtilization
Sets maxUtilization value.
name
Required, Sets name value.
Shorthand Example:
--custom-metrics-file=dryRun=boolean,maxUtilization=float,name=string --custom-metrics-file=dryRun=boolean,maxUtilization=float,name=string
JSON Example:
--custom-metrics-file='[{"dryRun": boolean, "maxUtilization": float, "name": "string"}]'
File Example:
--custom-metrics-file=path_to_file.(yaml|json)
At most one of these can be specified:
--global

View file

@ -43,6 +43,8 @@ SYNOPSIS
[--timeout=TIMEOUT; default="30s"] [--tracking-mode=TRACKING_MODE]
[--cache-key-query-string-blacklist=[QUERY_STRING,...]
| --cache-key-query-string-whitelist=QUERY_STRING,[...]]
[--custom-metrics=[CUSTOM_METRICS,...]
| --custom-metrics-file=[CUSTOM_METRICS,...]]
[--global | --region=REGION]
[--global-health-checks | --health-checks-region=HEALTH_CHECKS_REGION]
[GCLOUD_WIDE_FLAG ...]
@ -745,6 +747,72 @@ FLAGS
percent encoded and not treated as delimiters. Can only be applied
for global resources.
At most one of these can be specified:
--custom-metrics=[CUSTOM_METRICS,...]
List of custom metrics that are used for WEIGHTED_ROUND_ROBIN
locality load balancing policy.
Example:
$ gcloud compute backend-services create \
--custom-metrics='name=my-signal,dryRun=true'
$ gcloud compute backend-services create \
--custom-metrics='name=my-signal,dryRun=true' \
--custom-metrics='name=my-signal2'
$ gcloud compute backend-services create \
--custom-metrics='[{"name" : "my-signal", "dryRun" : true},
{"name" : "my-signal2"}]'
Sets custom_metrics value.
dryRun
Sets dryRun value.
name
Required, Sets name value.
Shorthand Example:
--custom-metrics=dryRun=boolean,name=string --custom-metrics=dryRun=boolean,name=string
JSON Example:
--custom-metrics='[{"dryRun": boolean, "name": "string"}]'
File Example:
--custom-metrics=path_to_file.(yaml|json)
--custom-metrics-file=[CUSTOM_METRICS,...]
File path to json file with custom metrics that are used for
WEIGHTED_ROUND_ROBIN locality load balancing policy.
Example:
$ gcloud compute backend-services create \
--custom-metrics-file='customMetric.json'
Sets custom_metrics_file value.
dryRun
Sets dryRun value.
name
Required, Sets name value.
Shorthand Example:
--custom-metrics-file=dryRun=boolean,name=string --custom-metrics-file=dryRun=boolean,name=string
JSON Example:
--custom-metrics-file='[{"dryRun": boolean, "name": "string"}]'
File Example:
--custom-metrics-file=path_to_file.(yaml|json)
At most one of these can be specified:
--global

View file

@ -37,6 +37,8 @@ SYNOPSIS
| --no-bypass-cache-on-request-headers]
[--cache-key-query-string-blacklist=[QUERY_STRING,...]
| --cache-key-query-string-whitelist=QUERY_STRING,[...]]
[--clear-custom-metrics | --custom-metrics=[CUSTOM_METRICS,...]
| --custom-metrics-file=[CUSTOM_METRICS,...]]
[--client-ttl=CLIENT_TTL | --no-client-ttl]
[--custom-request-header=CUSTOM_REQUEST_HEADER
| --no-custom-request-headers]
@ -571,6 +573,75 @@ FLAGS
percent encoded and not treated as delimiters. Can only be applied
for global resources.
At most one of these can be specified:
--clear-custom-metrics
Clears current list of CUSTOM_METRICS.
--custom-metrics=[CUSTOM_METRICS,...]
List of custom metrics that are used for WEIGHTED_ROUND_ROBIN
locality load balancing policy.
Example:
$ gcloud compute backend-services update \
--custom-metrics='name=my-signal,dryRun=true'
$ gcloud compute backend-services update \
--custom-metrics='name=my-signal,dryRun=true' \
--custom-metrics='name=my-signal2'
$ gcloud compute backend-services update \
--custom-metrics='[{"name" : "my-signal", "dryRun" : true},
{"name" : "my-signal2"}]'
Sets custom_metrics value.
dryRun
Sets dryRun value.
name
Required, Sets name value.
Shorthand Example:
--custom-metrics=dryRun=boolean,name=string --custom-metrics=dryRun=boolean,name=string
JSON Example:
--custom-metrics='[{"dryRun": boolean, "name": "string"}]'
File Example:
--custom-metrics=path_to_file.(yaml|json)
--custom-metrics-file=[CUSTOM_METRICS,...]
File path to json file with custom metrics that are used for
WEIGHTED_ROUND_ROBIN locality load balancing policy.
Example:
$ gcloud compute backend-services update \
--custom-metrics-file='customMetric.json'
Sets custom_metrics_file value.
dryRun
Sets dryRun value.
name
Required, Sets name value.
Shorthand Example:
--custom-metrics-file=dryRun=boolean,name=string --custom-metrics-file=dryRun=boolean,name=string
JSON Example:
--custom-metrics-file='[{"dryRun": boolean, "name": "string"}]'
File Example:
--custom-metrics-file=path_to_file.(yaml|json)
At most one of these can be specified:
--client-ttl=CLIENT_TTL

View file

@ -12,6 +12,8 @@ SYNOPSIS
[--balancing-mode=BALANCING_MODE] [--capacity-scaler=CAPACITY_SCALER]
[--description=DESCRIPTION] [--failover]
[--max-utilization=MAX_UTILIZATION] [--preference=PREFERENCE]
[--clear-custom-metrics | --custom-metrics=[CUSTOM_METRICS,...]
| --custom-metrics-file=[CUSTOM_METRICS,...]]
[--global | --region=REGION]
[--max-connections=MAX_CONNECTIONS
| --max-connections-per-endpoint=MAX_CONNECTIONS_PER_ENDPOINT
@ -216,6 +218,83 @@ OPTIONAL FLAGS
Backends with this preference setting are used up to their capacity
limits first, while optimizing overall network latency.
At most one of these can be specified:
--clear-custom-metrics
Clears current list of CUSTOM_METRICS.
--custom-metrics=[CUSTOM_METRICS,...]
List of custom metrics that are used for CUSTOM_METRICS balancing
mode and WEIGHTED_ROUND_ROBIN locality load balancing policy.
Example:
$ gcloud compute backend-services update-backend \
--custom-metrics='name=my-signal,maxUtilization=0.8,dryRun=true'
$ gcloud compute backend-services update-backend \
--custom-metrics='name=my-signal,maxUtilization=0.8,dryRun=true'\
--custom-metrics='name=my-signal2,maxUtilization=0.2'
$ gcloud compute backend-services update-backend \
--custom-metrics='[{"name" : "my-signal", "maxUtilization" :
0.8, "dryRun" : true}, {"name" : "my-signal2", "maxUtilization" :
0.1}]'
Sets custom_metrics value.
dryRun
Sets dryRun value.
maxUtilization
Sets maxUtilization value.
name
Required, Sets name value.
Shorthand Example:
--custom-metrics=dryRun=boolean,maxUtilization=float,name=string --custom-metrics=dryRun=boolean,maxUtilization=float,name=string
JSON Example:
--custom-metrics='[{"dryRun": boolean, "maxUtilization": float, "name": "string"}]'
File Example:
--custom-metrics=path_to_file.(yaml|json)
--custom-metrics-file=[CUSTOM_METRICS,...]
File path to json file with custom metrics that are used for
CUSTOM_METRICS balancing mode and WEIGHTED_ROUND_ROBIN locality load
balancing policy.
Example:
$ gcloud compute backend-services update-backend \
--custom-metrics-file='customMetric.json'
Sets custom_metrics_file value.
dryRun
Sets dryRun value.
maxUtilization
Sets maxUtilization value.
name
Required, Sets name value.
Shorthand Example:
--custom-metrics-file=dryRun=boolean,maxUtilization=float,name=string --custom-metrics-file=dryRun=boolean,maxUtilization=float,name=string
JSON Example:
--custom-metrics-file='[{"dryRun": boolean, "maxUtilization": float, "name": "string"}]'
File Example:
--custom-metrics-file=path_to_file.(yaml|json)
At most one of these can be specified:
--global

View file

@ -41,6 +41,13 @@ GCLOUD WIDE FLAGS
Run $ gcloud help for details.
IAM PERMISSIONS
To clone rules to a firewall policy, the user must have the following
permission: compute.firewallPolicies.cloneRules.
To find predefined roles that contain those permissions, see the Compute
Engine IAM roles (https://cloud.google.com/compute/docs/access/iam).
NOTES
These variants are also available:

View file

@ -45,6 +45,13 @@ GCLOUD WIDE FLAGS
Run $ gcloud help for details.
IAM PERMISSIONS
To create rules to a firewall policy, the user must have the following
permission: compute.firewallPolicies.create.
To find predefined roles that contain those permissions, see the Compute
Engine IAM roles (https://cloud.google.com/compute/docs/access/iam).
NOTES
These variants are also available:

View file

@ -33,6 +33,13 @@ GCLOUD WIDE FLAGS
Run $ gcloud help for details.
IAM PERMISSIONS
To delete a firewall policy, the user must have the following permission:
compute.firewallPolicies.delete.
To find predefined roles that contain those permissions, see the Compute
Engine IAM roles (https://cloud.google.com/compute/docs/access/iam).
NOTES
These variants are also available:

View file

@ -33,6 +33,13 @@ GCLOUD WIDE FLAGS
Run $ gcloud help for details.
IAM PERMISSIONS
To describe a firewall policy, the user must have the following permission:
compute.firewallPolicies.get.
To find predefined roles that contain those permissions, see the Compute
Engine IAM roles (https://cloud.google.com/compute/docs/access/iam).
NOTES
These variants are also available:

View file

@ -85,6 +85,13 @@ GCLOUD WIDE FLAGS
Run $ gcloud help for details.
IAM PERMISSIONS
To list firewall policies, the user must have the following permission:
compute.firewallPolicies.list.
To find predefined roles that contain those permissions, see the Compute
Engine IAM roles (https://cloud.google.com/compute/docs/access/iam).
NOTES
These variants are also available:

View file

@ -98,6 +98,13 @@ GCLOUD WIDE FLAGS
Run $ gcloud help for details.
IAM PERMISSIONS
To list rules of a firewall policy, the user must have the following
permission: compute.firewallPolicies.get.
To find predefined roles that contain those permissions, see the Compute
Engine IAM roles (https://cloud.google.com/compute/docs/access/iam).
NOTES
These variants are also available:

View file

@ -36,6 +36,13 @@ GCLOUD WIDE FLAGS
Run $ gcloud help for details.
IAM PERMISSIONS
To move a firewall policy, the user must have the following permission:
compute.firewallPolicies.move.
To find predefined roles that contain those permissions, see the Compute
Engine IAM roles (https://cloud.google.com/compute/docs/access/iam).
NOTES
These variants are also available:

View file

@ -39,6 +39,13 @@ GCLOUD WIDE FLAGS
Run $ gcloud help for details.
IAM PERMISSIONS
To update a firewall policy, the user must have the following permission:
compute.firewallPolicies.update.
To find predefined roles that contain those permissions, see the Compute
Engine IAM roles (https://cloud.google.com/compute/docs/access/iam).
NOTES
These variants are also available:

View file

@ -53,9 +53,10 @@ FLAGS
List images from public image projects. The public image projects that
are available include the following: cos-cloud, debian-cloud,
rocky-linux-cloud, ubuntu-os-cloud, centos-cloud, fedora-coreos-cloud,
opensuse-cloud, rhel-cloud, rhel-sap-cloud, suse-cloud, suse-sap-cloud,
ubuntu-os-pro-cloud, windows-cloud, windows-sql-cloud. Enabled by
default, use --no-standard-images to disable.
opensuse-cloud, oracle-linux-cloud, rhel-cloud, rhel-sap-cloud,
suse-cloud, suse-sap-cloud, ubuntu-os-pro-cloud, windows-cloud,
windows-sql-cloud. Enabled by default, use --no-standard-images to
disable.
LIST COMMAND FLAGS
--filter=EXPRESSION

View file

@ -58,6 +58,8 @@ REQUIRED FLAGS
100Gbps Ethernet, LR Optics.
LINK_TYPE_ETHERNET_10G_LR
10Gbps Ethernet, LR Optics.
LINK_TYPE_ETHERNET_400G_LR4
400Gbps Ethernet, LR4 Optics.
--location=LOCATION
The location for the interconnect. The locations can be listed by using