mirror of
https://github.com/imjasonh/gcloud-help
synced 2026-07-16 12:22:03 +00:00
gcloud: Wed Jan 29 10:02:21 UTC 2025
This commit is contained in:
parent
861d4011dc
commit
50090ced80
157 changed files with 5563 additions and 179 deletions
|
|
@ -567,7 +567,8 @@ FLAGS
|
|||
|
||||
stack-type
|
||||
Specifies whether IPv6 is enabled on the interface. STACK_TYPE must
|
||||
be one of: IPV4_ONLY, IPV4_IPV6. The default value is IPV4_ONLY.
|
||||
be one of: IPV4_ONLY, IPV4_IPV6, IPV6_ONLY. The default value is
|
||||
IPV4_ONLY.
|
||||
|
||||
ipv6-network-tier
|
||||
Specifies the IPv6 network tier that will be used to configure the
|
||||
|
|
@ -709,6 +710,8 @@ FLAGS
|
|||
The network interface can have both IPv4 and IPv6 addresses
|
||||
IPV4_ONLY
|
||||
The network interface will be assigned IPv4 addresses
|
||||
IPV6_ONLY
|
||||
The network interface will be assigned IPv6 addresses
|
||||
|
||||
--subnet=SUBNET
|
||||
Specifies the subnet that the VM instances are a part of. If --network
|
||||
|
|
|
|||
|
|
@ -660,7 +660,8 @@ FLAGS
|
|||
|
||||
stack-type
|
||||
Specifies whether IPv6 is enabled on the interface. STACK_TYPE must
|
||||
be one of: IPV4_ONLY, IPV4_IPV6. The default value is IPV4_ONLY.
|
||||
be one of: IPV4_ONLY, IPV4_IPV6, IPV6_ONLY. The default value is
|
||||
IPV4_ONLY.
|
||||
|
||||
ipv6-network-tier
|
||||
Specifies the IPv6 network tier that will be used to configure the
|
||||
|
|
@ -813,6 +814,8 @@ FLAGS
|
|||
The network interface can have both IPv4 and IPv6 addresses
|
||||
IPV4_ONLY
|
||||
The network interface will be assigned IPv4 addresses
|
||||
IPV6_ONLY
|
||||
The network interface will be assigned IPv6 addresses
|
||||
|
||||
--subnet=SUBNET
|
||||
Specifies the subnet that the VM instances are a part of. If --network
|
||||
|
|
|
|||
|
|
@ -19,8 +19,9 @@ 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],[tls-ja3-fingerprint],[user-ip]],[...]]
|
||||
[http-cookie=HTTP_COOKIE],[http-header=HTTP_HEADER],[http-path],[sni],
|
||||
[region-code],
|
||||
[tls-ja3-fingerprint],[user-ip],[tls-ja4-fingerprint]],[...]]
|
||||
[--enforce-on-key-name=ENFORCE_ON_KEY_NAME]
|
||||
[--exceed-action=EXCEED_ACTION]
|
||||
[--exceed-redirect-target=EXCEED_REDIRECT_TARGET]
|
||||
|
|
@ -182,11 +183,14 @@ OPTIONAL FLAGS
|
|||
◆ 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
|
||||
◆ tls-ja4-fingerprint: key type takes the value of JA4 TLS/SSL
|
||||
fingerprint if the client connects using HTTPS, HTTP/2 or HTTP/3
|
||||
|
||||
ENFORCE_ON_KEY must be one of: ip, all, http-header, xff-ip,
|
||||
http-cookie, http-path, sni, region-code, tls-ja3-fingerprint, user-ip.
|
||||
http-cookie, http-path, sni, region-code, tls-ja3-fingerprint, user-ip,
|
||||
tls-ja4-fingerprint.
|
||||
|
||||
--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]],[...]
|
||||
--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],[tls-ja4-fingerprint]],[...]
|
||||
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
|
||||
|
|
@ -207,6 +211,8 @@ OPTIONAL FLAGS
|
|||
◆ 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
|
||||
◆ tls-ja4-fingerprint: key type takes the value of JA4 TLS/SSL
|
||||
fingerprint if the client connects using HTTPS, HTTP/2 or HTTP/3
|
||||
|
||||
Key names are only applicable to the following key types:
|
||||
◆ http-header: The name of the HTTP header whose value is taken as
|
||||
|
|
|
|||
|
|
@ -10,8 +10,9 @@ 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],[tls-ja3-fingerprint],[user-ip]],[...]]
|
||||
[http-cookie=HTTP_COOKIE],[http-header=HTTP_HEADER],[http-path],[sni],
|
||||
[region-code],
|
||||
[tls-ja3-fingerprint],[user-ip],[tls-ja4-fingerprint]],[...]]
|
||||
[--enforce-on-key-name=ENFORCE_ON_KEY_NAME]
|
||||
[--exceed-action=EXCEED_ACTION]
|
||||
[--exceed-redirect-target=EXCEED_REDIRECT_TARGET]
|
||||
|
|
@ -133,11 +134,14 @@ FLAGS
|
|||
◆ 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
|
||||
◆ tls-ja4-fingerprint: key type takes the value of JA4 TLS/SSL
|
||||
fingerprint if the client connects using HTTPS, HTTP/2 or HTTP/3
|
||||
|
||||
ENFORCE_ON_KEY must be one of: ip, all, http-header, xff-ip,
|
||||
http-cookie, http-path, sni, region-code, tls-ja3-fingerprint, user-ip.
|
||||
http-cookie, http-path, sni, region-code, tls-ja3-fingerprint, user-ip,
|
||||
tls-ja4-fingerprint.
|
||||
|
||||
--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]],[...]
|
||||
--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],[tls-ja4-fingerprint]],[...]
|
||||
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
|
||||
|
|
@ -158,6 +162,8 @@ FLAGS
|
|||
◆ 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
|
||||
◆ tls-ja4-fingerprint: key type takes the value of JA4 TLS/SSL
|
||||
fingerprint if the client connects using HTTPS, HTTP/2 or HTTP/3
|
||||
|
||||
Key names are only applicable to the following key types:
|
||||
◆ http-header: The name of the HTTP header whose value is taken as
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue