imjasonh/gcloud-help
1
0
Fork 0
mirror of https://github.com/imjasonh/gcloud-help synced 2026-07-22 07:40:10 +00:00
Code Activity

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

Browse source
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
Download patch file Download diff file Expand all files Collapse all files

18
gcloud/alpha/compute/security-policies/rules/create
View file

@ -20,8 +20,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-action-rpc-status-code=EXCEED_ACTION_RPC_STATUS_CODE]
@ -184,11 +184,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
@ -204,6 +209,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

18
gcloud/alpha/compute/security-policies/rules/update
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-action-rpc-status-code=EXCEED_ACTION_RPC_STATUS_CODE]
@ -134,11 +134,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
@ -154,6 +159,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