imjasonh/gcloud-help
1
0
Fork 0
mirror of https://github.com/imjasonh/gcloud-help synced 2026-07-20 04:58:26 +00:00
Code Activity

gcloud: Wed Jul 31 09:35:15 UTC 2024

Browse source
This commit is contained in:
Automated 2024-07-31 09:35:16 +00:00
parent 3a4c5997b9
commit ed2f818f7a
2722 changed files with 12631 additions and 6826 deletions
Download patch file Download diff file Expand all files Collapse all files

38
gcloud/alpha/compute/backend-services/update
View file

@ -3,6 +3,7 @@ NAME
SYNOPSIS
gcloud alpha compute backend-services update BACKEND_SERVICE_NAME
[--affinity-cookie-name=AFFINITY_COOKIE_NAME]
[--affinity-cookie-ttl=AFFINITY_COOKIE_TTL] [--cache-key-include-host]
[--cache-key-include-http-header=[HEADER_FIELD_NAME,...]]
[--cache-key-include-named-cookie=[NAMED_COOKIE,...]]
@ -65,11 +66,15 @@ POSITIONAL ARGUMENTS
Name of the backend service to update.
FLAGS
--affinity-cookie-name=AFFINITY_COOKIE_NAME
If --session-affinity is set to HTTP_COOKIE, this flag sets the name of
the cookie.
--affinity-cookie-ttl=AFFINITY_COOKIE_TTL
If session-affinity is set to "generated_cookie", this flag sets the
TTL, in seconds, of the resulting cookie. A setting of 0 indicates that
the cookie should be transient. See $ gcloud topic datetimes for
information on duration formats.
If --session-affinity is set to GENERATED_COOKIE or HTTP_COOKIE, this
flag sets the TTL, in seconds, of the resulting cookie. A setting of 0
indicates that the cookie should be a session cookie. See $ gcloud
topic datetimes for information on duration formats.
--cache-key-include-host
Enable including host in cache key. If enabled, requests to different
@ -304,7 +309,7 @@ FLAGS
The load balancing algorithm used within the scope of the locality.
LOCALITY_LB_POLICY must be one of: INVALID_LB_POLICY, ROUND_ROBIN,
LEAST_REQUEST, RING_HASH, RANDOM, ORIGINAL_DESTINATION, MAGLEV,
WEIGHTED_MAGLEV.
WEIGHTED_MAGLEV, WEIGHTED_ROUND_ROBIN.
--logging-optional=LOGGING_OPTIONAL
This field can only be specified if logging is enabled for the backend
@ -454,15 +459,24 @@ FLAGS
HTTP_COOKIE
(Applicable if --load-balancing-scheme is INTERNAL_MANAGED,
EXTERNAL_MANAGED or INTERNAL_SELF_MANAGED) Route requests to
backend VMs or endpoints in a NEG, based on an HTTP cookie named in
the HTTP_COOKIE flag (with the optional --affinity-cookie-ttl
flag). If the client has not provided the cookie, the proxy
generates the cookie and returns it to the client in a Set-Cookie
header. This session affinity is only valid if the load balancing
locality policy is either RING_HASH or MAGLEV and the backend
service's consistent hash specifies the HTTP cookie.
backend VMs or endpoints in a NEG, based on an HTTP cookie in the
--affinity-cookie-name flag (with the optional
--affinity-cookie-ttl flag). If the client has not provided the
cookie, the proxy generates the cookie and returns it to the client
in a Set-Cookie header. This session affinity is only valid if the
load balancing locality policy is either RING_HASH or MAGLEV and
the backend service's consistent hash specifies the HTTP cookie.
NONE
Session affinity is disabled.
STRONG_COOKIE_AFFINITY
(Applicable if --load-balancing-scheme is INTERNAL_MANAGED or
EXTERNAL_MANAGED) Strong cookie-based affinity, based on an HTTP
cookie named in the --affinity-cookie-name flag (with the optional
--affinity-cookie-ttl flag). Connections bearing the same cookie
will be served by the same backend VM while that VM remains
healthy, as long as the cookie has not expired. If the
--affinity-cookie-ttl flag is set to 0, the cookie will be treated
as a session cookie.
--signed-url-cache-max-age=SIGNED_URL_CACHE_MAX_AGE
The amount of time up to which the response to a signed URL request