ansible-collections/google.cloud
1
0
Fork 0
mirror of https://github.com/ansible-collections/google.cloud.git synced 2025-04-09 20:30:27 -07:00
Code Issues Projects Releases Packages Wiki Activity Actions 1

fix doc formatting errors (#4118) (#310)

Browse source 
Co-authored-by: Riley Karson <rileykarson@google.com>
Signed-off-by: Modular Magician <magic-modules@google.com>

Co-authored-by: Riley Karson <rileykarson@google.com>
This commit is contained in:
The Magician 2020-10-16 13:41:31 -07:00 • committed by GitHub
parent 3228844456
commit 3af242d21d
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
16 changed files with 285 additions and 282 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
plugins/modules/gcp_compute_address.py
View file

@ -86,7 +86,7 @@ options:
type: str type: str
purpose: purpose:
description: description:
- 'The purpose of this resource, which can be one of the following values: - GCE_ENDPOINT - 'The purpose of this resource, which can be one of the following values: * GCE_ENDPOINT
for addresses that are used by VM instances, alias IP ranges, internal load for addresses that are used by VM instances, alias IP ranges, internal load
balancers, and similar resources.' balancers, and similar resources.'
- This should only be set when using an Internal address. - This should only be set when using an Internal address.
@ -223,7 +223,7 @@ name:
type: str type: str
purpose: purpose:
description: description:
- 'The purpose of this resource, which can be one of the following values: - GCE_ENDPOINT - 'The purpose of this resource, which can be one of the following values: * GCE_ENDPOINT
for addresses that are used by VM instances, alias IP ranges, internal load balancers, for addresses that are used by VM instances, alias IP ranges, internal load balancers,
and similar resources.' and similar resources.'
- This should only be set when using an Internal address. - This should only be set when using an Internal address.

2
plugins/modules/gcp_compute_address_info.py
View file

@ -158,7 +158,7 @@ resources:
type: str type: str
purpose: purpose:
description: description:
- 'The purpose of this resource, which can be one of the following values: - - 'The purpose of this resource, which can be one of the following values: *
GCE_ENDPOINT for addresses that are used by VM instances, alias IP ranges, GCE_ENDPOINT for addresses that are used by VM instances, alias IP ranges,
internal load balancers, and similar resources.' internal load balancers, and similar resources.'
- This should only be set when using an Internal address. - This should only be set when using an Internal address.

38
plugins/modules/gcp_compute_backend_service.py
View file

@ -406,19 +406,19 @@ options:
locality_lb_policy: locality_lb_policy:
description: description:
- The load balancing algorithm used within the scope of the locality. - The load balancing algorithm used within the scope of the locality.
- The possible values are - ROUND_ROBIN - This is a simple policy in which each - The possible values are - * ROUND_ROBIN - This is a simple policy in which each
healthy backend is selected in round robin order. healthy backend is selected in round robin order.
- LEAST_REQUEST - An O(1) algorithm which selects two random healthy hosts and - "* LEAST_REQUEST - An O(1) algorithm which selects two random healthy hosts
picks the host which has fewer active requests. and picks the host which has fewer active requests."
- RING_HASH - The ring/modulo hash load balancer implements consistent hashing - "* RING_HASH - The ring/modulo hash load balancer implements consistent hashing
to backends. The algorithm has the property that the addition/removal of a host to backends. The algorithm has the property that the addition/removal of a host
from a set of N hosts only affects 1/N of the requests. from a set of N hosts only affects 1/N of the requests."
- RANDOM - The load balancer selects a random healthy host. - "* RANDOM - The load balancer selects a random healthy host."
- ORIGINAL_DESTINATION - Backend host is selected based on the client connection - "* ORIGINAL_DESTINATION - Backend host is selected based on the client connection
metadata, i.e., connections are opened to the same address as the destination metadata, i.e., connections are opened to the same address as the destination
address of the incoming connection before the connection was redirected to the address of the incoming connection before the connection was redirected to the
load balancer. load balancer."
- MAGLEV - used as a drop in replacement for the ring hash load balancer. - "* MAGLEV - used as a drop in replacement for the ring hash load balancer."
- Maglev is not as stable as ring hash but has faster table lookup build times - Maglev is not as stable as ring hash but has faster table lookup build times
and host selection times. For more information about Maglev, refer to https://ai.google/research/pubs/pub44824 and host selection times. For more information about Maglev, refer to https://ai.google/research/pubs/pub44824
This field is applicable only when the load_balancing_scheme is set to INTERNAL_SELF_MANAGED. This field is applicable only when the load_balancing_scheme is set to INTERNAL_SELF_MANAGED.
@ -1067,19 +1067,19 @@ loadBalancingScheme:
localityLbPolicy: localityLbPolicy:
description: description:
- The load balancing algorithm used within the scope of the locality. - The load balancing algorithm used within the scope of the locality.
- The possible values are - ROUND_ROBIN - This is a simple policy in which each - The possible values are - * ROUND_ROBIN - This is a simple policy in which each
healthy backend is selected in round robin order. healthy backend is selected in round robin order.
- LEAST_REQUEST - An O(1) algorithm which selects two random healthy hosts and picks - "* LEAST_REQUEST - An O(1) algorithm which selects two random healthy hosts and
the host which has fewer active requests. picks the host which has fewer active requests."
- RING_HASH - The ring/modulo hash load balancer implements consistent hashing to - "* RING_HASH - The ring/modulo hash load balancer implements consistent hashing
backends. The algorithm has the property that the addition/removal of a host from to backends. The algorithm has the property that the addition/removal of a host
a set of N hosts only affects 1/N of the requests. from a set of N hosts only affects 1/N of the requests."
- RANDOM - The load balancer selects a random healthy host. - "* RANDOM - The load balancer selects a random healthy host."
- ORIGINAL_DESTINATION - Backend host is selected based on the client connection - "* ORIGINAL_DESTINATION - Backend host is selected based on the client connection
metadata, i.e., connections are opened to the same address as the destination metadata, i.e., connections are opened to the same address as the destination
address of the incoming connection before the connection was redirected to the address of the incoming connection before the connection was redirected to the
load balancer. load balancer."
- MAGLEV - used as a drop in replacement for the ring hash load balancer. - "* MAGLEV - used as a drop in replacement for the ring hash load balancer."
- Maglev is not as stable as ring hash but has faster table lookup build times and - Maglev is not as stable as ring hash but has faster table lookup build times and
host selection times. For more information about Maglev, refer to https://ai.google/research/pubs/pub44824 host selection times. For more information about Maglev, refer to https://ai.google/research/pubs/pub44824
This field is applicable only when the load_balancing_scheme is set to INTERNAL_SELF_MANAGED. This field is applicable only when the load_balancing_scheme is set to INTERNAL_SELF_MANAGED.

20
plugins/modules/gcp_compute_backend_service_info.py
View file

@ -475,19 +475,19 @@ resources:
localityLbPolicy: localityLbPolicy:
description: description:
- The load balancing algorithm used within the scope of the locality. - The load balancing algorithm used within the scope of the locality.
- The possible values are - ROUND_ROBIN - This is a simple policy in which each - The possible values are - * ROUND_ROBIN - This is a simple policy in which
healthy backend is selected in round robin order. each healthy backend is selected in round robin order.
- LEAST_REQUEST - An O(1) algorithm which selects two random healthy hosts and - "* LEAST_REQUEST - An O(1) algorithm which selects two random healthy hosts
picks the host which has fewer active requests. and picks the host which has fewer active requests."
- RING_HASH - The ring/modulo hash load balancer implements consistent hashing - "* RING_HASH - The ring/modulo hash load balancer implements consistent hashing
to backends. The algorithm has the property that the addition/removal of a to backends. The algorithm has the property that the addition/removal of a
host from a set of N hosts only affects 1/N of the requests. host from a set of N hosts only affects 1/N of the requests."
- RANDOM - The load balancer selects a random healthy host. - "* RANDOM - The load balancer selects a random healthy host."
- ORIGINAL_DESTINATION - Backend host is selected based on the client connection - "* ORIGINAL_DESTINATION - Backend host is selected based on the client connection
metadata, i.e., connections are opened to the same address as the destination metadata, i.e., connections are opened to the same address as the destination
address of the incoming connection before the connection was redirected to address of the incoming connection before the connection was redirected to
the load balancer. the load balancer."
- MAGLEV - used as a drop in replacement for the ring hash load balancer. - "* MAGLEV - used as a drop in replacement for the ring hash load balancer."
- Maglev is not as stable as ring hash but has faster table lookup build times - Maglev is not as stable as ring hash but has faster table lookup build times
and host selection times. For more information about Maglev, refer to https://ai.google/research/pubs/pub44824 and host selection times. For more information about Maglev, refer to https://ai.google/research/pubs/pub44824
This field is applicable only when the load_balancing_scheme is set to INTERNAL_SELF_MANAGED. This field is applicable only when the load_balancing_scheme is set to INTERNAL_SELF_MANAGED.

16
plugins/modules/gcp_compute_image.py
View file

@ -187,8 +187,8 @@ options:
source_image: source_image:
description: description:
- 'URL of the source image used to create this image. In order to create an image, - 'URL of the source image used to create this image. In order to create an image,
you must provide the full or partial URL of one of the following: The selfLink you must provide the full or partial URL of one of the following: * The selfLink
URL This property The rawDisk.source URL The sourceDisk URL .' URL * This property * The rawDisk.source URL * The sourceDisk URL .'
- 'This field represents a link to a Image resource in GCP. It can be specified - 'This field represents a link to a Image resource in GCP. It can be specified
in two ways. First, you can place a dictionary with key ''selfLink'' and value in two ways. First, you can place a dictionary with key ''selfLink'' and value
of your resource''s selfLink Alternatively, you can add `register: name-of-resource` of your resource''s selfLink Alternatively, you can add `register: name-of-resource`
@ -200,8 +200,8 @@ options:
description: description:
- URL of the source snapshot used to create this image. - URL of the source snapshot used to create this image.
- 'In order to create an image, you must provide the full or partial URL of one - 'In order to create an image, you must provide the full or partial URL of one
of the following: The selfLink URL This property The sourceImage URL The rawDisk.source of the following: * The selfLink URL * This property * The sourceImage URL *
URL The sourceDisk URL .' The rawDisk.source URL * The sourceDisk URL .'
- 'This field represents a link to a Snapshot resource in GCP. It can be specified - 'This field represents a link to a Snapshot resource in GCP. It can be specified
in two ways. First, you can place a dictionary with key ''selfLink'' and value in two ways. First, you can place a dictionary with key ''selfLink'' and value
of your resource''s selfLink Alternatively, you can add `register: name-of-resource` of your resource''s selfLink Alternatively, you can add `register: name-of-resource`
@ -487,16 +487,16 @@ sourceDiskId:
sourceImage: sourceImage:
description: description:
- 'URL of the source image used to create this image. In order to create an image, - 'URL of the source image used to create this image. In order to create an image,
you must provide the full or partial URL of one of the following: The selfLink you must provide the full or partial URL of one of the following: * The selfLink
URL This property The rawDisk.source URL The sourceDisk URL .' URL * This property * The rawDisk.source URL * The sourceDisk URL .'
returned: success returned: success
type: dict type: dict
sourceSnapshot: sourceSnapshot:
description: description:
- URL of the source snapshot used to create this image. - URL of the source snapshot used to create this image.
- 'In order to create an image, you must provide the full or partial URL of one - 'In order to create an image, you must provide the full or partial URL of one
of the following: The selfLink URL This property The sourceImage URL The rawDisk.source of the following: * The selfLink URL * This property * The sourceImage URL * The
URL The sourceDisk URL .' rawDisk.source URL * The sourceDisk URL .'
returned: success returned: success
type: dict type: dict
sourceType: sourceType:

9
plugins/modules/gcp_compute_image_info.py
View file

@ -311,16 +311,17 @@ resources:
sourceImage: sourceImage:
description: description:
- 'URL of the source image used to create this image. In order to create an - 'URL of the source image used to create this image. In order to create an
image, you must provide the full or partial URL of one of the following: The image, you must provide the full or partial URL of one of the following: *
selfLink URL This property The rawDisk.source URL The sourceDisk URL .' The selfLink URL * This property * The rawDisk.source URL * The sourceDisk
URL .'
returned: success returned: success
type: dict type: dict
sourceSnapshot: sourceSnapshot:
description: description:
- URL of the source snapshot used to create this image. - URL of the source snapshot used to create this image.
- 'In order to create an image, you must provide the full or partial URL of - 'In order to create an image, you must provide the full or partial URL of
one of the following: The selfLink URL This property The sourceImage URL The one of the following: * The selfLink URL * This property * The sourceImage
rawDisk.source URL The sourceDisk URL .' URL * The rawDisk.source URL * The sourceDisk URL .'
returned: success returned: success
type: dict type: dict
sourceType: sourceType:

38
plugins/modules/gcp_compute_region_backend_service.py
View file

@ -356,19 +356,19 @@ options:
locality_lb_policy: locality_lb_policy:
description: description:
- The load balancing algorithm used within the scope of the locality. - The load balancing algorithm used within the scope of the locality.
- The possible values are - ROUND_ROBIN - This is a simple policy in which each - The possible values are - * ROUND_ROBIN - This is a simple policy in which each
healthy backend is selected in round robin order. healthy backend is selected in round robin order.
- LEAST_REQUEST - An O(1) algorithm which selects two random healthy hosts and - "* LEAST_REQUEST - An O(1) algorithm which selects two random healthy hosts
picks the host which has fewer active requests. and picks the host which has fewer active requests."
- RING_HASH - The ring/modulo hash load balancer implements consistent hashing - "* RING_HASH - The ring/modulo hash load balancer implements consistent hashing
to backends. The algorithm has the property that the addition/removal of a host to backends. The algorithm has the property that the addition/removal of a host
from a set of N hosts only affects 1/N of the requests. from a set of N hosts only affects 1/N of the requests."
- RANDOM - The load balancer selects a random healthy host. - "* RANDOM - The load balancer selects a random healthy host."
- ORIGINAL_DESTINATION - Backend host is selected based on the client connection - "* ORIGINAL_DESTINATION - Backend host is selected based on the client connection
metadata, i.e., connections are opened to the same address as the destination metadata, i.e., connections are opened to the same address as the destination
address of the incoming connection before the connection was redirected to the address of the incoming connection before the connection was redirected to the
load balancer. load balancer."
- MAGLEV - used as a drop in replacement for the ring hash load balancer. - "* MAGLEV - used as a drop in replacement for the ring hash load balancer."
- Maglev is not as stable as ring hash but has faster table lookup build times - Maglev is not as stable as ring hash but has faster table lookup build times
and host selection times. For more information about Maglev, refer to https://ai.google/research/pubs/pub44824 and host selection times. For more information about Maglev, refer to https://ai.google/research/pubs/pub44824
This field is applicable only when the `load_balancing_scheme` is set to INTERNAL_MANAGED This field is applicable only when the `load_balancing_scheme` is set to INTERNAL_MANAGED
@ -981,19 +981,19 @@ loadBalancingScheme:
localityLbPolicy: localityLbPolicy:
description: description:
- The load balancing algorithm used within the scope of the locality. - The load balancing algorithm used within the scope of the locality.
- The possible values are - ROUND_ROBIN - This is a simple policy in which each - The possible values are - * ROUND_ROBIN - This is a simple policy in which each
healthy backend is selected in round robin order. healthy backend is selected in round robin order.
- LEAST_REQUEST - An O(1) algorithm which selects two random healthy hosts and picks - "* LEAST_REQUEST - An O(1) algorithm which selects two random healthy hosts and
the host which has fewer active requests. picks the host which has fewer active requests."
- RING_HASH - The ring/modulo hash load balancer implements consistent hashing to - "* RING_HASH - The ring/modulo hash load balancer implements consistent hashing
backends. The algorithm has the property that the addition/removal of a host from to backends. The algorithm has the property that the addition/removal of a host
a set of N hosts only affects 1/N of the requests. from a set of N hosts only affects 1/N of the requests."
- RANDOM - The load balancer selects a random healthy host. - "* RANDOM - The load balancer selects a random healthy host."
- ORIGINAL_DESTINATION - Backend host is selected based on the client connection - "* ORIGINAL_DESTINATION - Backend host is selected based on the client connection
metadata, i.e., connections are opened to the same address as the destination metadata, i.e., connections are opened to the same address as the destination
address of the incoming connection before the connection was redirected to the address of the incoming connection before the connection was redirected to the
load balancer. load balancer."
- MAGLEV - used as a drop in replacement for the ring hash load balancer. - "* MAGLEV - used as a drop in replacement for the ring hash load balancer."
- Maglev is not as stable as ring hash but has faster table lookup build times and - Maglev is not as stable as ring hash but has faster table lookup build times and
host selection times. For more information about Maglev, refer to https://ai.google/research/pubs/pub44824 host selection times. For more information about Maglev, refer to https://ai.google/research/pubs/pub44824
This field is applicable only when the `load_balancing_scheme` is set to INTERNAL_MANAGED This field is applicable only when the `load_balancing_scheme` is set to INTERNAL_MANAGED

20
plugins/modules/gcp_compute_region_backend_service_info.py
View file

@ -436,19 +436,19 @@ resources:
localityLbPolicy: localityLbPolicy:
description: description:
- The load balancing algorithm used within the scope of the locality. - The load balancing algorithm used within the scope of the locality.
- The possible values are - ROUND_ROBIN - This is a simple policy in which each - The possible values are - * ROUND_ROBIN - This is a simple policy in which
healthy backend is selected in round robin order. each healthy backend is selected in round robin order.
- LEAST_REQUEST - An O(1) algorithm which selects two random healthy hosts and - "* LEAST_REQUEST - An O(1) algorithm which selects two random healthy hosts
picks the host which has fewer active requests. and picks the host which has fewer active requests."
- RING_HASH - The ring/modulo hash load balancer implements consistent hashing - "* RING_HASH - The ring/modulo hash load balancer implements consistent hashing
to backends. The algorithm has the property that the addition/removal of a to backends. The algorithm has the property that the addition/removal of a
host from a set of N hosts only affects 1/N of the requests. host from a set of N hosts only affects 1/N of the requests."
- RANDOM - The load balancer selects a random healthy host. - "* RANDOM - The load balancer selects a random healthy host."
- ORIGINAL_DESTINATION - Backend host is selected based on the client connection - "* ORIGINAL_DESTINATION - Backend host is selected based on the client connection
metadata, i.e., connections are opened to the same address as the destination metadata, i.e., connections are opened to the same address as the destination
address of the incoming connection before the connection was redirected to address of the incoming connection before the connection was redirected to
the load balancer. the load balancer."
- MAGLEV - used as a drop in replacement for the ring hash load balancer. - "* MAGLEV - used as a drop in replacement for the ring hash load balancer."
- Maglev is not as stable as ring hash but has faster table lookup build times - Maglev is not as stable as ring hash but has faster table lookup build times
and host selection times. For more information about Maglev, refer to https://ai.google/research/pubs/pub44824 and host selection times. For more information about Maglev, refer to https://ai.google/research/pubs/pub44824
This field is applicable only when the `load_balancing_scheme` is set to INTERNAL_MANAGED This field is applicable only when the `load_balancing_scheme` is set to INTERNAL_MANAGED

8
plugins/modules/gcp_compute_region_health_check.py
View file

@ -434,9 +434,9 @@ options:
grpc_service_name: grpc_service_name:
description: description:
- 'The gRPC service name for the health check. The value of grpcServiceName - 'The gRPC service name for the health check. The value of grpcServiceName
has the following meanings by convention: - Empty serviceName means the has the following meanings by convention: * Empty serviceName means the
overall status of all services at the backend.' overall status of all services at the backend.'
- "- Non-empty serviceName means the health of that gRPC service, as defined - "* Non-empty serviceName means the health of that gRPC service, as defined
by the owner of the service." by the owner of the service."
- The grpcServiceName can only be ASCII. - The grpcServiceName can only be ASCII.
required: false required: false
@ -873,9 +873,9 @@ grpcHealthCheck:
grpcServiceName: grpcServiceName:
description: description:
- 'The gRPC service name for the health check. The value of grpcServiceName - 'The gRPC service name for the health check. The value of grpcServiceName
has the following meanings by convention: - Empty serviceName means the overall has the following meanings by convention: * Empty serviceName means the overall
status of all services at the backend.' status of all services at the backend.'
- "- Non-empty serviceName means the health of that gRPC service, as defined - "* Non-empty serviceName means the health of that gRPC service, as defined
by the owner of the service." by the owner of the service."
- The grpcServiceName can only be ASCII. - The grpcServiceName can only be ASCII.
returned: success returned: success

4
plugins/modules/gcp_compute_region_health_check_info.py
View file

@ -493,9 +493,9 @@ resources:
grpcServiceName: grpcServiceName:
description: description:
- 'The gRPC service name for the health check. The value of grpcServiceName - 'The gRPC service name for the health check. The value of grpcServiceName
has the following meanings by convention: - Empty serviceName means the has the following meanings by convention: * Empty serviceName means the
overall status of all services at the backend.' overall status of all services at the backend.'
- "- Non-empty serviceName means the health of that gRPC service, as defined - "* Non-empty serviceName means the health of that gRPC service, as defined
by the owner of the service." by the owner of the service."
- The grpcServiceName can only be ASCII. - The grpcServiceName can only be ASCII.
returned: success returned: success

60
plugins/modules/gcp_compute_region_url_map.py
View file

@ -324,10 +324,10 @@ options:
- The header value must be an integer and its value must be in - The header value must be an integer and its value must be in
the range specified in rangeMatch. If the header does not contain the range specified in rangeMatch. If the header does not contain
an integer, number or is empty, the match fails. For example an integer, number or is empty, the match fails. For example
for a range [-5, 0] - -3 will match. - 0 will not match. - 0.25 for a range [-5, 0] * -3 will match * 0 will not match * 0.25
will not match. - -3someString will not match. Only one of exactMatch, will not match * -3someString will not match.
prefixMatch, suffixMatch, regexMatch, presentMatch or rangeMatch - Only one of exactMatch, prefixMatch, suffixMatch, regexMatch,
must be set. presentMatch or rangeMatch must be set.
required: false required: false
type: dict type: dict
suboptions: suboptions:
@ -411,9 +411,9 @@ options:
description: description:
- 'Specifies how individual filterLabel matches within the list - 'Specifies how individual filterLabel matches within the list
of filterLabels contribute towards the overall metadataFilter of filterLabels contribute towards the overall metadataFilter
match. Supported values are: - MATCH_ANY: At least one of the match. Supported values are: * MATCH_ANY: At least one of the
filterLabels must have a matching label in the provided metadata.' filterLabels must have a matching label in the provided metadata.'
- "- MATCH_ALL: All filterLabels must have matching labels in - "* MATCH_ALL: All filterLabels must have matching labels in
the provided metadata." the provided metadata."
- 'Some valid choices include: "MATCH_ALL", "MATCH_ANY"' - 'Some valid choices include: "MATCH_ALL", "MATCH_ANY"'
required: true required: true
@ -675,26 +675,26 @@ options:
retry_conditions: retry_conditions:
description: description:
- 'Specfies one or more conditions when this retry rule applies. - 'Specfies one or more conditions when this retry rule applies.
Valid values are: - 5xx: Loadbalancer will attempt a retry if Valid values are: * 5xx: Loadbalancer will attempt a retry if
the backend service responds with any 5xx response code, or the backend service responds with any 5xx response code, or
if the backend service does not respond at all, example: disconnects, if the backend service does not respond at all, example: disconnects,
reset, read timeout, connection failure, and refused streams.' reset, read timeout, connection failure, and refused streams.'
- "- gateway-error: Similar to 5xx, but only applies to response - "* gateway-error: Similar to 5xx, but only applies to response
codes 502, 503 or 504." codes 502, 503 or 504."
- "- connect-failure: Loadbalancer will retry on failures connecting - "* connect-failure: Loadbalancer will retry on failures connecting
to backend services, for example due to connection timeouts." to backend services, for example due to connection timeouts."
- "- retriable-4xx: Loadbalancer will retry for retriable 4xx - "* retriable-4xx: Loadbalancer will retry for retriable 4xx
response codes." response codes."
- Currently the only retriable error supported is 409. - Currently the only retriable error supported is 409.
- "- refused-stream: Loadbalancer will retry if the backend service - "* refused-stream: Loadbalancer will retry if the backend service
resets the stream with a REFUSED_STREAM error code. This reset resets the stream with a REFUSED_STREAM error code. This reset
type indicates that it is safe to retry." type indicates that it is safe to retry."
- "- cancelled: Loadbalancer will retry if the gRPC status code - "* cancelled: Loadbalancer will retry if the gRPC status code
in the response header is set to cancelled - deadline-exceeded: in the response header is set to cancelled * deadline-exceeded:
Loadbalancer will retry if the gRPC status code in the response Loadbalancer will retry if the gRPC status code in the response
header is set to deadline-exceeded - resource-exhausted: Loadbalancer header is set to deadline-exceeded * resource-exhausted: Loadbalancer
will retry if the gRPC status code in the response header is will retry if the gRPC status code in the response header is
set to resource-exhausted - unavailable: Loadbalancer will retry set to resource-exhausted * unavailable: Loadbalancer will retry
if the gRPC status code in the response header is set to unavailable if the gRPC status code in the response header is set to unavailable
." ."
elements: str elements: str
@ -1935,10 +1935,10 @@ pathMatchers:
- The header value must be an integer and its value must be in the - The header value must be an integer and its value must be in the
range specified in rangeMatch. If the header does not contain range specified in rangeMatch. If the header does not contain
an integer, number or is empty, the match fails. For example for an integer, number or is empty, the match fails. For example for
a range [-5, 0] - -3 will match. - 0 will not match. - 0.25 will a range [-5, 0] * -3 will match * 0 will not match * 0.25 will
not match. - -3someString will not match. Only one of exactMatch, not match * -3someString will not match.
prefixMatch, suffixMatch, regexMatch, presentMatch or rangeMatch - Only one of exactMatch, prefixMatch, suffixMatch, regexMatch,
must be set. presentMatch or rangeMatch must be set.
returned: success returned: success
type: complex type: complex
contains: contains:
@ -2017,9 +2017,9 @@ pathMatchers:
description: description:
- 'Specifies how individual filterLabel matches within the list - 'Specifies how individual filterLabel matches within the list
of filterLabels contribute towards the overall metadataFilter of filterLabels contribute towards the overall metadataFilter
match. Supported values are: - MATCH_ANY: At least one of the match. Supported values are: * MATCH_ANY: At least one of the
filterLabels must have a matching label in the provided metadata.' filterLabels must have a matching label in the provided metadata.'
- "- MATCH_ALL: All filterLabels must have matching labels in the - "* MATCH_ALL: All filterLabels must have matching labels in the
provided metadata." provided metadata."
returned: success returned: success
type: str type: str
@ -2261,26 +2261,26 @@ pathMatchers:
retryConditions: retryConditions:
description: description:
- 'Specfies one or more conditions when this retry rule applies. - 'Specfies one or more conditions when this retry rule applies.
Valid values are: - 5xx: Loadbalancer will attempt a retry if Valid values are: * 5xx: Loadbalancer will attempt a retry if
the backend service responds with any 5xx response code, or if the backend service responds with any 5xx response code, or if
the backend service does not respond at all, example: disconnects, the backend service does not respond at all, example: disconnects,
reset, read timeout, connection failure, and refused streams.' reset, read timeout, connection failure, and refused streams.'
- "- gateway-error: Similar to 5xx, but only applies to response - "* gateway-error: Similar to 5xx, but only applies to response
codes 502, 503 or 504." codes 502, 503 or 504."
- "- connect-failure: Loadbalancer will retry on failures connecting - "* connect-failure: Loadbalancer will retry on failures connecting
to backend services, for example due to connection timeouts." to backend services, for example due to connection timeouts."
- "- retriable-4xx: Loadbalancer will retry for retriable 4xx response - "* retriable-4xx: Loadbalancer will retry for retriable 4xx response
codes." codes."
- Currently the only retriable error supported is 409. - Currently the only retriable error supported is 409.
- "- refused-stream: Loadbalancer will retry if the backend service - "* refused-stream: Loadbalancer will retry if the backend service
resets the stream with a REFUSED_STREAM error code. This reset resets the stream with a REFUSED_STREAM error code. This reset
type indicates that it is safe to retry." type indicates that it is safe to retry."
- "- cancelled: Loadbalancer will retry if the gRPC status code - "* cancelled: Loadbalancer will retry if the gRPC status code
in the response header is set to cancelled - deadline-exceeded: in the response header is set to cancelled * deadline-exceeded:
Loadbalancer will retry if the gRPC status code in the response Loadbalancer will retry if the gRPC status code in the response
header is set to deadline-exceeded - resource-exhausted: Loadbalancer header is set to deadline-exceeded * resource-exhausted: Loadbalancer
will retry if the gRPC status code in the response header is set will retry if the gRPC status code in the response header is set
to resource-exhausted - unavailable: Loadbalancer will retry if to resource-exhausted * unavailable: Loadbalancer will retry if
the gRPC status code in the response header is set to unavailable the gRPC status code in the response header is set to unavailable
." ."
returned: success returned: success

28
plugins/modules/gcp_compute_region_url_map_info.py
View file

@ -386,9 +386,9 @@ resources:
- The header value must be an integer and its value must be - The header value must be an integer and its value must be
in the range specified in rangeMatch. If the header does not in the range specified in rangeMatch. If the header does not
contain an integer, number or is empty, the match fails. For contain an integer, number or is empty, the match fails. For
example for a range [-5, 0] - -3 will match. - 0 will not example for a range [-5, 0] * -3 will match * 0 will not match
match. - 0.25 will not match. - -3someString will not match. * 0.25 will not match * -3someString will not match.
Only one of exactMatch, prefixMatch, suffixMatch, regexMatch, - Only one of exactMatch, prefixMatch, suffixMatch, regexMatch,
presentMatch or rangeMatch must be set. presentMatch or rangeMatch must be set.
returned: success returned: success
type: complex type: complex
@ -471,10 +471,10 @@ resources:
description: description:
- 'Specifies how individual filterLabel matches within the list - 'Specifies how individual filterLabel matches within the list
of filterLabels contribute towards the overall metadataFilter of filterLabels contribute towards the overall metadataFilter
match. Supported values are: - MATCH_ANY: At least one of match. Supported values are: * MATCH_ANY: At least one of
the filterLabels must have a matching label in the provided the filterLabels must have a matching label in the provided
metadata.' metadata.'
- "- MATCH_ALL: All filterLabels must have matching labels in - "* MATCH_ALL: All filterLabels must have matching labels in
the provided metadata." the provided metadata."
returned: success returned: success
type: str type: str
@ -724,27 +724,27 @@ resources:
retryConditions: retryConditions:
description: description:
- 'Specfies one or more conditions when this retry rule applies. - 'Specfies one or more conditions when this retry rule applies.
Valid values are: - 5xx: Loadbalancer will attempt a retry Valid values are: * 5xx: Loadbalancer will attempt a retry
if the backend service responds with any 5xx response code, if the backend service responds with any 5xx response code,
or if the backend service does not respond at all, example: or if the backend service does not respond at all, example:
disconnects, reset, read timeout, connection failure, and disconnects, reset, read timeout, connection failure, and
refused streams.' refused streams.'
- "- gateway-error: Similar to 5xx, but only applies to response - "* gateway-error: Similar to 5xx, but only applies to response
codes 502, 503 or 504." codes 502, 503 or 504."
- "- connect-failure: Loadbalancer will retry on failures connecting - "* connect-failure: Loadbalancer will retry on failures connecting
to backend services, for example due to connection timeouts." to backend services, for example due to connection timeouts."
- "- retriable-4xx: Loadbalancer will retry for retriable 4xx - "* retriable-4xx: Loadbalancer will retry for retriable 4xx
response codes." response codes."
- Currently the only retriable error supported is 409. - Currently the only retriable error supported is 409.
- "- refused-stream: Loadbalancer will retry if the backend - "* refused-stream: Loadbalancer will retry if the backend
service resets the stream with a REFUSED_STREAM error code. service resets the stream with a REFUSED_STREAM error code.
This reset type indicates that it is safe to retry." This reset type indicates that it is safe to retry."
- "- cancelled: Loadbalancer will retry if the gRPC status code - "* cancelled: Loadbalancer will retry if the gRPC status code
in the response header is set to cancelled - deadline-exceeded: in the response header is set to cancelled * deadline-exceeded:
Loadbalancer will retry if the gRPC status code in the response Loadbalancer will retry if the gRPC status code in the response
header is set to deadline-exceeded - resource-exhausted: Loadbalancer header is set to deadline-exceeded * resource-exhausted: Loadbalancer
will retry if the gRPC status code in the response header will retry if the gRPC status code in the response header
is set to resource-exhausted - unavailable: Loadbalancer will is set to resource-exhausted * unavailable: Loadbalancer will
retry if the gRPC status code in the response header is set retry if the gRPC status code in the response header is set
to unavailable ." to unavailable ."
returned: success returned: success

12
plugins/modules/gcp_compute_target_pool.py
View file

@ -119,11 +119,11 @@ options:
type: str type: str
session_affinity: session_affinity:
description: description:
- 'Session affinity option. Must be one of these values: - NONE: Connections from - 'Session affinity option. Must be one of these values: * NONE: Connections from
the same client IP may go to any instance in the pool.' the same client IP may go to any instance in the pool.'
- "- CLIENT_IP: Connections from the same client IP will go to the same instance - "* CLIENT_IP: Connections from the same client IP will go to the same instance
in the pool while that instance remains healthy." in the pool while that instance remains healthy."
- "- CLIENT_IP_PROTO: Connections from the same client IP with the same IP protocol - "* CLIENT_IP_PROTO: Connections from the same client IP with the same IP protocol
will go to the same instance in the pool while that instance remains healthy." will go to the same instance in the pool while that instance remains healthy."
- 'Some valid choices include: "NONE", "CLIENT_IP", "CLIENT_IP_PROTO"' - 'Some valid choices include: "NONE", "CLIENT_IP", "CLIENT_IP_PROTO"'
required: false required: false
@ -269,11 +269,11 @@ name:
type: str type: str
sessionAffinity: sessionAffinity:
description: description:
- 'Session affinity option. Must be one of these values: - NONE: Connections from - 'Session affinity option. Must be one of these values: * NONE: Connections from
the same client IP may go to any instance in the pool.' the same client IP may go to any instance in the pool.'
- "- CLIENT_IP: Connections from the same client IP will go to the same instance - "* CLIENT_IP: Connections from the same client IP will go to the same instance
in the pool while that instance remains healthy." in the pool while that instance remains healthy."
- "- CLIENT_IP_PROTO: Connections from the same client IP with the same IP protocol - "* CLIENT_IP_PROTO: Connections from the same client IP with the same IP protocol
will go to the same instance in the pool while that instance remains healthy." will go to the same instance in the pool while that instance remains healthy."
returned: success returned: success
type: str type: str

6
plugins/modules/gcp_compute_target_pool_info.py
View file

@ -190,11 +190,11 @@ resources:
type: str type: str
sessionAffinity: sessionAffinity:
description: description:
- 'Session affinity option. Must be one of these values: - NONE: Connections - 'Session affinity option. Must be one of these values: * NONE: Connections
from the same client IP may go to any instance in the pool.' from the same client IP may go to any instance in the pool.'
- "- CLIENT_IP: Connections from the same client IP will go to the same instance - "* CLIENT_IP: Connections from the same client IP will go to the same instance
in the pool while that instance remains healthy." in the pool while that instance remains healthy."
- "- CLIENT_IP_PROTO: Connections from the same client IP with the same IP protocol - "* CLIENT_IP_PROTO: Connections from the same client IP with the same IP protocol
will go to the same instance in the pool while that instance remains healthy." will go to the same instance in the pool while that instance remains healthy."
returned: success returned: success
type: str type: str

197
plugins/modules/gcp_compute_url_map.py
View file

@ -529,26 +529,26 @@ options:
retry_conditions: retry_conditions:
description: description:
- 'Specifies one or more conditions when this retry rule applies. - 'Specifies one or more conditions when this retry rule applies.
Valid values are: - 5xx: Loadbalancer will attempt a retry if Valid values are: * 5xx: Loadbalancer will attempt a retry if
the backend service responds with any 5xx response code, or the backend service responds with any 5xx response code, or
if the backend service does not respond at all, example: disconnects, if the backend service does not respond at all, example: disconnects,
reset, read timeout, connection failure, and refused streams.' reset, read timeout, connection failure, and refused streams.'
- "- gateway-error: Similar to 5xx, but only applies to response - "* gateway-error: Similar to 5xx, but only applies to response
codes 502, 503 or 504." codes 502, 503 or 504."
- "- connect-failure: Loadbalancer will retry on failures connecting - "* connect-failure: Loadbalancer will retry on failures connecting
to backend services, for example due to connection timeouts." to backend services, for example due to connection timeouts."
- "- retriable-4xx: Loadbalancer will retry for retriable 4xx - "* retriable-4xx: Loadbalancer will retry for retriable 4xx
response codes." response codes."
- Currently the only retriable error supported is 409. - Currently the only retriable error supported is 409.
- "- refused-stream: Loadbalancer will retry if the backend service - "* refused-stream: Loadbalancer will retry if the backend service
resets the stream with a REFUSED_STREAM error code. This reset resets the stream with a REFUSED_STREAM error code. This reset
type indicates that it is safe to retry." type indicates that it is safe to retry."
- "- cancelled: Loadbalancer will retry if the gRPC status code - "* cancelled: Loadbalancer will retry if the gRPC status code
in the response header is set to cancelled - deadline-exceeded: in the response header is set to cancelled * deadline-exceeded:
Loadbalancer will retry if the gRPC status code in the response Loadbalancer will retry if the gRPC status code in the response
header is set to deadline-exceeded - resource-exhausted: Loadbalancer header is set to deadline-exceeded * resource-exhausted: Loadbalancer
will retry if the gRPC status code in the response header is will retry if the gRPC status code in the response header is
set to resource-exhausted - unavailable: Loadbalancer will retry set to resource-exhausted * unavailable: Loadbalancer will retry
if the gRPC status code in the response header is set to unavailable if the gRPC status code in the response header is set to unavailable
." ."
elements: str elements: str
@ -1324,26 +1324,26 @@ options:
retry_conditions: retry_conditions:
description: description:
- 'Specfies one or more conditions when this retry rule applies. - 'Specfies one or more conditions when this retry rule applies.
Valid values are: - 5xx: Loadbalancer will attempt a retry if Valid values are: * 5xx: Loadbalancer will attempt a retry if
the backend service responds with any 5xx response code, or the backend service responds with any 5xx response code, or
if the backend service does not respond at all, example: disconnects, if the backend service does not respond at all, example: disconnects,
reset, read timeout, connection failure, and refused streams.' reset, read timeout, connection failure, and refused streams.'
- "- gateway-error: Similar to 5xx, but only applies to response - "* gateway-error: Similar to 5xx, but only applies to response
codes 502, 503 or 504." codes 502, 503 or 504."
- "- connect-failure: Loadbalancer will retry on failures connecting - "* connect-failure: Loadbalancer will retry on failures connecting
to backend services, for example due to connection timeouts." to backend services, for example due to connection timeouts."
- "- retriable-4xx: Loadbalancer will retry for retriable 4xx - "* retriable-4xx: Loadbalancer will retry for retriable 4xx
response codes." response codes."
- Currently the only retriable error supported is 409. - Currently the only retriable error supported is 409.
- "- refused-stream: Loadbalancer will retry if the backend service - "* refused-stream: Loadbalancer will retry if the backend service
resets the stream with a REFUSED_STREAM error code. This reset resets the stream with a REFUSED_STREAM error code. This reset
type indicates that it is safe to retry." type indicates that it is safe to retry."
- "- cancelled: Loadbalancer will retry if the gRPC status code - "* cancelled: Loadbalancer will retry if the gRPC status code
in the response header is set to cancelled - deadline-exceeded: in the response header is set to cancelled * deadline-exceeded:
Loadbalancer will retry if the gRPC status code in the response Loadbalancer will retry if the gRPC status code in the response
header is set to deadline-exceeded - resource-exhausted: Loadbalancer header is set to deadline-exceeded * resource-exhausted: Loadbalancer
will retry if the gRPC status code in the response header is will retry if the gRPC status code in the response header is
set to resource-exhausted - unavailable: Loadbalancer will retry set to resource-exhausted * unavailable: Loadbalancer will retry
if the gRPC status code in the response header is set to unavailable if the gRPC status code in the response header is set to unavailable
." ."
elements: str elements: str
@ -1827,27 +1827,27 @@ options:
retry_conditions: retry_conditions:
description: description:
- 'Specfies one or more conditions when this retry rule applies. Valid - 'Specfies one or more conditions when this retry rule applies. Valid
values are: 5xx: Loadbalancer will attempt a retry if the backend values are: * 5xx: Loadbalancer will attempt a retry if the backend
service responds with any 5xx response code, or if the backend service service responds with any 5xx response code, or if the backend service
does not respond at all, example: disconnects, reset, read timeout, does not respond at all, example: disconnects, reset, read timeout,
connection failure, and refused streams.' * connection failure, and refused streams.'
- 'gateway-error: Similar to 5xx, but only applies to response codes - "* gateway-error: Similar to 5xx, but only applies to response codes
502, 503 or 504.' 502, 503 or 504."
- 'connect-failure: Loadbalancer will retry on failures connecting - "* connect-failure: Loadbalancer will retry on failures connecting
to backend services, for example due to connection timeouts.' to backend services, for example due to connection timeouts."
- 'retriable-4xx: Loadbalancer will retry for retriable 4xx response - "* retriable-4xx: Loadbalancer will retry for retriable 4xx response
codes.' codes."
- Currently the only retriable error supported is 409. - Currently the only retriable error supported is 409.
- refused-stream:Loadbalancer will retry if the backend service resets - "* refused-stream:Loadbalancer will retry if the backend service
the stream with a REFUSED_STREAM error code. resets the stream with a REFUSED_STREAM error code."
- This reset type indicates that it is safe to retry. - This reset type indicates that it is safe to retry.
- 'cancelled: Loadbalancer will retry if the gRPC status code in the - "* cancelled: Loadbalancer will retry if the gRPC status code in
response header is set to cancelled deadline-exceeded: Loadbalancer the response header is set to cancelled * deadline-exceeded: Loadbalancer
will retry if the gRPC status code in the response header is set will retry if the gRPC status code in the response header is set
to deadline-exceeded resource-exhausted: Loadbalancer will retry to deadline-exceeded * resource-exhausted: Loadbalancer will retry
if the gRPC status code in the response header is set to resource-exhausted if the gRPC status code in the response header is set to resource-exhausted
unavailable: Loadbalancer will retry if the gRPC status code in * unavailable: Loadbalancer will retry if the gRPC status code in
the response header is set to unavailable .' the response header is set to unavailable ."
elements: str elements: str
required: false required: false
type: list type: list
@ -2324,26 +2324,27 @@ options:
retry_conditions: retry_conditions:
description: description:
- 'Specfies one or more conditions when this retry rule applies. Valid - 'Specfies one or more conditions when this retry rule applies. Valid
values are: 5xx: Loadbalancer will attempt a retry if the backend service values are: * 5xx: Loadbalancer will attempt a retry if the backend
responds with any 5xx response code, or if the backend service does service responds with any 5xx response code, or if the backend service
not respond at all, example: disconnects, reset, read timeout, connection does not respond at all, example: disconnects, reset, read timeout,
failure, and refused streams.' * connection failure, and refused streams.'
- 'gateway-error: Similar to 5xx, but only applies to response codes 502, - "* gateway-error: Similar to 5xx, but only applies to response codes
503 or 504.' 502, 503 or 504."
- 'connect-failure: Loadbalancer will retry on failures connecting to - "* connect-failure: Loadbalancer will retry on failures connecting to
backend services, for example due to connection timeouts.' backend services, for example due to connection timeouts."
- 'retriable-4xx: Loadbalancer will retry for retriable 4xx response codes.' - "* retriable-4xx: Loadbalancer will retry for retriable 4xx response
codes."
- Currently the only retriable error supported is 409. - Currently the only retriable error supported is 409.
- refused-stream:Loadbalancer will retry if the backend service resets - "* refused-stream:Loadbalancer will retry if the backend service resets
the stream with a REFUSED_STREAM error code. the stream with a REFUSED_STREAM error code."
- This reset type indicates that it is safe to retry. - This reset type indicates that it is safe to retry.
- 'cancelled: Loadbalancer will retry if the gRPC status code in the response - "* cancelled: Loadbalancer will retry if the gRPC status code in the
header is set to cancelled deadline-exceeded: Loadbalancer will retry response header is set to cancelled * deadline-exceeded: Loadbalancer
if the gRPC status code in the response header is set to deadline-exceeded
resource-exhausted: Loadbalancer will retry if the gRPC status code
in the response header is set to resource-exhausted unavailable: Loadbalancer
will retry if the gRPC status code in the response header is set to will retry if the gRPC status code in the response header is set to
unavailable .' deadline-exceeded * resource-exhausted: Loadbalancer will retry if the
gRPC status code in the response header is set to resource-exhausted
* unavailable: Loadbalancer will retry if the gRPC status code in the
response header is set to unavailable ."
elements: str elements: str
required: false required: false
type: list type: list
@ -3086,26 +3087,26 @@ pathMatchers:
retryConditions: retryConditions:
description: description:
- 'Specifies one or more conditions when this retry rule applies. - 'Specifies one or more conditions when this retry rule applies.
Valid values are: - 5xx: Loadbalancer will attempt a retry if Valid values are: * 5xx: Loadbalancer will attempt a retry if
the backend service responds with any 5xx response code, or if the backend service responds with any 5xx response code, or if
the backend service does not respond at all, example: disconnects, the backend service does not respond at all, example: disconnects,
reset, read timeout, connection failure, and refused streams.' reset, read timeout, connection failure, and refused streams.'
- "- gateway-error: Similar to 5xx, but only applies to response - "* gateway-error: Similar to 5xx, but only applies to response
codes 502, 503 or 504." codes 502, 503 or 504."
- "- connect-failure: Loadbalancer will retry on failures connecting - "* connect-failure: Loadbalancer will retry on failures connecting
to backend services, for example due to connection timeouts." to backend services, for example due to connection timeouts."
- "- retriable-4xx: Loadbalancer will retry for retriable 4xx response - "* retriable-4xx: Loadbalancer will retry for retriable 4xx response
codes." codes."
- Currently the only retriable error supported is 409. - Currently the only retriable error supported is 409.
- "- refused-stream: Loadbalancer will retry if the backend service - "* refused-stream: Loadbalancer will retry if the backend service
resets the stream with a REFUSED_STREAM error code. This reset resets the stream with a REFUSED_STREAM error code. This reset
type indicates that it is safe to retry." type indicates that it is safe to retry."
- "- cancelled: Loadbalancer will retry if the gRPC status code - "* cancelled: Loadbalancer will retry if the gRPC status code
in the response header is set to cancelled - deadline-exceeded: in the response header is set to cancelled * deadline-exceeded:
Loadbalancer will retry if the gRPC status code in the response Loadbalancer will retry if the gRPC status code in the response
header is set to deadline-exceeded - resource-exhausted: Loadbalancer header is set to deadline-exceeded * resource-exhausted: Loadbalancer
will retry if the gRPC status code in the response header is set will retry if the gRPC status code in the response header is set
to resource-exhausted - unavailable: Loadbalancer will retry if to resource-exhausted * unavailable: Loadbalancer will retry if
the gRPC status code in the response header is set to unavailable the gRPC status code in the response header is set to unavailable
." ."
returned: success returned: success
@ -3825,26 +3826,26 @@ pathMatchers:
retryConditions: retryConditions:
description: description:
- 'Specfies one or more conditions when this retry rule applies. - 'Specfies one or more conditions when this retry rule applies.
Valid values are: - 5xx: Loadbalancer will attempt a retry if Valid values are: * 5xx: Loadbalancer will attempt a retry if
the backend service responds with any 5xx response code, or if the backend service responds with any 5xx response code, or if
the backend service does not respond at all, example: disconnects, the backend service does not respond at all, example: disconnects,
reset, read timeout, connection failure, and refused streams.' reset, read timeout, connection failure, and refused streams.'
- "- gateway-error: Similar to 5xx, but only applies to response - "* gateway-error: Similar to 5xx, but only applies to response
codes 502, 503 or 504." codes 502, 503 or 504."
- "- connect-failure: Loadbalancer will retry on failures connecting - "* connect-failure: Loadbalancer will retry on failures connecting
to backend services, for example due to connection timeouts." to backend services, for example due to connection timeouts."
- "- retriable-4xx: Loadbalancer will retry for retriable 4xx response - "* retriable-4xx: Loadbalancer will retry for retriable 4xx response
codes." codes."
- Currently the only retriable error supported is 409. - Currently the only retriable error supported is 409.
- "- refused-stream: Loadbalancer will retry if the backend service - "* refused-stream: Loadbalancer will retry if the backend service
resets the stream with a REFUSED_STREAM error code. This reset resets the stream with a REFUSED_STREAM error code. This reset
type indicates that it is safe to retry." type indicates that it is safe to retry."
- "- cancelled: Loadbalancer will retry if the gRPC status code - "* cancelled: Loadbalancer will retry if the gRPC status code
in the response header is set to cancelled - deadline-exceeded: in the response header is set to cancelled * deadline-exceeded:
Loadbalancer will retry if the gRPC status code in the response Loadbalancer will retry if the gRPC status code in the response
header is set to deadline-exceeded - resource-exhausted: Loadbalancer header is set to deadline-exceeded * resource-exhausted: Loadbalancer
will retry if the gRPC status code in the response header is set will retry if the gRPC status code in the response header is set
to resource-exhausted - unavailable: Loadbalancer will retry if to resource-exhausted * unavailable: Loadbalancer will retry if
the gRPC status code in the response header is set to unavailable the gRPC status code in the response header is set to unavailable
." ."
returned: success returned: success
@ -4292,27 +4293,27 @@ pathMatchers:
retryConditions: retryConditions:
description: description:
- 'Specfies one or more conditions when this retry rule applies. Valid - 'Specfies one or more conditions when this retry rule applies. Valid
values are: 5xx: Loadbalancer will attempt a retry if the backend values are: * 5xx: Loadbalancer will attempt a retry if the backend
service responds with any 5xx response code, or if the backend service service responds with any 5xx response code, or if the backend service
does not respond at all, example: disconnects, reset, read timeout, does not respond at all, example: disconnects, reset, read timeout,
connection failure, and refused streams.' * connection failure, and refused streams.'
- 'gateway-error: Similar to 5xx, but only applies to response codes - "* gateway-error: Similar to 5xx, but only applies to response codes
502, 503 or 504.' 502, 503 or 504."
- 'connect-failure: Loadbalancer will retry on failures connecting to - "* connect-failure: Loadbalancer will retry on failures connecting
backend services, for example due to connection timeouts.' to backend services, for example due to connection timeouts."
- 'retriable-4xx: Loadbalancer will retry for retriable 4xx response - "* retriable-4xx: Loadbalancer will retry for retriable 4xx response
codes.' codes."
- Currently the only retriable error supported is 409. - Currently the only retriable error supported is 409.
- refused-stream:Loadbalancer will retry if the backend service resets - "* refused-stream:Loadbalancer will retry if the backend service resets
the stream with a REFUSED_STREAM error code. the stream with a REFUSED_STREAM error code."
- This reset type indicates that it is safe to retry. - This reset type indicates that it is safe to retry.
- 'cancelled: Loadbalancer will retry if the gRPC status code in the - "* cancelled: Loadbalancer will retry if the gRPC status code in the
response header is set to cancelled deadline-exceeded: Loadbalancer response header is set to cancelled * deadline-exceeded: Loadbalancer
will retry if the gRPC status code in the response header is set to will retry if the gRPC status code in the response header is set to
deadline-exceeded resource-exhausted: Loadbalancer will retry if the deadline-exceeded * resource-exhausted: Loadbalancer will retry if
gRPC status code in the response header is set to resource-exhausted the gRPC status code in the response header is set to resource-exhausted
unavailable: Loadbalancer will retry if the gRPC status code in the * unavailable: Loadbalancer will retry if the gRPC status code in
response header is set to unavailable .' the response header is set to unavailable ."
returned: success returned: success
type: list type: list
numRetries: numRetries:
@ -4748,26 +4749,26 @@ defaultRouteAction:
retryConditions: retryConditions:
description: description:
- 'Specfies one or more conditions when this retry rule applies. Valid values - 'Specfies one or more conditions when this retry rule applies. Valid values
are: 5xx: Loadbalancer will attempt a retry if the backend service responds are: * 5xx: Loadbalancer will attempt a retry if the backend service responds
with any 5xx response code, or if the backend service does not respond with any 5xx response code, or if the backend service does not respond
at all, example: disconnects, reset, read timeout, connection failure, at all, example: disconnects, reset, read timeout, * connection failure,
and refused streams.' and refused streams.'
- 'gateway-error: Similar to 5xx, but only applies to response codes 502, - "* gateway-error: Similar to 5xx, but only applies to response codes 502,
503 or 504.' 503 or 504."
- 'connect-failure: Loadbalancer will retry on failures connecting to backend - "* connect-failure: Loadbalancer will retry on failures connecting to
services, for example due to connection timeouts.' backend services, for example due to connection timeouts."
- 'retriable-4xx: Loadbalancer will retry for retriable 4xx response codes.' - "* retriable-4xx: Loadbalancer will retry for retriable 4xx response codes."
- Currently the only retriable error supported is 409. - Currently the only retriable error supported is 409.
- refused-stream:Loadbalancer will retry if the backend service resets the - "* refused-stream:Loadbalancer will retry if the backend service resets
stream with a REFUSED_STREAM error code. the stream with a REFUSED_STREAM error code."
- This reset type indicates that it is safe to retry. - This reset type indicates that it is safe to retry.
- 'cancelled: Loadbalancer will retry if the gRPC status code in the response - "* cancelled: Loadbalancer will retry if the gRPC status code in the response
header is set to cancelled deadline-exceeded: Loadbalancer will retry header is set to cancelled * deadline-exceeded: Loadbalancer will retry
if the gRPC status code in the response header is set to deadline-exceeded if the gRPC status code in the response header is set to deadline-exceeded
resource-exhausted: Loadbalancer will retry if the gRPC status code in * resource-exhausted: Loadbalancer will retry if the gRPC status code
the response header is set to resource-exhausted unavailable: Loadbalancer in the response header is set to resource-exhausted * unavailable: Loadbalancer
will retry if the gRPC status code in the response header is set to unavailable will retry if the gRPC status code in the response header is set to unavailable
.' ."
returned: success returned: success
type: list type: list
numRetries: numRetries:

105
plugins/modules/gcp_compute_url_map_info.py
View file

@ -576,27 +576,27 @@ resources:
retryConditions: retryConditions:
description: description:
- 'Specifies one or more conditions when this retry rule applies. - 'Specifies one or more conditions when this retry rule applies.
Valid values are: - 5xx: Loadbalancer will attempt a retry Valid values are: * 5xx: Loadbalancer will attempt a retry
if the backend service responds with any 5xx response code, if the backend service responds with any 5xx response code,
or if the backend service does not respond at all, example: or if the backend service does not respond at all, example:
disconnects, reset, read timeout, connection failure, and disconnects, reset, read timeout, connection failure, and
refused streams.' refused streams.'
- "- gateway-error: Similar to 5xx, but only applies to response - "* gateway-error: Similar to 5xx, but only applies to response
codes 502, 503 or 504." codes 502, 503 or 504."
- "- connect-failure: Loadbalancer will retry on failures connecting - "* connect-failure: Loadbalancer will retry on failures connecting
to backend services, for example due to connection timeouts." to backend services, for example due to connection timeouts."
- "- retriable-4xx: Loadbalancer will retry for retriable 4xx - "* retriable-4xx: Loadbalancer will retry for retriable 4xx
response codes." response codes."
- Currently the only retriable error supported is 409. - Currently the only retriable error supported is 409.
- "- refused-stream: Loadbalancer will retry if the backend - "* refused-stream: Loadbalancer will retry if the backend
service resets the stream with a REFUSED_STREAM error code. service resets the stream with a REFUSED_STREAM error code.
This reset type indicates that it is safe to retry." This reset type indicates that it is safe to retry."
- "- cancelled: Loadbalancer will retry if the gRPC status code - "* cancelled: Loadbalancer will retry if the gRPC status code
in the response header is set to cancelled - deadline-exceeded: in the response header is set to cancelled * deadline-exceeded:
Loadbalancer will retry if the gRPC status code in the response Loadbalancer will retry if the gRPC status code in the response
header is set to deadline-exceeded - resource-exhausted: Loadbalancer header is set to deadline-exceeded * resource-exhausted: Loadbalancer
will retry if the gRPC status code in the response header will retry if the gRPC status code in the response header
is set to resource-exhausted - unavailable: Loadbalancer will is set to resource-exhausted * unavailable: Loadbalancer will
retry if the gRPC status code in the response header is set retry if the gRPC status code in the response header is set
to unavailable ." to unavailable ."
returned: success returned: success
@ -1331,27 +1331,27 @@ resources:
retryConditions: retryConditions:
description: description:
- 'Specfies one or more conditions when this retry rule applies. - 'Specfies one or more conditions when this retry rule applies.
Valid values are: - 5xx: Loadbalancer will attempt a retry Valid values are: * 5xx: Loadbalancer will attempt a retry
if the backend service responds with any 5xx response code, if the backend service responds with any 5xx response code,
or if the backend service does not respond at all, example: or if the backend service does not respond at all, example:
disconnects, reset, read timeout, connection failure, and disconnects, reset, read timeout, connection failure, and
refused streams.' refused streams.'
- "- gateway-error: Similar to 5xx, but only applies to response - "* gateway-error: Similar to 5xx, but only applies to response
codes 502, 503 or 504." codes 502, 503 or 504."
- "- connect-failure: Loadbalancer will retry on failures connecting - "* connect-failure: Loadbalancer will retry on failures connecting
to backend services, for example due to connection timeouts." to backend services, for example due to connection timeouts."
- "- retriable-4xx: Loadbalancer will retry for retriable 4xx - "* retriable-4xx: Loadbalancer will retry for retriable 4xx
response codes." response codes."
- Currently the only retriable error supported is 409. - Currently the only retriable error supported is 409.
- "- refused-stream: Loadbalancer will retry if the backend - "* refused-stream: Loadbalancer will retry if the backend
service resets the stream with a REFUSED_STREAM error code. service resets the stream with a REFUSED_STREAM error code.
This reset type indicates that it is safe to retry." This reset type indicates that it is safe to retry."
- "- cancelled: Loadbalancer will retry if the gRPC status code - "* cancelled: Loadbalancer will retry if the gRPC status code
in the response header is set to cancelled - deadline-exceeded: in the response header is set to cancelled * deadline-exceeded:
Loadbalancer will retry if the gRPC status code in the response Loadbalancer will retry if the gRPC status code in the response
header is set to deadline-exceeded - resource-exhausted: Loadbalancer header is set to deadline-exceeded * resource-exhausted: Loadbalancer
will retry if the gRPC status code in the response header will retry if the gRPC status code in the response header
is set to resource-exhausted - unavailable: Loadbalancer will is set to resource-exhausted * unavailable: Loadbalancer will
retry if the gRPC status code in the response header is set retry if the gRPC status code in the response header is set
to unavailable ." to unavailable ."
returned: success returned: success
@ -1806,27 +1806,28 @@ resources:
retryConditions: retryConditions:
description: description:
- 'Specfies one or more conditions when this retry rule applies. - 'Specfies one or more conditions when this retry rule applies.
Valid values are: 5xx: Loadbalancer will attempt a retry if the Valid values are: * 5xx: Loadbalancer will attempt a retry if
backend service responds with any 5xx response code, or if the the backend service responds with any 5xx response code, or if
backend service does not respond at all, example: disconnects, the backend service does not respond at all, example: disconnects,
reset, read timeout, connection failure, and refused streams.' reset, read timeout, * connection failure, and refused streams.'
- 'gateway-error: Similar to 5xx, but only applies to response codes - "* gateway-error: Similar to 5xx, but only applies to response
502, 503 or 504.' codes 502, 503 or 504."
- 'connect-failure: Loadbalancer will retry on failures connecting - "* connect-failure: Loadbalancer will retry on failures connecting
to backend services, for example due to connection timeouts.' to backend services, for example due to connection timeouts."
- 'retriable-4xx: Loadbalancer will retry for retriable 4xx response - "* retriable-4xx: Loadbalancer will retry for retriable 4xx response
codes.' codes."
- Currently the only retriable error supported is 409. - Currently the only retriable error supported is 409.
- refused-stream:Loadbalancer will retry if the backend service - "* refused-stream:Loadbalancer will retry if the backend service
resets the stream with a REFUSED_STREAM error code. resets the stream with a REFUSED_STREAM error code."
- This reset type indicates that it is safe to retry. - This reset type indicates that it is safe to retry.
- 'cancelled: Loadbalancer will retry if the gRPC status code in - "* cancelled: Loadbalancer will retry if the gRPC status code
the response header is set to cancelled deadline-exceeded: Loadbalancer in the response header is set to cancelled * deadline-exceeded:
Loadbalancer will retry if the gRPC status code in the response
header is set to deadline-exceeded * resource-exhausted: Loadbalancer
will retry if the gRPC status code in the response header is set will retry if the gRPC status code in the response header is set
to deadline-exceeded resource-exhausted: Loadbalancer will retry to resource-exhausted * unavailable: Loadbalancer will retry if
if the gRPC status code in the response header is set to resource-exhausted the gRPC status code in the response header is set to unavailable
unavailable: Loadbalancer will retry if the gRPC status code in ."
the response header is set to unavailable .'
returned: success returned: success
type: list type: list
numRetries: numRetries:
@ -2268,27 +2269,27 @@ resources:
retryConditions: retryConditions:
description: description:
- 'Specfies one or more conditions when this retry rule applies. Valid - 'Specfies one or more conditions when this retry rule applies. Valid
values are: 5xx: Loadbalancer will attempt a retry if the backend values are: * 5xx: Loadbalancer will attempt a retry if the backend
service responds with any 5xx response code, or if the backend service service responds with any 5xx response code, or if the backend service
does not respond at all, example: disconnects, reset, read timeout, does not respond at all, example: disconnects, reset, read timeout,
connection failure, and refused streams.' * connection failure, and refused streams.'
- 'gateway-error: Similar to 5xx, but only applies to response codes - "* gateway-error: Similar to 5xx, but only applies to response codes
502, 503 or 504.' 502, 503 or 504."
- 'connect-failure: Loadbalancer will retry on failures connecting to - "* connect-failure: Loadbalancer will retry on failures connecting
backend services, for example due to connection timeouts.' to backend services, for example due to connection timeouts."
- 'retriable-4xx: Loadbalancer will retry for retriable 4xx response - "* retriable-4xx: Loadbalancer will retry for retriable 4xx response
codes.' codes."
- Currently the only retriable error supported is 409. - Currently the only retriable error supported is 409.
- refused-stream:Loadbalancer will retry if the backend service resets - "* refused-stream:Loadbalancer will retry if the backend service resets
the stream with a REFUSED_STREAM error code. the stream with a REFUSED_STREAM error code."
- This reset type indicates that it is safe to retry. - This reset type indicates that it is safe to retry.
- 'cancelled: Loadbalancer will retry if the gRPC status code in the - "* cancelled: Loadbalancer will retry if the gRPC status code in the
response header is set to cancelled deadline-exceeded: Loadbalancer response header is set to cancelled * deadline-exceeded: Loadbalancer
will retry if the gRPC status code in the response header is set to will retry if the gRPC status code in the response header is set to
deadline-exceeded resource-exhausted: Loadbalancer will retry if the deadline-exceeded * resource-exhausted: Loadbalancer will retry if
gRPC status code in the response header is set to resource-exhausted the gRPC status code in the response header is set to resource-exhausted
unavailable: Loadbalancer will retry if the gRPC status code in the * unavailable: Loadbalancer will retry if the gRPC status code in
response header is set to unavailable .' the response header is set to unavailable ."
returned: success returned: success
type: list type: list
numRetries: numRetries: