1
0
Fork 0
mirror of https://github.com/imjasonh/gcloud-help synced 2026-07-18 23:08:48 +00:00

gcloud: Thu Dec 14 10:23:57 UTC 2023

This commit is contained in:
Automated 2023-12-14 10:23:58 +00:00
parent f36750d203
commit a990278fb3
205 changed files with 4929 additions and 1866 deletions

View file

@ -114,12 +114,14 @@ REQUIRED FLAGS
Target gRPC proxy that receives the traffic.
--target-http-proxy=TARGET_HTTP_PROXY
Target HTTP proxy that receives the traffic. Acceptable values for
--ports flag are: 80, 8080.
Target HTTP proxy that receives the traffic. For the acceptable
ports, see Port specifications
(https://cloud.google.com/load-balancing/docs/forwarding-rule-concepts#port_specifications).
--target-https-proxy=TARGET_HTTPS_PROXY
Target HTTPS proxy that receives the traffic. Acceptable values for
--ports flag are: 443.
Target HTTPS proxy that receives the traffic. For the acceptable
ports, see Port specifications
(https://cloud.google.com/load-balancing/docs/forwarding-rule-concepts#port_specifications).
--target-instance=TARGET_INSTANCE
Name of the target instance that receives the traffic. The target

View file

@ -79,12 +79,14 @@ REQUIRED FLAGS
Target gRPC proxy that receives the traffic.
--target-http-proxy=TARGET_HTTP_PROXY
Target HTTP proxy that receives the traffic. Acceptable values for
--ports flag are: 80, 8080.
Target HTTP proxy that receives the traffic. For the acceptable
ports, see Port specifications
(https://cloud.google.com/load-balancing/docs/forwarding-rule-concepts#port_specifications).
--target-https-proxy=TARGET_HTTPS_PROXY
Target HTTPS proxy that receives the traffic. Acceptable values for
--ports flag are: 443.
Target HTTPS proxy that receives the traffic. For the acceptable
ports, see Port specifications
(https://cloud.google.com/load-balancing/docs/forwarding-rule-concepts#port_specifications).
--target-instance=TARGET_INSTANCE
Name of the target instance that receives the traffic. The target

View file

@ -840,7 +840,7 @@ FLAGS
--source-instance-template=SOURCE_INSTANCE_TEMPLATE
The name of the instance template that the instance will be created
from.
from. An instance template can be a global/regional resource.
Users can also override machine type and labels. Values of other flags
will be ignored and --source-instance-template will be used instead.

View file

@ -695,7 +695,7 @@ FLAGS
--source-instance-template=SOURCE_INSTANCE_TEMPLATE
The name of the instance template that the instance will be created
from.
from. An instance template can be a global/regional resource.
Users can also override machine type and labels. Values of other flags
will be ignored and --source-instance-template will be used instead.

View file

@ -247,6 +247,7 @@ REQUIRED FLAGS
ubuntu 21.10
ubuntu 22.04
ubuntu 23.04
ubuntu 23.10
windows 10.*
windows 6.*

View file

@ -284,6 +284,7 @@ FLAGS
ubuntu 21.10
ubuntu 22.04
ubuntu 23.04
ubuntu 23.10
windows 10.*
windows 6.*

View file

@ -60,8 +60,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 compute instances set-name
$ gcloud alpha compute instances set-name

View file

@ -20,11 +20,11 @@ POSITIONAL ARGUMENTS
REQUIRED FLAGS
--dns-verification-ip=DNS_VERIFICATION_IP
IPv4 address to use for verification. It must be within the IPv4 range
IP address to use for verification. It must be within the IP range
specified in --range.
--range=RANGE
IPv4 range allocated to this public advertised prefix, in CIDR format.
IP range allocated to this public advertised prefix, in CIDR format.
OPTIONAL FLAGS
--description=DESCRIPTION

View file

@ -22,8 +22,8 @@ POSITIONAL ARGUMENTS
REQUIRED FLAGS
--range=RANGE
IPv4 range from this public delegated prefix that should be delegated,
in CIDR format. It must be smaller than parent public advertised prefix
IP range from this public delegated prefix that should be delegated, in
CIDR format. It must be smaller than parent public advertised prefix
range.
Exactly one of these must be specified:

View file

@ -19,8 +19,8 @@ SYNOPSIS
[--conform-action=CONFORM_ACTION] [--description=DESCRIPTION]
[--enforce-on-key=ENFORCE_ON_KEY]
[--enforce-on-key-configs=[[all],[ip],[xff-ip],
[http-cookie=HTTP_COOKIE],
[http-header=HTTP_HEADER],[http-path],[sni],[region-code]],[...]]
[http-cookie=HTTP_COOKIE],[http-header=HTTP_HEADER],[http-path],
[sni],[region-code],[tls-ja3-fingerprint],[user-ip]],[...]]
[--enforce-on-key-name=ENFORCE_ON_KEY_NAME]
[--exceed-action=EXCEED_ACTION]
[--exceed-redirect-target=EXCEED_REDIRECT_TARGET]
@ -177,11 +177,16 @@ OPTIONAL FLAGS
the TLS session of the HTTPS request
◆ region-code: key type takes the value of the region code from which
the request originates
◆ tls-ja3-fingerprint: key type takes the value of JA3 TLS/SSL
fingerprint if the client connects using HTTPS, HTTP/2 or HTTP/3
◆ user-ip: key type takes the IP address of the originating client,
which is resolved based on user-ip-request-headers configured with
the security policy
ENFORCE_ON_KEY must be one of: ip, all, http-header, xff-ip,
http-cookie, http-path, sni, region-code.
http-cookie, http-path, sni, region-code, tls-ja3-fingerprint, user-ip.
--enforce-on-key-configs=[[all],[ip],[xff-ip],[http-cookie=HTTP_COOKIE],[http-header=HTTP_HEADER],[http-path],[sni],[region-code]],[...]
--enforce-on-key-configs=[[all],[ip],[xff-ip],[http-cookie=HTTP_COOKIE],[http-header=HTTP_HEADER],[http-path],[sni],[region-code],[tls-ja3-fingerprint],[user-ip]],[...]
Specify up to 3 key type/name pairs to rate limit. Valid key types are:
◆ ip: each client IP address has this limit enforced separately
@ -197,6 +202,11 @@ OPTIONAL FLAGS
the TLS session of the HTTPS request
◆ region-code: key type takes the value of the region code from which
the request originates
◆ tls-ja3-fingerprint: key type takes the value of JA3 TLS/SSL
fingerprint if the client connects using HTTPS, HTTP/2 or HTTP/3
◆ user-ip: key type takes the IP address of the originating client,
which is resolved based on user-ip-request-headers configured with
the security policy
Key names are only applicable to the following key types:
◆ http-header: The name of the HTTP header whose value is taken as

View file

@ -10,8 +10,8 @@ SYNOPSIS
[--conform-action=CONFORM_ACTION] [--description=DESCRIPTION]
[--enforce-on-key=ENFORCE_ON_KEY]
[--enforce-on-key-configs=[[all],[ip],[xff-ip],
[http-cookie=HTTP_COOKIE],
[http-header=HTTP_HEADER],[http-path],[sni],[region-code]],[...]]
[http-cookie=HTTP_COOKIE],[http-header=HTTP_HEADER],[http-path],
[sni],[region-code],[tls-ja3-fingerprint],[user-ip]],[...]]
[--enforce-on-key-name=ENFORCE_ON_KEY_NAME]
[--exceed-action=EXCEED_ACTION]
[--exceed-redirect-target=EXCEED_REDIRECT_TARGET]
@ -128,11 +128,16 @@ FLAGS
the TLS session of the HTTPS request
◆ region-code: key type takes the value of the region code from which
the request originates
◆ tls-ja3-fingerprint: key type takes the value of JA3 TLS/SSL
fingerprint if the client connects using HTTPS, HTTP/2 or HTTP/3
◆ user-ip: key type takes the IP address of the originating client,
which is resolved based on user-ip-request-headers configured with
the security policy
ENFORCE_ON_KEY must be one of: ip, all, http-header, xff-ip,
http-cookie, http-path, sni, region-code.
http-cookie, http-path, sni, region-code, tls-ja3-fingerprint, user-ip.
--enforce-on-key-configs=[[all],[ip],[xff-ip],[http-cookie=HTTP_COOKIE],[http-header=HTTP_HEADER],[http-path],[sni],[region-code]],[...]
--enforce-on-key-configs=[[all],[ip],[xff-ip],[http-cookie=HTTP_COOKIE],[http-header=HTTP_HEADER],[http-path],[sni],[region-code],[tls-ja3-fingerprint],[user-ip]],[...]
Specify up to 3 key type/name pairs to rate limit. Valid key types are:
◆ ip: each client IP address has this limit enforced separately
@ -148,6 +153,11 @@ FLAGS
the TLS session of the HTTPS request
◆ region-code: key type takes the value of the region code from which
the request originates
◆ tls-ja3-fingerprint: key type takes the value of JA3 TLS/SSL
fingerprint if the client connects using HTTPS, HTTP/2 or HTTP/3
◆ user-ip: key type takes the IP address of the originating client,
which is resolved based on user-ip-request-headers configured with
the security policy
Key names are only applicable to the following key types:
◆ http-header: The name of the HTTP header whose value is taken as