imjasonh/gcloud-help
1
0
Fork 0
mirror of https://github.com/imjasonh/gcloud-help synced 2026-07-18 14:56:05 +00:00
Code Activity

gcloud: Wed Jan 29 10:02:21 UTC 2025

Browse source
This commit is contained in:
Automated 2025-01-29 10:02:21 +00:00
parent 861d4011dc
commit 50090ced80
157 changed files with 5563 additions and 179 deletions
Download patch file Download diff file Expand all files Collapse all files

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

@ -20,8 +20,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-action-rpc-status-code=EXCEED_ACTION_RPC_STATUS_CODE]
@ -189,11 +190,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
@ -214,6 +218,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

14
gcloud/alpha/compute/security-policies/rules/update
View file

@ -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-action-rpc-status-code=EXCEED_ACTION_RPC_STATUS_CODE]
@ -139,11 +140,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
@ -164,6 +168,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