From 3af242d21da7df81c95d355271118df31797f317 Mon Sep 17 00:00:00 2001 From: The Magician Date: Fri, 16 Oct 2020 13:41:31 -0700 Subject: [PATCH] fix doc formatting errors (#4118) (#310) Co-authored-by: Riley Karson Signed-off-by: Modular Magician Co-authored-by: Riley Karson --- plugins/modules/gcp_compute_address.py | 4 +- plugins/modules/gcp_compute_address_info.py | 2 +- .../modules/gcp_compute_backend_service.py | 38 ++-- .../gcp_compute_backend_service_info.py | 20 +- plugins/modules/gcp_compute_image.py | 16 +- plugins/modules/gcp_compute_image_info.py | 9 +- .../gcp_compute_region_backend_service.py | 38 ++-- ...gcp_compute_region_backend_service_info.py | 20 +- .../gcp_compute_region_health_check.py | 8 +- .../gcp_compute_region_health_check_info.py | 4 +- plugins/modules/gcp_compute_region_url_map.py | 60 +++--- .../gcp_compute_region_url_map_info.py | 28 +-- plugins/modules/gcp_compute_target_pool.py | 12 +- .../modules/gcp_compute_target_pool_info.py | 6 +- plugins/modules/gcp_compute_url_map.py | 197 +++++++++--------- plugins/modules/gcp_compute_url_map_info.py | 105 +++++----- 16 files changed, 285 insertions(+), 282 deletions(-) diff --git a/plugins/modules/gcp_compute_address.py b/plugins/modules/gcp_compute_address.py index c11b7db..99cae76 100644 --- a/plugins/modules/gcp_compute_address.py +++ b/plugins/modules/gcp_compute_address.py @@ -86,7 +86,7 @@ options: type: str purpose: 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, and similar resources.' - This should only be set when using an Internal address. @@ -223,7 +223,7 @@ name: type: str purpose: 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, and similar resources.' - This should only be set when using an Internal address. diff --git a/plugins/modules/gcp_compute_address_info.py b/plugins/modules/gcp_compute_address_info.py index c5cc01f..bb4d5e2 100644 --- a/plugins/modules/gcp_compute_address_info.py +++ b/plugins/modules/gcp_compute_address_info.py @@ -158,7 +158,7 @@ resources: type: str purpose: 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, internal load balancers, and similar resources.' - This should only be set when using an Internal address. diff --git a/plugins/modules/gcp_compute_backend_service.py b/plugins/modules/gcp_compute_backend_service.py index 5dd1df9..dd96173 100644 --- a/plugins/modules/gcp_compute_backend_service.py +++ b/plugins/modules/gcp_compute_backend_service.py @@ -406,19 +406,19 @@ options: locality_lb_policy: description: - 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. - - LEAST_REQUEST - An O(1) algorithm which selects two random healthy hosts and - picks the host which has fewer active requests. - - RING_HASH - The ring/modulo hash load balancer implements consistent hashing + - "* LEAST_REQUEST - An O(1) algorithm which selects two random healthy hosts + and picks the host which has fewer active requests." + - "* 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 - from a set of N hosts only affects 1/N of the requests. - - RANDOM - The load balancer selects a random healthy host. - - ORIGINAL_DESTINATION - Backend host is selected based on the client connection + from a set of N hosts only affects 1/N of the requests." + - "* RANDOM - The load balancer selects a random healthy host." + - "* ORIGINAL_DESTINATION - Backend host is selected based on the client connection 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 - load balancer. - - MAGLEV - used as a drop in replacement for the ring hash load balancer. + 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 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. @@ -1067,19 +1067,19 @@ loadBalancingScheme: localityLbPolicy: description: - 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. - - LEAST_REQUEST - An O(1) algorithm which selects two random healthy hosts and picks - the host which has fewer active requests. - - 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 from - a set of N hosts only affects 1/N of the requests. - - RANDOM - The load balancer selects a random healthy host. - - ORIGINAL_DESTINATION - Backend host is selected based on the client connection + - "* LEAST_REQUEST - An O(1) algorithm which selects two random healthy hosts and + picks the host which has fewer active requests." + - "* 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 + from a set of N hosts only affects 1/N of the requests." + - "* RANDOM - The load balancer selects a random healthy host." + - "* ORIGINAL_DESTINATION - Backend host is selected based on the client connection 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 - load balancer. - - MAGLEV - used as a drop in replacement for the ring hash load balancer. + 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 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. diff --git a/plugins/modules/gcp_compute_backend_service_info.py b/plugins/modules/gcp_compute_backend_service_info.py index 8dc7105..83ef2fb 100644 --- a/plugins/modules/gcp_compute_backend_service_info.py +++ b/plugins/modules/gcp_compute_backend_service_info.py @@ -475,19 +475,19 @@ resources: localityLbPolicy: description: - 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 - healthy backend is selected in round robin order. - - LEAST_REQUEST - An O(1) algorithm which selects two random healthy hosts and - picks the host which has fewer active requests. - - RING_HASH - The ring/modulo hash load balancer implements consistent hashing + - The possible values are - * ROUND_ROBIN - This is a simple policy in which + each healthy backend is selected in round robin order. + - "* LEAST_REQUEST - An O(1) algorithm which selects two random healthy hosts + and picks the host which has fewer active requests." + - "* 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 from a set of N hosts only affects 1/N of the requests. - - RANDOM - The load balancer selects a random healthy host. - - ORIGINAL_DESTINATION - Backend host is selected based on the client connection + host from a set of N hosts only affects 1/N of the requests." + - "* RANDOM - The load balancer selects a random healthy host." + - "* ORIGINAL_DESTINATION - Backend host is selected based on the client connection 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 load balancer. - - MAGLEV - used as a drop in replacement for the ring hash load balancer. + the 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 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. diff --git a/plugins/modules/gcp_compute_image.py b/plugins/modules/gcp_compute_image.py index 6368808..35f4b12 100644 --- a/plugins/modules/gcp_compute_image.py +++ b/plugins/modules/gcp_compute_image.py @@ -187,8 +187,8 @@ options: source_image: description: - '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 - URL This property The rawDisk.source URL The sourceDisk URL .' + 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 .' - '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 of your resource''s selfLink Alternatively, you can add `register: name-of-resource` @@ -200,8 +200,8 @@ options: description: - 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 - of the following: The selfLink URL This property The sourceImage URL The rawDisk.source - URL The sourceDisk URL .' + of the following: * The selfLink URL * This property * The sourceImage URL * + The rawDisk.source URL * The sourceDisk URL .' - '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 of your resource''s selfLink Alternatively, you can add `register: name-of-resource` @@ -487,16 +487,16 @@ sourceDiskId: sourceImage: description: - '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 - URL This property The rawDisk.source URL The sourceDisk URL .' + 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 .' returned: success type: dict sourceSnapshot: description: - 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 - of the following: The selfLink URL This property The sourceImage URL The rawDisk.source - URL The sourceDisk URL .' + of the following: * The selfLink URL * This property * The sourceImage URL * The + rawDisk.source URL * The sourceDisk URL .' returned: success type: dict sourceType: diff --git a/plugins/modules/gcp_compute_image_info.py b/plugins/modules/gcp_compute_image_info.py index 5f8a3c5..a94d86b 100644 --- a/plugins/modules/gcp_compute_image_info.py +++ b/plugins/modules/gcp_compute_image_info.py @@ -311,16 +311,17 @@ resources: sourceImage: description: - '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 URL This property The rawDisk.source URL The sourceDisk URL .' + image, 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 .' returned: success type: dict sourceSnapshot: description: - 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 of the following: The selfLink URL This property The sourceImage URL The - rawDisk.source URL The sourceDisk URL .' + one of the following: * The selfLink URL * This property * The sourceImage + URL * The rawDisk.source URL * The sourceDisk URL .' returned: success type: dict sourceType: diff --git a/plugins/modules/gcp_compute_region_backend_service.py b/plugins/modules/gcp_compute_region_backend_service.py index ed8009f..1d00e0b 100644 --- a/plugins/modules/gcp_compute_region_backend_service.py +++ b/plugins/modules/gcp_compute_region_backend_service.py @@ -356,19 +356,19 @@ options: locality_lb_policy: description: - 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. - - LEAST_REQUEST - An O(1) algorithm which selects two random healthy hosts and - picks the host which has fewer active requests. - - RING_HASH - The ring/modulo hash load balancer implements consistent hashing + - "* LEAST_REQUEST - An O(1) algorithm which selects two random healthy hosts + and picks the host which has fewer active requests." + - "* 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 - from a set of N hosts only affects 1/N of the requests. - - RANDOM - The load balancer selects a random healthy host. - - ORIGINAL_DESTINATION - Backend host is selected based on the client connection + from a set of N hosts only affects 1/N of the requests." + - "* RANDOM - The load balancer selects a random healthy host." + - "* ORIGINAL_DESTINATION - Backend host is selected based on the client connection 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 - load balancer. - - MAGLEV - used as a drop in replacement for the ring hash load balancer. + 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 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 @@ -981,19 +981,19 @@ loadBalancingScheme: localityLbPolicy: description: - 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. - - LEAST_REQUEST - An O(1) algorithm which selects two random healthy hosts and picks - the host which has fewer active requests. - - 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 from - a set of N hosts only affects 1/N of the requests. - - RANDOM - The load balancer selects a random healthy host. - - ORIGINAL_DESTINATION - Backend host is selected based on the client connection + - "* LEAST_REQUEST - An O(1) algorithm which selects two random healthy hosts and + picks the host which has fewer active requests." + - "* 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 + from a set of N hosts only affects 1/N of the requests." + - "* RANDOM - The load balancer selects a random healthy host." + - "* ORIGINAL_DESTINATION - Backend host is selected based on the client connection 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 - load balancer. - - MAGLEV - used as a drop in replacement for the ring hash load balancer. + 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 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 diff --git a/plugins/modules/gcp_compute_region_backend_service_info.py b/plugins/modules/gcp_compute_region_backend_service_info.py index a030fd8..f6e4c15 100644 --- a/plugins/modules/gcp_compute_region_backend_service_info.py +++ b/plugins/modules/gcp_compute_region_backend_service_info.py @@ -436,19 +436,19 @@ resources: localityLbPolicy: description: - 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 - healthy backend is selected in round robin order. - - LEAST_REQUEST - An O(1) algorithm which selects two random healthy hosts and - picks the host which has fewer active requests. - - RING_HASH - The ring/modulo hash load balancer implements consistent hashing + - The possible values are - * ROUND_ROBIN - This is a simple policy in which + each healthy backend is selected in round robin order. + - "* LEAST_REQUEST - An O(1) algorithm which selects two random healthy hosts + and picks the host which has fewer active requests." + - "* 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 from a set of N hosts only affects 1/N of the requests. - - RANDOM - The load balancer selects a random healthy host. - - ORIGINAL_DESTINATION - Backend host is selected based on the client connection + host from a set of N hosts only affects 1/N of the requests." + - "* RANDOM - The load balancer selects a random healthy host." + - "* ORIGINAL_DESTINATION - Backend host is selected based on the client connection 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 load balancer. - - MAGLEV - used as a drop in replacement for the ring hash load balancer. + the 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 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 diff --git a/plugins/modules/gcp_compute_region_health_check.py b/plugins/modules/gcp_compute_region_health_check.py index 1dd49bf..23d9359 100644 --- a/plugins/modules/gcp_compute_region_health_check.py +++ b/plugins/modules/gcp_compute_region_health_check.py @@ -434,9 +434,9 @@ options: grpc_service_name: description: - '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.' - - "- 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." - The grpcServiceName can only be ASCII. required: false @@ -873,9 +873,9 @@ grpcHealthCheck: grpcServiceName: description: - '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.' - - "- 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." - The grpcServiceName can only be ASCII. returned: success diff --git a/plugins/modules/gcp_compute_region_health_check_info.py b/plugins/modules/gcp_compute_region_health_check_info.py index 68ca955..e11fb89 100644 --- a/plugins/modules/gcp_compute_region_health_check_info.py +++ b/plugins/modules/gcp_compute_region_health_check_info.py @@ -493,9 +493,9 @@ resources: grpcServiceName: description: - '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.' - - "- 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." - The grpcServiceName can only be ASCII. returned: success diff --git a/plugins/modules/gcp_compute_region_url_map.py b/plugins/modules/gcp_compute_region_url_map.py index 50c3086..0cea992 100644 --- a/plugins/modules/gcp_compute_region_url_map.py +++ b/plugins/modules/gcp_compute_region_url_map.py @@ -324,10 +324,10 @@ options: - The header value must be an integer and its value must be in the range specified in rangeMatch. If the header does not contain 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 not match. - -3someString will not match. Only one of exactMatch, - prefixMatch, suffixMatch, regexMatch, presentMatch or rangeMatch - must be set. + 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, prefixMatch, suffixMatch, regexMatch, + presentMatch or rangeMatch must be set. required: false type: dict suboptions: @@ -411,9 +411,9 @@ options: description: - 'Specifies how individual filterLabel matches within the list 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.' - - "- MATCH_ALL: All filterLabels must have matching labels in + - "* MATCH_ALL: All filterLabels must have matching labels in the provided metadata." - 'Some valid choices include: "MATCH_ALL", "MATCH_ANY"' required: true @@ -675,26 +675,26 @@ options: retry_conditions: description: - '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 does not respond at all, example: disconnects, 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." - - "- 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." - - "- retriable-4xx: Loadbalancer will retry for retriable 4xx + - "* retriable-4xx: Loadbalancer will retry for retriable 4xx response codes." - 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 type indicates that it is safe to retry." - - "- cancelled: Loadbalancer will retry if the gRPC status code - in the response header is set to cancelled - deadline-exceeded: + - "* cancelled: Loadbalancer will retry if the gRPC status code + 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 + 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 + set to resource-exhausted * unavailable: Loadbalancer will retry if the gRPC status code in the response header is set to unavailable ." elements: str @@ -1935,10 +1935,10 @@ pathMatchers: - The header value must be an integer and its value must be in the range specified in rangeMatch. If the header does not contain 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 - not match. - -3someString will not match. Only one of exactMatch, - prefixMatch, suffixMatch, regexMatch, presentMatch or rangeMatch - must be set. + a range [-5, 0] * -3 will match * 0 will not match * 0.25 will + not match * -3someString will not match. + - Only one of exactMatch, prefixMatch, suffixMatch, regexMatch, + presentMatch or rangeMatch must be set. returned: success type: complex contains: @@ -2017,9 +2017,9 @@ pathMatchers: description: - 'Specifies how individual filterLabel matches within the list 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.' - - "- MATCH_ALL: All filterLabels must have matching labels in the + - "* MATCH_ALL: All filterLabels must have matching labels in the provided metadata." returned: success type: str @@ -2261,26 +2261,26 @@ pathMatchers: retryConditions: description: - '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 does not respond at all, example: disconnects, 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." - - "- 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." - - "- retriable-4xx: Loadbalancer will retry for retriable 4xx response + - "* retriable-4xx: Loadbalancer will retry for retriable 4xx response codes." - 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 type indicates that it is safe to retry." - - "- cancelled: Loadbalancer will retry if the gRPC status code - in the response header is set to cancelled - deadline-exceeded: + - "* cancelled: Loadbalancer will retry if the gRPC status code + 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 + 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 + to resource-exhausted * unavailable: Loadbalancer will retry if the gRPC status code in the response header is set to unavailable ." returned: success diff --git a/plugins/modules/gcp_compute_region_url_map_info.py b/plugins/modules/gcp_compute_region_url_map_info.py index 09ab7b0..d9e9754 100644 --- a/plugins/modules/gcp_compute_region_url_map_info.py +++ b/plugins/modules/gcp_compute_region_url_map_info.py @@ -386,9 +386,9 @@ resources: - The header value must be an integer and its value must be in the range specified in rangeMatch. If the header does not contain 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 not match. - -3someString will not match. - Only one of exactMatch, prefixMatch, suffixMatch, regexMatch, + example 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, prefixMatch, suffixMatch, regexMatch, presentMatch or rangeMatch must be set. returned: success type: complex @@ -471,10 +471,10 @@ resources: description: - 'Specifies how individual filterLabel matches within the list 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 metadata.' - - "- MATCH_ALL: All filterLabels must have matching labels in + - "* MATCH_ALL: All filterLabels must have matching labels in the provided metadata." returned: success type: str @@ -724,27 +724,27 @@ resources: retryConditions: description: - '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, or if the backend service does not respond at all, example: disconnects, 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." - - "- 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." - - "- retriable-4xx: Loadbalancer will retry for retriable 4xx + - "* retriable-4xx: Loadbalancer will retry for retriable 4xx response codes." - 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. This reset type indicates that it is safe to retry." - - "- cancelled: Loadbalancer will retry if the gRPC status code - in the response header is set to cancelled - deadline-exceeded: + - "* cancelled: Loadbalancer will retry if the gRPC status code + 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 + 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 + is set to resource-exhausted * unavailable: Loadbalancer will retry if the gRPC status code in the response header is set to unavailable ." returned: success diff --git a/plugins/modules/gcp_compute_target_pool.py b/plugins/modules/gcp_compute_target_pool.py index 06dadcd..ac52bc4 100644 --- a/plugins/modules/gcp_compute_target_pool.py +++ b/plugins/modules/gcp_compute_target_pool.py @@ -119,11 +119,11 @@ options: type: str session_affinity: 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.' - - "- 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." - - "- 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." - 'Some valid choices include: "NONE", "CLIENT_IP", "CLIENT_IP_PROTO"' required: false @@ -269,11 +269,11 @@ name: type: str sessionAffinity: 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.' - - "- 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." - - "- 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." returned: success type: str diff --git a/plugins/modules/gcp_compute_target_pool_info.py b/plugins/modules/gcp_compute_target_pool_info.py index c19532a..1bc4996 100644 --- a/plugins/modules/gcp_compute_target_pool_info.py +++ b/plugins/modules/gcp_compute_target_pool_info.py @@ -190,11 +190,11 @@ resources: type: str sessionAffinity: 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.' - - "- 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." - - "- 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." returned: success type: str diff --git a/plugins/modules/gcp_compute_url_map.py b/plugins/modules/gcp_compute_url_map.py index a597e3d..2e04570 100644 --- a/plugins/modules/gcp_compute_url_map.py +++ b/plugins/modules/gcp_compute_url_map.py @@ -529,26 +529,26 @@ options: retry_conditions: description: - '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 does not respond at all, example: disconnects, 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." - - "- 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." - - "- retriable-4xx: Loadbalancer will retry for retriable 4xx + - "* retriable-4xx: Loadbalancer will retry for retriable 4xx response codes." - 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 type indicates that it is safe to retry." - - "- cancelled: Loadbalancer will retry if the gRPC status code - in the response header is set to cancelled - deadline-exceeded: + - "* cancelled: Loadbalancer will retry if the gRPC status code + 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 + 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 + set to resource-exhausted * unavailable: Loadbalancer will retry if the gRPC status code in the response header is set to unavailable ." elements: str @@ -1324,26 +1324,26 @@ options: retry_conditions: description: - '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 does not respond at all, example: disconnects, 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." - - "- 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." - - "- retriable-4xx: Loadbalancer will retry for retriable 4xx + - "* retriable-4xx: Loadbalancer will retry for retriable 4xx response codes." - 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 type indicates that it is safe to retry." - - "- cancelled: Loadbalancer will retry if the gRPC status code - in the response header is set to cancelled - deadline-exceeded: + - "* cancelled: Loadbalancer will retry if the gRPC status code + 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 + 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 + set to resource-exhausted * unavailable: Loadbalancer will retry if the gRPC status code in the response header is set to unavailable ." elements: str @@ -1827,27 +1827,27 @@ options: retry_conditions: description: - '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 does not respond at all, example: disconnects, reset, read timeout, - connection failure, and refused streams.' - - 'gateway-error: Similar to 5xx, but only applies to response codes - 502, 503 or 504.' - - 'connect-failure: Loadbalancer will retry on failures connecting - to backend services, for example due to connection timeouts.' - - 'retriable-4xx: Loadbalancer will retry for retriable 4xx response - codes.' + * connection failure, and refused streams.' + - "* gateway-error: Similar to 5xx, but only applies to response codes + 502, 503 or 504." + - "* connect-failure: Loadbalancer will retry on failures connecting + to backend services, for example due to connection timeouts." + - "* retriable-4xx: Loadbalancer will retry for retriable 4xx response + codes." - Currently the only retriable error supported is 409. - - refused-stream:Loadbalancer will retry if the backend service resets - the stream with a REFUSED_STREAM error code. + - "* refused-stream:Loadbalancer will retry if the backend service + resets the stream with a REFUSED_STREAM error code." - This reset type indicates that it is safe to retry. - - 'cancelled: Loadbalancer will retry if the gRPC status code in the - response header is set to cancelled deadline-exceeded: Loadbalancer + - "* cancelled: Loadbalancer will retry if the gRPC status code 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 + 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 unavailable .' + * unavailable: Loadbalancer will retry if the gRPC status code in + the response header is set to unavailable ." elements: str required: false type: list @@ -2324,26 +2324,27 @@ options: retry_conditions: description: - 'Specfies one or more conditions when this retry rule applies. Valid - values 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 at all, example: disconnects, reset, read timeout, connection - failure, and refused streams.' - - 'gateway-error: Similar to 5xx, but only applies to response codes 502, - 503 or 504.' - - 'connect-failure: Loadbalancer will retry on failures connecting to - backend services, for example due to connection timeouts.' - - 'retriable-4xx: Loadbalancer will retry for retriable 4xx response codes.' + values 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 at all, example: disconnects, reset, read timeout, + * connection failure, and refused streams.' + - "* gateway-error: Similar to 5xx, but only applies to response codes + 502, 503 or 504." + - "* connect-failure: Loadbalancer will retry on failures connecting to + backend services, for example due to connection timeouts." + - "* retriable-4xx: Loadbalancer will retry for retriable 4xx response + codes." - Currently the only retriable error supported is 409. - - refused-stream:Loadbalancer will retry if the backend service resets - the stream with a REFUSED_STREAM error code. + - "* refused-stream:Loadbalancer will retry if the backend service resets + the stream with a REFUSED_STREAM error code." - This reset type indicates that it is safe to retry. - - 'cancelled: Loadbalancer will retry if the gRPC status code 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 to resource-exhausted unavailable: Loadbalancer + - "* cancelled: Loadbalancer will retry if the gRPC status code 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 - 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 required: false type: list @@ -3086,26 +3087,26 @@ pathMatchers: retryConditions: description: - '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 does not respond at all, example: disconnects, 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." - - "- 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." - - "- retriable-4xx: Loadbalancer will retry for retriable 4xx response + - "* retriable-4xx: Loadbalancer will retry for retriable 4xx response codes." - 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 type indicates that it is safe to retry." - - "- cancelled: Loadbalancer will retry if the gRPC status code - in the response header is set to cancelled - deadline-exceeded: + - "* cancelled: Loadbalancer will retry if the gRPC status code + 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 + 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 + to resource-exhausted * unavailable: Loadbalancer will retry if the gRPC status code in the response header is set to unavailable ." returned: success @@ -3825,26 +3826,26 @@ pathMatchers: retryConditions: description: - '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 does not respond at all, example: disconnects, 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." - - "- 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." - - "- retriable-4xx: Loadbalancer will retry for retriable 4xx response + - "* retriable-4xx: Loadbalancer will retry for retriable 4xx response codes." - 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 type indicates that it is safe to retry." - - "- cancelled: Loadbalancer will retry if the gRPC status code - in the response header is set to cancelled - deadline-exceeded: + - "* cancelled: Loadbalancer will retry if the gRPC status code + 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 + 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 + to resource-exhausted * unavailable: Loadbalancer will retry if the gRPC status code in the response header is set to unavailable ." returned: success @@ -4292,27 +4293,27 @@ pathMatchers: retryConditions: description: - '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 does not respond at all, example: disconnects, reset, read timeout, - connection failure, and refused streams.' - - 'gateway-error: Similar to 5xx, but only applies to response codes - 502, 503 or 504.' - - 'connect-failure: Loadbalancer will retry on failures connecting to - backend services, for example due to connection timeouts.' - - 'retriable-4xx: Loadbalancer will retry for retriable 4xx response - codes.' + * connection failure, and refused streams.' + - "* gateway-error: Similar to 5xx, but only applies to response codes + 502, 503 or 504." + - "* connect-failure: Loadbalancer will retry on failures connecting + to backend services, for example due to connection timeouts." + - "* retriable-4xx: Loadbalancer will retry for retriable 4xx response + codes." - Currently the only retriable error supported is 409. - - refused-stream:Loadbalancer will retry if the backend service resets - the stream with a REFUSED_STREAM error code. + - "* refused-stream:Loadbalancer will retry if the backend service resets + the stream with a REFUSED_STREAM error code." - This reset type indicates that it is safe to retry. - - 'cancelled: Loadbalancer will retry if the gRPC status code in the - response header is set to cancelled deadline-exceeded: Loadbalancer + - "* cancelled: Loadbalancer will retry if the gRPC status code 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 to resource-exhausted - unavailable: Loadbalancer 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 ." returned: success type: list numRetries: @@ -4748,26 +4749,26 @@ defaultRouteAction: retryConditions: description: - '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 - at all, example: disconnects, reset, read timeout, connection failure, + at all, example: disconnects, reset, read timeout, * connection failure, and refused streams.' - - 'gateway-error: Similar to 5xx, but only applies to response codes 502, - 503 or 504.' - - 'connect-failure: Loadbalancer will retry on failures connecting to backend - services, for example due to connection timeouts.' - - 'retriable-4xx: Loadbalancer will retry for retriable 4xx response codes.' + - "* gateway-error: Similar to 5xx, but only applies to response codes 502, + 503 or 504." + - "* connect-failure: Loadbalancer will retry on failures connecting to + backend services, for example due to connection timeouts." + - "* retriable-4xx: Loadbalancer will retry for retriable 4xx response codes." - Currently the only retriable error supported is 409. - - refused-stream:Loadbalancer will retry if the backend service resets the - stream with a REFUSED_STREAM error code. + - "* refused-stream:Loadbalancer will retry if the backend service resets + the stream with a REFUSED_STREAM error code." - This reset type indicates that it is safe to retry. - - 'cancelled: Loadbalancer will retry if the gRPC status code in the response - header is set to cancelled deadline-exceeded: Loadbalancer will retry + - "* cancelled: Loadbalancer will retry if the gRPC status code 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 to resource-exhausted unavailable: Loadbalancer + * 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 - .' + ." returned: success type: list numRetries: diff --git a/plugins/modules/gcp_compute_url_map_info.py b/plugins/modules/gcp_compute_url_map_info.py index 69df04d..3de013b 100644 --- a/plugins/modules/gcp_compute_url_map_info.py +++ b/plugins/modules/gcp_compute_url_map_info.py @@ -576,27 +576,27 @@ resources: retryConditions: description: - '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, or if the backend service does not respond at all, example: disconnects, 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." - - "- 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." - - "- retriable-4xx: Loadbalancer will retry for retriable 4xx + - "* retriable-4xx: Loadbalancer will retry for retriable 4xx response codes." - 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. This reset type indicates that it is safe to retry." - - "- cancelled: Loadbalancer will retry if the gRPC status code - in the response header is set to cancelled - deadline-exceeded: + - "* cancelled: Loadbalancer will retry if the gRPC status code + 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 + 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 + is set to resource-exhausted * unavailable: Loadbalancer will retry if the gRPC status code in the response header is set to unavailable ." returned: success @@ -1331,27 +1331,27 @@ resources: retryConditions: description: - '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, or if the backend service does not respond at all, example: disconnects, 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." - - "- 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." - - "- retriable-4xx: Loadbalancer will retry for retriable 4xx + - "* retriable-4xx: Loadbalancer will retry for retriable 4xx response codes." - 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. This reset type indicates that it is safe to retry." - - "- cancelled: Loadbalancer will retry if the gRPC status code - in the response header is set to cancelled - deadline-exceeded: + - "* cancelled: Loadbalancer will retry if the gRPC status code + 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 + 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 + is set to resource-exhausted * unavailable: Loadbalancer will retry if the gRPC status code in the response header is set to unavailable ." returned: success @@ -1806,27 +1806,28 @@ resources: retryConditions: description: - 'Specfies one or more conditions when this retry rule applies. - Valid values 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 at all, example: disconnects, - reset, read timeout, connection failure, and refused streams.' - - 'gateway-error: Similar to 5xx, but only applies to response codes - 502, 503 or 504.' - - 'connect-failure: Loadbalancer will retry on failures connecting - to backend services, for example due to connection timeouts.' - - 'retriable-4xx: Loadbalancer will retry for retriable 4xx response - codes.' + Valid values 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 at all, example: disconnects, + reset, read timeout, * connection failure, and refused streams.' + - "* gateway-error: Similar to 5xx, but only applies to response + codes 502, 503 or 504." + - "* connect-failure: Loadbalancer will retry on failures connecting + to backend services, for example due to connection timeouts." + - "* retriable-4xx: Loadbalancer will retry for retriable 4xx response + codes." - Currently the only retriable error supported is 409. - - refused-stream:Loadbalancer will retry if the backend service - resets the stream with a REFUSED_STREAM error code. + - "* refused-stream:Loadbalancer will retry if the backend service + resets the stream with a REFUSED_STREAM error code." - This reset type indicates that it is safe to retry. - - 'cancelled: Loadbalancer will retry if the gRPC status code in - the response header is set to cancelled deadline-exceeded: Loadbalancer + - "* cancelled: Loadbalancer will retry if the gRPC status code + 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 - 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 unavailable .' + to resource-exhausted * unavailable: Loadbalancer will retry if + the gRPC status code in the response header is set to unavailable + ." returned: success type: list numRetries: @@ -2268,27 +2269,27 @@ resources: retryConditions: description: - '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 does not respond at all, example: disconnects, reset, read timeout, - connection failure, and refused streams.' - - 'gateway-error: Similar to 5xx, but only applies to response codes - 502, 503 or 504.' - - 'connect-failure: Loadbalancer will retry on failures connecting to - backend services, for example due to connection timeouts.' - - 'retriable-4xx: Loadbalancer will retry for retriable 4xx response - codes.' + * connection failure, and refused streams.' + - "* gateway-error: Similar to 5xx, but only applies to response codes + 502, 503 or 504." + - "* connect-failure: Loadbalancer will retry on failures connecting + to backend services, for example due to connection timeouts." + - "* retriable-4xx: Loadbalancer will retry for retriable 4xx response + codes." - Currently the only retriable error supported is 409. - - refused-stream:Loadbalancer will retry if the backend service resets - the stream with a REFUSED_STREAM error code. + - "* refused-stream:Loadbalancer will retry if the backend service resets + the stream with a REFUSED_STREAM error code." - This reset type indicates that it is safe to retry. - - 'cancelled: Loadbalancer will retry if the gRPC status code in the - response header is set to cancelled deadline-exceeded: Loadbalancer + - "* cancelled: Loadbalancer will retry if the gRPC status code 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 to resource-exhausted - unavailable: Loadbalancer 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 ." returned: success type: list numRetries: