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

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
commit 3af242d21d
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
16 changed files with 285 additions and 282 deletions
Download patch file Download diff file Expand all files Collapse all files

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
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