commit c2cd326ef156fc2652d23e4c64fd06e2d66e3a80
author yoshi-code-bot <70984784+yoshi-code-bot@users.noreply.github.com> Sun May 16 02:16:04 2021 -0700
committer GitHub <noreply@github.com> Sun May 16 09:16:04 2021 +0000
tree 29b1798378bc5781c0235bfe8d710d9629d3104d
parent befabc36817ff986c80ff64299ec28d690c5d5c6

chore: Update discovery artifacts (#1356)

## Deleted keys were detected in the following stable discovery artifacts:
compute v1 https://github.com/googleapis/google-api-python-client/commit/685c19d4b5262d27a2b1016e01186188afe610fd
genomics v1 https://github.com/googleapis/google-api-python-client/commit/d0e6cc48df2d0a00d91ce6fbab83aa82146f3573

## Deleted keys were detected in the following pre-stable discovery artifacts:
compute alpha https://github.com/googleapis/google-api-python-client/commit/685c19d4b5262d27a2b1016e01186188afe610fd
compute beta https://github.com/googleapis/google-api-python-client/commit/685c19d4b5262d27a2b1016e01186188afe610fd
genomics v2alpha1 https://github.com/googleapis/google-api-python-client/commit/d0e6cc48df2d0a00d91ce6fbab83aa82146f3573

## Discovery Artifact Change Summary:
feat(analyticsadmin): update the api https://github.com/googleapis/google-api-python-client/commit/9648bae09873a132e7b4627096c153043911be6e
feat(artifactregistry): update the api https://github.com/googleapis/google-api-python-client/commit/7dd722fe8b0ae822f4847219c442aa67a1aae7fd
feat(assuredworkloads): update the api https://github.com/googleapis/google-api-python-client/commit/9b84ffce415133e860cc55bfbd3b9c15c3d46a24
feat(cloudasset): update the api https://github.com/googleapis/google-api-python-client/commit/a8228db5ef31724493f0f62bf8062aca9adc44aa
feat(cloudbuild): update the api https://github.com/googleapis/google-api-python-client/commit/c9d8208c0f9579d958224566af369b809e13016a
feat(compute): update the api https://github.com/googleapis/google-api-python-client/commit/685c19d4b5262d27a2b1016e01186188afe610fd
feat(container): update the api https://github.com/googleapis/google-api-python-client/commit/c5cd244f996b1dfb605ef28eb22f8b0e76bffa1b
feat(dialogflow): update the api https://github.com/googleapis/google-api-python-client/commit/0c6b31fd2deb75ca1c023fed36903b638f5e74f8
feat(documentai): update the api https://github.com/googleapis/google-api-python-client/commit/6dcec9fd8c0f803d37b4c8355870208e5a8c61ce
feat(drive): update the api https://github.com/googleapis/google-api-python-client/commit/8788823461610f31eebd655915e07def9690da48
feat(genomics): update the api https://github.com/googleapis/google-api-python-client/commit/d0e6cc48df2d0a00d91ce6fbab83aa82146f3573
feat(logging): update the api https://github.com/googleapis/google-api-python-client/commit/7f5fa161fd3db9ca6f2df23f5c8bd41ba01e9b9c
feat(privateca): update the api https://github.com/googleapis/google-api-python-client/commit/0a5c31d74f788444640c174c413b12d494a00f1a
feat(pubsublite): update the api https://github.com/googleapis/google-api-python-client/commit/dd67e9b117fdc8d0d0ecff6ade657003a95c12f7
feat(recommender): update the api https://github.com/googleapis/google-api-python-client/commit/4b261d97bea2a8bc042a274c2d904be09da2d82c

docs/dyn/compute_alpha.urlMaps.html

diff --git a/docs/dyn/compute_alpha.urlMaps.html b/docs/dyn/compute_alpha.urlMaps.html
index 71d1ef9..bb5ec49 100644
--- a/docs/dyn/compute_alpha.urlMaps.html
+++ b/docs/dyn/compute_alpha.urlMaps.html
@@ -193,10 +193,10 @@
             },
             "faultInjectionPolicy": { # The specification for fault injection introduced into traffic to test the resiliency of clients to backend service failure. As part of fault injection, when clients send requests to a backend service, delays can be introduced by Loadbalancer on a percentage of requests before sending those request to the backend service. Similarly requests from clients can be aborted by the Loadbalancer for a percentage of requests. # The specification for fault injection introduced into traffic to test the resiliency of clients to backend service failure. As part of fault injection, when clients send requests to a backend service, delays can be introduced by Loadbalancer on a percentage of requests before sending those request to the backend service. Similarly requests from clients can be aborted by the Loadbalancer for a percentage of requests.
                 # timeout and retry_policy will be ignored by clients that are configured with a fault_injection_policy.
-                # Not supported when the URL map is bound to target gRPC proxy that has validateForProxyless field set to true.
               "abort": { # Specification for how requests are aborted as part of fault injection. # The specification for how client requests are aborted as part of fault injection.
                 "httpStatus": 42, # The HTTP status code used to abort the request.
                     # The value must be between 200 and 599 inclusive.
+                    # For gRPC protocol, the gRPC status code is mapped to HTTP status code according to this  mapping table. HTTP status 200 is mapped to gRPC status UNKNOWN. Injecting an OK status is currently not supported by Traffic Director.
                 "percentage": 3.14, # The percentage of traffic (connections/operations/requests) which will be aborted as part of fault injection.
                     # The value must be between 0.0 and 100.0 inclusive.
               },
@@ -227,7 +227,7 @@
                 "nanos": 42, # Span of time that's a fraction of a second at nanosecond resolution. Durations less than one second are represented with a 0 `seconds` field and a positive `nanos` field. Must be from 0 to 999,999,999 inclusive.
                 "seconds": "A String", # Span of time at a resolution of a second. Must be from 0 to 315,576,000,000 inclusive. Note: these bounds are computed from: 60 sec/min * 60 min/hr * 24 hr/day * 365.25 days/year * 10000 years
               },
-              "retryConditions": [ # Specfies one or more conditions when this retry rule applies. Valid values are:
+              "retryConditions": [ # Specifies 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.
                   # -
@@ -394,10 +394,10 @@
                 },
                 "faultInjectionPolicy": { # The specification for fault injection introduced into traffic to test the resiliency of clients to backend service failure. As part of fault injection, when clients send requests to a backend service, delays can be introduced by Loadbalancer on a percentage of requests before sending those request to the backend service. Similarly requests from clients can be aborted by the Loadbalancer for a percentage of requests. # The specification for fault injection introduced into traffic to test the resiliency of clients to backend service failure. As part of fault injection, when clients send requests to a backend service, delays can be introduced by Loadbalancer on a percentage of requests before sending those request to the backend service. Similarly requests from clients can be aborted by the Loadbalancer for a percentage of requests.
                     # timeout and retry_policy will be ignored by clients that are configured with a fault_injection_policy.
-                    # Not supported when the URL map is bound to target gRPC proxy that has validateForProxyless field set to true.
                   "abort": { # Specification for how requests are aborted as part of fault injection. # The specification for how client requests are aborted as part of fault injection.
                     "httpStatus": 42, # The HTTP status code used to abort the request.
                         # The value must be between 200 and 599 inclusive.
+                        # For gRPC protocol, the gRPC status code is mapped to HTTP status code according to this  mapping table. HTTP status 200 is mapped to gRPC status UNKNOWN. Injecting an OK status is currently not supported by Traffic Director.
                     "percentage": 3.14, # The percentage of traffic (connections/operations/requests) which will be aborted as part of fault injection.
                         # The value must be between 0.0 and 100.0 inclusive.
                   },
@@ -428,7 +428,7 @@
                     "nanos": 42, # Span of time that's a fraction of a second at nanosecond resolution. Durations less than one second are represented with a 0 `seconds` field and a positive `nanos` field. Must be from 0 to 999,999,999 inclusive.
                     "seconds": "A String", # Span of time at a resolution of a second. Must be from 0 to 315,576,000,000 inclusive. Note: these bounds are computed from: 60 sec/min * 60 min/hr * 24 hr/day * 365.25 days/year * 10000 years
                   },
-                  "retryConditions": [ # Specfies one or more conditions when this retry rule applies. Valid values are:
+                  "retryConditions": [ # Specifies 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.
                       # -
@@ -590,10 +590,10 @@
                     },
                     "faultInjectionPolicy": { # The specification for fault injection introduced into traffic to test the resiliency of clients to backend service failure. As part of fault injection, when clients send requests to a backend service, delays can be introduced by Loadbalancer on a percentage of requests before sending those request to the backend service. Similarly requests from clients can be aborted by the Loadbalancer for a percentage of requests. # The specification for fault injection introduced into traffic to test the resiliency of clients to backend service failure. As part of fault injection, when clients send requests to a backend service, delays can be introduced by Loadbalancer on a percentage of requests before sending those request to the backend service. Similarly requests from clients can be aborted by the Loadbalancer for a percentage of requests.
                         # timeout and retry_policy will be ignored by clients that are configured with a fault_injection_policy.
-                        # Not supported when the URL map is bound to target gRPC proxy that has validateForProxyless field set to true.
                       "abort": { # Specification for how requests are aborted as part of fault injection. # The specification for how client requests are aborted as part of fault injection.
                         "httpStatus": 42, # The HTTP status code used to abort the request.
                             # The value must be between 200 and 599 inclusive.
+                            # For gRPC protocol, the gRPC status code is mapped to HTTP status code according to this  mapping table. HTTP status 200 is mapped to gRPC status UNKNOWN. Injecting an OK status is currently not supported by Traffic Director.
                         "percentage": 3.14, # The percentage of traffic (connections/operations/requests) which will be aborted as part of fault injection.
                             # The value must be between 0.0 and 100.0 inclusive.
                       },
@@ -624,7 +624,7 @@
                         "nanos": 42, # Span of time that's a fraction of a second at nanosecond resolution. Durations less than one second are represented with a 0 `seconds` field and a positive `nanos` field. Must be from 0 to 999,999,999 inclusive.
                         "seconds": "A String", # Span of time at a resolution of a second. Must be from 0 to 315,576,000,000 inclusive. Note: these bounds are computed from: 60 sec/min * 60 min/hr * 24 hr/day * 365.25 days/year * 10000 years
                       },
-                      "retryConditions": [ # Specfies one or more conditions when this retry rule applies. Valid values are:
+                      "retryConditions": [ # Specifies 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.
                           # -
@@ -884,10 +884,10 @@
                     },
                     "faultInjectionPolicy": { # The specification for fault injection introduced into traffic to test the resiliency of clients to backend service failure. As part of fault injection, when clients send requests to a backend service, delays can be introduced by Loadbalancer on a percentage of requests before sending those request to the backend service. Similarly requests from clients can be aborted by the Loadbalancer for a percentage of requests. # The specification for fault injection introduced into traffic to test the resiliency of clients to backend service failure. As part of fault injection, when clients send requests to a backend service, delays can be introduced by Loadbalancer on a percentage of requests before sending those request to the backend service. Similarly requests from clients can be aborted by the Loadbalancer for a percentage of requests.
                         # timeout and retry_policy will be ignored by clients that are configured with a fault_injection_policy.
-                        # Not supported when the URL map is bound to target gRPC proxy that has validateForProxyless field set to true.
                       "abort": { # Specification for how requests are aborted as part of fault injection. # The specification for how client requests are aborted as part of fault injection.
                         "httpStatus": 42, # The HTTP status code used to abort the request.
                             # The value must be between 200 and 599 inclusive.
+                            # For gRPC protocol, the gRPC status code is mapped to HTTP status code according to this  mapping table. HTTP status 200 is mapped to gRPC status UNKNOWN. Injecting an OK status is currently not supported by Traffic Director.
                         "percentage": 3.14, # The percentage of traffic (connections/operations/requests) which will be aborted as part of fault injection.
                             # The value must be between 0.0 and 100.0 inclusive.
                       },
@@ -918,7 +918,7 @@
                         "nanos": 42, # Span of time that's a fraction of a second at nanosecond resolution. Durations less than one second are represented with a 0 `seconds` field and a positive `nanos` field. Must be from 0 to 999,999,999 inclusive.
                         "seconds": "A String", # Span of time at a resolution of a second. Must be from 0 to 315,576,000,000 inclusive. Note: these bounds are computed from: 60 sec/min * 60 min/hr * 24 hr/day * 365.25 days/year * 10000 years
                       },
-                      "retryConditions": [ # Specfies one or more conditions when this retry rule applies. Valid values are:
+                      "retryConditions": [ # Specifies 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.
                           # -
@@ -1230,10 +1230,10 @@
     },
     "faultInjectionPolicy": { # The specification for fault injection introduced into traffic to test the resiliency of clients to backend service failure. As part of fault injection, when clients send requests to a backend service, delays can be introduced by Loadbalancer on a percentage of requests before sending those request to the backend service. Similarly requests from clients can be aborted by the Loadbalancer for a percentage of requests. # The specification for fault injection introduced into traffic to test the resiliency of clients to backend service failure. As part of fault injection, when clients send requests to a backend service, delays can be introduced by Loadbalancer on a percentage of requests before sending those request to the backend service. Similarly requests from clients can be aborted by the Loadbalancer for a percentage of requests.
         # timeout and retry_policy will be ignored by clients that are configured with a fault_injection_policy.
-        # Not supported when the URL map is bound to target gRPC proxy that has validateForProxyless field set to true.
       "abort": { # Specification for how requests are aborted as part of fault injection. # The specification for how client requests are aborted as part of fault injection.
         "httpStatus": 42, # The HTTP status code used to abort the request.
             # The value must be between 200 and 599 inclusive.
+            # For gRPC protocol, the gRPC status code is mapped to HTTP status code according to this  mapping table. HTTP status 200 is mapped to gRPC status UNKNOWN. Injecting an OK status is currently not supported by Traffic Director.
         "percentage": 3.14, # The percentage of traffic (connections/operations/requests) which will be aborted as part of fault injection.
             # The value must be between 0.0 and 100.0 inclusive.
       },
@@ -1264,7 +1264,7 @@
         "nanos": 42, # Span of time that's a fraction of a second at nanosecond resolution. Durations less than one second are represented with a 0 `seconds` field and a positive `nanos` field. Must be from 0 to 999,999,999 inclusive.
         "seconds": "A String", # Span of time at a resolution of a second. Must be from 0 to 315,576,000,000 inclusive. Note: these bounds are computed from: 60 sec/min * 60 min/hr * 24 hr/day * 365.25 days/year * 10000 years
       },
-      "retryConditions": [ # Specfies one or more conditions when this retry rule applies. Valid values are:
+      "retryConditions": [ # Specifies 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.
           # -
@@ -1431,10 +1431,10 @@
         },
         "faultInjectionPolicy": { # The specification for fault injection introduced into traffic to test the resiliency of clients to backend service failure. As part of fault injection, when clients send requests to a backend service, delays can be introduced by Loadbalancer on a percentage of requests before sending those request to the backend service. Similarly requests from clients can be aborted by the Loadbalancer for a percentage of requests. # The specification for fault injection introduced into traffic to test the resiliency of clients to backend service failure. As part of fault injection, when clients send requests to a backend service, delays can be introduced by Loadbalancer on a percentage of requests before sending those request to the backend service. Similarly requests from clients can be aborted by the Loadbalancer for a percentage of requests.
             # timeout and retry_policy will be ignored by clients that are configured with a fault_injection_policy.
-            # Not supported when the URL map is bound to target gRPC proxy that has validateForProxyless field set to true.
           "abort": { # Specification for how requests are aborted as part of fault injection. # The specification for how client requests are aborted as part of fault injection.
             "httpStatus": 42, # The HTTP status code used to abort the request.
                 # The value must be between 200 and 599 inclusive.
+                # For gRPC protocol, the gRPC status code is mapped to HTTP status code according to this  mapping table. HTTP status 200 is mapped to gRPC status UNKNOWN. Injecting an OK status is currently not supported by Traffic Director.
             "percentage": 3.14, # The percentage of traffic (connections/operations/requests) which will be aborted as part of fault injection.
                 # The value must be between 0.0 and 100.0 inclusive.
           },
@@ -1465,7 +1465,7 @@
             "nanos": 42, # Span of time that's a fraction of a second at nanosecond resolution. Durations less than one second are represented with a 0 `seconds` field and a positive `nanos` field. Must be from 0 to 999,999,999 inclusive.
             "seconds": "A String", # Span of time at a resolution of a second. Must be from 0 to 315,576,000,000 inclusive. Note: these bounds are computed from: 60 sec/min * 60 min/hr * 24 hr/day * 365.25 days/year * 10000 years
           },
-          "retryConditions": [ # Specfies one or more conditions when this retry rule applies. Valid values are:
+          "retryConditions": [ # Specifies 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.
               # -
@@ -1627,10 +1627,10 @@
             },
             "faultInjectionPolicy": { # The specification for fault injection introduced into traffic to test the resiliency of clients to backend service failure. As part of fault injection, when clients send requests to a backend service, delays can be introduced by Loadbalancer on a percentage of requests before sending those request to the backend service. Similarly requests from clients can be aborted by the Loadbalancer for a percentage of requests. # The specification for fault injection introduced into traffic to test the resiliency of clients to backend service failure. As part of fault injection, when clients send requests to a backend service, delays can be introduced by Loadbalancer on a percentage of requests before sending those request to the backend service. Similarly requests from clients can be aborted by the Loadbalancer for a percentage of requests.
                 # timeout and retry_policy will be ignored by clients that are configured with a fault_injection_policy.
-                # Not supported when the URL map is bound to target gRPC proxy that has validateForProxyless field set to true.
               "abort": { # Specification for how requests are aborted as part of fault injection. # The specification for how client requests are aborted as part of fault injection.
                 "httpStatus": 42, # The HTTP status code used to abort the request.
                     # The value must be between 200 and 599 inclusive.
+                    # For gRPC protocol, the gRPC status code is mapped to HTTP status code according to this  mapping table. HTTP status 200 is mapped to gRPC status UNKNOWN. Injecting an OK status is currently not supported by Traffic Director.
                 "percentage": 3.14, # The percentage of traffic (connections/operations/requests) which will be aborted as part of fault injection.
                     # The value must be between 0.0 and 100.0 inclusive.
               },
@@ -1661,7 +1661,7 @@
                 "nanos": 42, # Span of time that's a fraction of a second at nanosecond resolution. Durations less than one second are represented with a 0 `seconds` field and a positive `nanos` field. Must be from 0 to 999,999,999 inclusive.
                 "seconds": "A String", # Span of time at a resolution of a second. Must be from 0 to 315,576,000,000 inclusive. Note: these bounds are computed from: 60 sec/min * 60 min/hr * 24 hr/day * 365.25 days/year * 10000 years
               },
-              "retryConditions": [ # Specfies one or more conditions when this retry rule applies. Valid values are:
+              "retryConditions": [ # Specifies 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.
                   # -
@@ -1921,10 +1921,10 @@
             },
             "faultInjectionPolicy": { # The specification for fault injection introduced into traffic to test the resiliency of clients to backend service failure. As part of fault injection, when clients send requests to a backend service, delays can be introduced by Loadbalancer on a percentage of requests before sending those request to the backend service. Similarly requests from clients can be aborted by the Loadbalancer for a percentage of requests. # The specification for fault injection introduced into traffic to test the resiliency of clients to backend service failure. As part of fault injection, when clients send requests to a backend service, delays can be introduced by Loadbalancer on a percentage of requests before sending those request to the backend service. Similarly requests from clients can be aborted by the Loadbalancer for a percentage of requests.
                 # timeout and retry_policy will be ignored by clients that are configured with a fault_injection_policy.
-                # Not supported when the URL map is bound to target gRPC proxy that has validateForProxyless field set to true.
               "abort": { # Specification for how requests are aborted as part of fault injection. # The specification for how client requests are aborted as part of fault injection.
                 "httpStatus": 42, # The HTTP status code used to abort the request.
                     # The value must be between 200 and 599 inclusive.
+                    # For gRPC protocol, the gRPC status code is mapped to HTTP status code according to this  mapping table. HTTP status 200 is mapped to gRPC status UNKNOWN. Injecting an OK status is currently not supported by Traffic Director.
                 "percentage": 3.14, # The percentage of traffic (connections/operations/requests) which will be aborted as part of fault injection.
                     # The value must be between 0.0 and 100.0 inclusive.
               },
@@ -1955,7 +1955,7 @@
                 "nanos": 42, # Span of time that's a fraction of a second at nanosecond resolution. Durations less than one second are represented with a 0 `seconds` field and a positive `nanos` field. Must be from 0 to 999,999,999 inclusive.
                 "seconds": "A String", # Span of time at a resolution of a second. Must be from 0 to 315,576,000,000 inclusive. Note: these bounds are computed from: 60 sec/min * 60 min/hr * 24 hr/day * 365.25 days/year * 10000 years
               },
-              "retryConditions": [ # Specfies one or more conditions when this retry rule applies. Valid values are:
+              "retryConditions": [ # Specifies 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.
                   # -
@@ -2136,10 +2136,10 @@
     },
     "faultInjectionPolicy": { # The specification for fault injection introduced into traffic to test the resiliency of clients to backend service failure. As part of fault injection, when clients send requests to a backend service, delays can be introduced by Loadbalancer on a percentage of requests before sending those request to the backend service. Similarly requests from clients can be aborted by the Loadbalancer for a percentage of requests. # The specification for fault injection introduced into traffic to test the resiliency of clients to backend service failure. As part of fault injection, when clients send requests to a backend service, delays can be introduced by Loadbalancer on a percentage of requests before sending those request to the backend service. Similarly requests from clients can be aborted by the Loadbalancer for a percentage of requests.
         # timeout and retry_policy will be ignored by clients that are configured with a fault_injection_policy.
-        # Not supported when the URL map is bound to target gRPC proxy that has validateForProxyless field set to true.
       "abort": { # Specification for how requests are aborted as part of fault injection. # The specification for how client requests are aborted as part of fault injection.
         "httpStatus": 42, # The HTTP status code used to abort the request.
             # The value must be between 200 and 599 inclusive.
+            # For gRPC protocol, the gRPC status code is mapped to HTTP status code according to this  mapping table. HTTP status 200 is mapped to gRPC status UNKNOWN. Injecting an OK status is currently not supported by Traffic Director.
         "percentage": 3.14, # The percentage of traffic (connections/operations/requests) which will be aborted as part of fault injection.
             # The value must be between 0.0 and 100.0 inclusive.
       },
@@ -2170,7 +2170,7 @@
         "nanos": 42, # Span of time that's a fraction of a second at nanosecond resolution. Durations less than one second are represented with a 0 `seconds` field and a positive `nanos` field. Must be from 0 to 999,999,999 inclusive.
         "seconds": "A String", # Span of time at a resolution of a second. Must be from 0 to 315,576,000,000 inclusive. Note: these bounds are computed from: 60 sec/min * 60 min/hr * 24 hr/day * 365.25 days/year * 10000 years
       },
-      "retryConditions": [ # Specfies one or more conditions when this retry rule applies. Valid values are:
+      "retryConditions": [ # Specifies 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.
           # -
@@ -2337,10 +2337,10 @@
         },
         "faultInjectionPolicy": { # The specification for fault injection introduced into traffic to test the resiliency of clients to backend service failure. As part of fault injection, when clients send requests to a backend service, delays can be introduced by Loadbalancer on a percentage of requests before sending those request to the backend service. Similarly requests from clients can be aborted by the Loadbalancer for a percentage of requests. # The specification for fault injection introduced into traffic to test the resiliency of clients to backend service failure. As part of fault injection, when clients send requests to a backend service, delays can be introduced by Loadbalancer on a percentage of requests before sending those request to the backend service. Similarly requests from clients can be aborted by the Loadbalancer for a percentage of requests.
             # timeout and retry_policy will be ignored by clients that are configured with a fault_injection_policy.
-            # Not supported when the URL map is bound to target gRPC proxy that has validateForProxyless field set to true.
           "abort": { # Specification for how requests are aborted as part of fault injection. # The specification for how client requests are aborted as part of fault injection.
             "httpStatus": 42, # The HTTP status code used to abort the request.
                 # The value must be between 200 and 599 inclusive.
+                # For gRPC protocol, the gRPC status code is mapped to HTTP status code according to this  mapping table. HTTP status 200 is mapped to gRPC status UNKNOWN. Injecting an OK status is currently not supported by Traffic Director.
             "percentage": 3.14, # The percentage of traffic (connections/operations/requests) which will be aborted as part of fault injection.
                 # The value must be between 0.0 and 100.0 inclusive.
           },
@@ -2371,7 +2371,7 @@
             "nanos": 42, # Span of time that's a fraction of a second at nanosecond resolution. Durations less than one second are represented with a 0 `seconds` field and a positive `nanos` field. Must be from 0 to 999,999,999 inclusive.
             "seconds": "A String", # Span of time at a resolution of a second. Must be from 0 to 315,576,000,000 inclusive. Note: these bounds are computed from: 60 sec/min * 60 min/hr * 24 hr/day * 365.25 days/year * 10000 years
           },
-          "retryConditions": [ # Specfies one or more conditions when this retry rule applies. Valid values are:
+          "retryConditions": [ # Specifies 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.
               # -
@@ -2533,10 +2533,10 @@
             },
             "faultInjectionPolicy": { # The specification for fault injection introduced into traffic to test the resiliency of clients to backend service failure. As part of fault injection, when clients send requests to a backend service, delays can be introduced by Loadbalancer on a percentage of requests before sending those request to the backend service. Similarly requests from clients can be aborted by the Loadbalancer for a percentage of requests. # The specification for fault injection introduced into traffic to test the resiliency of clients to backend service failure. As part of fault injection, when clients send requests to a backend service, delays can be introduced by Loadbalancer on a percentage of requests before sending those request to the backend service. Similarly requests from clients can be aborted by the Loadbalancer for a percentage of requests.
                 # timeout and retry_policy will be ignored by clients that are configured with a fault_injection_policy.
-                # Not supported when the URL map is bound to target gRPC proxy that has validateForProxyless field set to true.
               "abort": { # Specification for how requests are aborted as part of fault injection. # The specification for how client requests are aborted as part of fault injection.
                 "httpStatus": 42, # The HTTP status code used to abort the request.
                     # The value must be between 200 and 599 inclusive.
+                    # For gRPC protocol, the gRPC status code is mapped to HTTP status code according to this  mapping table. HTTP status 200 is mapped to gRPC status UNKNOWN. Injecting an OK status is currently not supported by Traffic Director.
                 "percentage": 3.14, # The percentage of traffic (connections/operations/requests) which will be aborted as part of fault injection.
                     # The value must be between 0.0 and 100.0 inclusive.
               },
@@ -2567,7 +2567,7 @@
                 "nanos": 42, # Span of time that's a fraction of a second at nanosecond resolution. Durations less than one second are represented with a 0 `seconds` field and a positive `nanos` field. Must be from 0 to 999,999,999 inclusive.
                 "seconds": "A String", # Span of time at a resolution of a second. Must be from 0 to 315,576,000,000 inclusive. Note: these bounds are computed from: 60 sec/min * 60 min/hr * 24 hr/day * 365.25 days/year * 10000 years
               },
-              "retryConditions": [ # Specfies one or more conditions when this retry rule applies. Valid values are:
+              "retryConditions": [ # Specifies 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.
                   # -
@@ -2827,10 +2827,10 @@
             },
             "faultInjectionPolicy": { # The specification for fault injection introduced into traffic to test the resiliency of clients to backend service failure. As part of fault injection, when clients send requests to a backend service, delays can be introduced by Loadbalancer on a percentage of requests before sending those request to the backend service. Similarly requests from clients can be aborted by the Loadbalancer for a percentage of requests. # The specification for fault injection introduced into traffic to test the resiliency of clients to backend service failure. As part of fault injection, when clients send requests to a backend service, delays can be introduced by Loadbalancer on a percentage of requests before sending those request to the backend service. Similarly requests from clients can be aborted by the Loadbalancer for a percentage of requests.
                 # timeout and retry_policy will be ignored by clients that are configured with a fault_injection_policy.
-                # Not supported when the URL map is bound to target gRPC proxy that has validateForProxyless field set to true.
               "abort": { # Specification for how requests are aborted as part of fault injection. # The specification for how client requests are aborted as part of fault injection.
                 "httpStatus": 42, # The HTTP status code used to abort the request.
                     # The value must be between 200 and 599 inclusive.
+                    # For gRPC protocol, the gRPC status code is mapped to HTTP status code according to this  mapping table. HTTP status 200 is mapped to gRPC status UNKNOWN. Injecting an OK status is currently not supported by Traffic Director.
                 "percentage": 3.14, # The percentage of traffic (connections/operations/requests) which will be aborted as part of fault injection.
                     # The value must be between 0.0 and 100.0 inclusive.
               },
@@ -2861,7 +2861,7 @@
                 "nanos": 42, # Span of time that's a fraction of a second at nanosecond resolution. Durations less than one second are represented with a 0 `seconds` field and a positive `nanos` field. Must be from 0 to 999,999,999 inclusive.
                 "seconds": "A String", # Span of time at a resolution of a second. Must be from 0 to 315,576,000,000 inclusive. Note: these bounds are computed from: 60 sec/min * 60 min/hr * 24 hr/day * 365.25 days/year * 10000 years
               },
-              "retryConditions": [ # Specfies one or more conditions when this retry rule applies. Valid values are:
+              "retryConditions": [ # Specifies 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.
                   # -
@@ -3219,10 +3219,10 @@
         },
         "faultInjectionPolicy": { # The specification for fault injection introduced into traffic to test the resiliency of clients to backend service failure. As part of fault injection, when clients send requests to a backend service, delays can be introduced by Loadbalancer on a percentage of requests before sending those request to the backend service. Similarly requests from clients can be aborted by the Loadbalancer for a percentage of requests. # The specification for fault injection introduced into traffic to test the resiliency of clients to backend service failure. As part of fault injection, when clients send requests to a backend service, delays can be introduced by Loadbalancer on a percentage of requests before sending those request to the backend service. Similarly requests from clients can be aborted by the Loadbalancer for a percentage of requests.
             # timeout and retry_policy will be ignored by clients that are configured with a fault_injection_policy.
-            # Not supported when the URL map is bound to target gRPC proxy that has validateForProxyless field set to true.
           "abort": { # Specification for how requests are aborted as part of fault injection. # The specification for how client requests are aborted as part of fault injection.
             "httpStatus": 42, # The HTTP status code used to abort the request.
                 # The value must be between 200 and 599 inclusive.
+                # For gRPC protocol, the gRPC status code is mapped to HTTP status code according to this  mapping table. HTTP status 200 is mapped to gRPC status UNKNOWN. Injecting an OK status is currently not supported by Traffic Director.
             "percentage": 3.14, # The percentage of traffic (connections/operations/requests) which will be aborted as part of fault injection.
                 # The value must be between 0.0 and 100.0 inclusive.
           },
@@ -3253,7 +3253,7 @@
             "nanos": 42, # Span of time that's a fraction of a second at nanosecond resolution. Durations less than one second are represented with a 0 `seconds` field and a positive `nanos` field. Must be from 0 to 999,999,999 inclusive.
             "seconds": "A String", # Span of time at a resolution of a second. Must be from 0 to 315,576,000,000 inclusive. Note: these bounds are computed from: 60 sec/min * 60 min/hr * 24 hr/day * 365.25 days/year * 10000 years
           },
-          "retryConditions": [ # Specfies one or more conditions when this retry rule applies. Valid values are:
+          "retryConditions": [ # Specifies 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.
               # -
@@ -3420,10 +3420,10 @@
             },
             "faultInjectionPolicy": { # The specification for fault injection introduced into traffic to test the resiliency of clients to backend service failure. As part of fault injection, when clients send requests to a backend service, delays can be introduced by Loadbalancer on a percentage of requests before sending those request to the backend service. Similarly requests from clients can be aborted by the Loadbalancer for a percentage of requests. # The specification for fault injection introduced into traffic to test the resiliency of clients to backend service failure. As part of fault injection, when clients send requests to a backend service, delays can be introduced by Loadbalancer on a percentage of requests before sending those request to the backend service. Similarly requests from clients can be aborted by the Loadbalancer for a percentage of requests.
                 # timeout and retry_policy will be ignored by clients that are configured with a fault_injection_policy.
-                # Not supported when the URL map is bound to target gRPC proxy that has validateForProxyless field set to true.
               "abort": { # Specification for how requests are aborted as part of fault injection. # The specification for how client requests are aborted as part of fault injection.
                 "httpStatus": 42, # The HTTP status code used to abort the request.
                     # The value must be between 200 and 599 inclusive.
+                    # For gRPC protocol, the gRPC status code is mapped to HTTP status code according to this  mapping table. HTTP status 200 is mapped to gRPC status UNKNOWN. Injecting an OK status is currently not supported by Traffic Director.
                 "percentage": 3.14, # The percentage of traffic (connections/operations/requests) which will be aborted as part of fault injection.
                     # The value must be between 0.0 and 100.0 inclusive.
               },
@@ -3454,7 +3454,7 @@
                 "nanos": 42, # Span of time that's a fraction of a second at nanosecond resolution. Durations less than one second are represented with a 0 `seconds` field and a positive `nanos` field. Must be from 0 to 999,999,999 inclusive.
                 "seconds": "A String", # Span of time at a resolution of a second. Must be from 0 to 315,576,000,000 inclusive. Note: these bounds are computed from: 60 sec/min * 60 min/hr * 24 hr/day * 365.25 days/year * 10000 years
               },
-              "retryConditions": [ # Specfies one or more conditions when this retry rule applies. Valid values are:
+              "retryConditions": [ # Specifies 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.
                   # -
@@ -3616,10 +3616,10 @@
                 },
                 "faultInjectionPolicy": { # The specification for fault injection introduced into traffic to test the resiliency of clients to backend service failure. As part of fault injection, when clients send requests to a backend service, delays can be introduced by Loadbalancer on a percentage of requests before sending those request to the backend service. Similarly requests from clients can be aborted by the Loadbalancer for a percentage of requests. # The specification for fault injection introduced into traffic to test the resiliency of clients to backend service failure. As part of fault injection, when clients send requests to a backend service, delays can be introduced by Loadbalancer on a percentage of requests before sending those request to the backend service. Similarly requests from clients can be aborted by the Loadbalancer for a percentage of requests.
                     # timeout and retry_policy will be ignored by clients that are configured with a fault_injection_policy.
-                    # Not supported when the URL map is bound to target gRPC proxy that has validateForProxyless field set to true.
                   "abort": { # Specification for how requests are aborted as part of fault injection. # The specification for how client requests are aborted as part of fault injection.
                     "httpStatus": 42, # The HTTP status code used to abort the request.
                         # The value must be between 200 and 599 inclusive.
+                        # For gRPC protocol, the gRPC status code is mapped to HTTP status code according to this  mapping table. HTTP status 200 is mapped to gRPC status UNKNOWN. Injecting an OK status is currently not supported by Traffic Director.
                     "percentage": 3.14, # The percentage of traffic (connections/operations/requests) which will be aborted as part of fault injection.
                         # The value must be between 0.0 and 100.0 inclusive.
                   },
@@ -3650,7 +3650,7 @@
                     "nanos": 42, # Span of time that's a fraction of a second at nanosecond resolution. Durations less than one second are represented with a 0 `seconds` field and a positive `nanos` field. Must be from 0 to 999,999,999 inclusive.
                     "seconds": "A String", # Span of time at a resolution of a second. Must be from 0 to 315,576,000,000 inclusive. Note: these bounds are computed from: 60 sec/min * 60 min/hr * 24 hr/day * 365.25 days/year * 10000 years
                   },
-                  "retryConditions": [ # Specfies one or more conditions when this retry rule applies. Valid values are:
+                  "retryConditions": [ # Specifies 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.
                       # -
@@ -3910,10 +3910,10 @@
                 },
                 "faultInjectionPolicy": { # The specification for fault injection introduced into traffic to test the resiliency of clients to backend service failure. As part of fault injection, when clients send requests to a backend service, delays can be introduced by Loadbalancer on a percentage of requests before sending those request to the backend service. Similarly requests from clients can be aborted by the Loadbalancer for a percentage of requests. # The specification for fault injection introduced into traffic to test the resiliency of clients to backend service failure. As part of fault injection, when clients send requests to a backend service, delays can be introduced by Loadbalancer on a percentage of requests before sending those request to the backend service. Similarly requests from clients can be aborted by the Loadbalancer for a percentage of requests.
                     # timeout and retry_policy will be ignored by clients that are configured with a fault_injection_policy.
-                    # Not supported when the URL map is bound to target gRPC proxy that has validateForProxyless field set to true.
                   "abort": { # Specification for how requests are aborted as part of fault injection. # The specification for how client requests are aborted as part of fault injection.
                     "httpStatus": 42, # The HTTP status code used to abort the request.
                         # The value must be between 200 and 599 inclusive.
+                        # For gRPC protocol, the gRPC status code is mapped to HTTP status code according to this  mapping table. HTTP status 200 is mapped to gRPC status UNKNOWN. Injecting an OK status is currently not supported by Traffic Director.
                     "percentage": 3.14, # The percentage of traffic (connections/operations/requests) which will be aborted as part of fault injection.
                         # The value must be between 0.0 and 100.0 inclusive.
                   },
@@ -3944,7 +3944,7 @@
                     "nanos": 42, # Span of time that's a fraction of a second at nanosecond resolution. Durations less than one second are represented with a 0 `seconds` field and a positive `nanos` field. Must be from 0 to 999,999,999 inclusive.
                     "seconds": "A String", # Span of time at a resolution of a second. Must be from 0 to 315,576,000,000 inclusive. Note: these bounds are computed from: 60 sec/min * 60 min/hr * 24 hr/day * 365.25 days/year * 10000 years
                   },
-                  "retryConditions": [ # Specfies one or more conditions when this retry rule applies. Valid values are:
+                  "retryConditions": [ # Specifies 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.
                       # -
@@ -4156,10 +4156,10 @@
     },
     "faultInjectionPolicy": { # The specification for fault injection introduced into traffic to test the resiliency of clients to backend service failure. As part of fault injection, when clients send requests to a backend service, delays can be introduced by Loadbalancer on a percentage of requests before sending those request to the backend service. Similarly requests from clients can be aborted by the Loadbalancer for a percentage of requests. # The specification for fault injection introduced into traffic to test the resiliency of clients to backend service failure. As part of fault injection, when clients send requests to a backend service, delays can be introduced by Loadbalancer on a percentage of requests before sending those request to the backend service. Similarly requests from clients can be aborted by the Loadbalancer for a percentage of requests.
         # timeout and retry_policy will be ignored by clients that are configured with a fault_injection_policy.
-        # Not supported when the URL map is bound to target gRPC proxy that has validateForProxyless field set to true.
       "abort": { # Specification for how requests are aborted as part of fault injection. # The specification for how client requests are aborted as part of fault injection.
         "httpStatus": 42, # The HTTP status code used to abort the request.
             # The value must be between 200 and 599 inclusive.
+            # For gRPC protocol, the gRPC status code is mapped to HTTP status code according to this  mapping table. HTTP status 200 is mapped to gRPC status UNKNOWN. Injecting an OK status is currently not supported by Traffic Director.
         "percentage": 3.14, # The percentage of traffic (connections/operations/requests) which will be aborted as part of fault injection.
             # The value must be between 0.0 and 100.0 inclusive.
       },
@@ -4190,7 +4190,7 @@
         "nanos": 42, # Span of time that's a fraction of a second at nanosecond resolution. Durations less than one second are represented with a 0 `seconds` field and a positive `nanos` field. Must be from 0 to 999,999,999 inclusive.
         "seconds": "A String", # Span of time at a resolution of a second. Must be from 0 to 315,576,000,000 inclusive. Note: these bounds are computed from: 60 sec/min * 60 min/hr * 24 hr/day * 365.25 days/year * 10000 years
       },
-      "retryConditions": [ # Specfies one or more conditions when this retry rule applies. Valid values are:
+      "retryConditions": [ # Specifies 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.
           # -
@@ -4357,10 +4357,10 @@
         },
         "faultInjectionPolicy": { # The specification for fault injection introduced into traffic to test the resiliency of clients to backend service failure. As part of fault injection, when clients send requests to a backend service, delays can be introduced by Loadbalancer on a percentage of requests before sending those request to the backend service. Similarly requests from clients can be aborted by the Loadbalancer for a percentage of requests. # The specification for fault injection introduced into traffic to test the resiliency of clients to backend service failure. As part of fault injection, when clients send requests to a backend service, delays can be introduced by Loadbalancer on a percentage of requests before sending those request to the backend service. Similarly requests from clients can be aborted by the Loadbalancer for a percentage of requests.
             # timeout and retry_policy will be ignored by clients that are configured with a fault_injection_policy.
-            # Not supported when the URL map is bound to target gRPC proxy that has validateForProxyless field set to true.
           "abort": { # Specification for how requests are aborted as part of fault injection. # The specification for how client requests are aborted as part of fault injection.
             "httpStatus": 42, # The HTTP status code used to abort the request.
                 # The value must be between 200 and 599 inclusive.
+                # For gRPC protocol, the gRPC status code is mapped to HTTP status code according to this  mapping table. HTTP status 200 is mapped to gRPC status UNKNOWN. Injecting an OK status is currently not supported by Traffic Director.
             "percentage": 3.14, # The percentage of traffic (connections/operations/requests) which will be aborted as part of fault injection.
                 # The value must be between 0.0 and 100.0 inclusive.
           },
@@ -4391,7 +4391,7 @@
             "nanos": 42, # Span of time that's a fraction of a second at nanosecond resolution. Durations less than one second are represented with a 0 `seconds` field and a positive `nanos` field. Must be from 0 to 999,999,999 inclusive.
             "seconds": "A String", # Span of time at a resolution of a second. Must be from 0 to 315,576,000,000 inclusive. Note: these bounds are computed from: 60 sec/min * 60 min/hr * 24 hr/day * 365.25 days/year * 10000 years
           },
-          "retryConditions": [ # Specfies one or more conditions when this retry rule applies. Valid values are:
+          "retryConditions": [ # Specifies 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.
               # -
@@ -4553,10 +4553,10 @@
             },
             "faultInjectionPolicy": { # The specification for fault injection introduced into traffic to test the resiliency of clients to backend service failure. As part of fault injection, when clients send requests to a backend service, delays can be introduced by Loadbalancer on a percentage of requests before sending those request to the backend service. Similarly requests from clients can be aborted by the Loadbalancer for a percentage of requests. # The specification for fault injection introduced into traffic to test the resiliency of clients to backend service failure. As part of fault injection, when clients send requests to a backend service, delays can be introduced by Loadbalancer on a percentage of requests before sending those request to the backend service. Similarly requests from clients can be aborted by the Loadbalancer for a percentage of requests.
                 # timeout and retry_policy will be ignored by clients that are configured with a fault_injection_policy.
-                # Not supported when the URL map is bound to target gRPC proxy that has validateForProxyless field set to true.
               "abort": { # Specification for how requests are aborted as part of fault injection. # The specification for how client requests are aborted as part of fault injection.
                 "httpStatus": 42, # The HTTP status code used to abort the request.
                     # The value must be between 200 and 599 inclusive.
+                    # For gRPC protocol, the gRPC status code is mapped to HTTP status code according to this  mapping table. HTTP status 200 is mapped to gRPC status UNKNOWN. Injecting an OK status is currently not supported by Traffic Director.
                 "percentage": 3.14, # The percentage of traffic (connections/operations/requests) which will be aborted as part of fault injection.
                     # The value must be between 0.0 and 100.0 inclusive.
               },
@@ -4587,7 +4587,7 @@
                 "nanos": 42, # Span of time that's a fraction of a second at nanosecond resolution. Durations less than one second are represented with a 0 `seconds` field and a positive `nanos` field. Must be from 0 to 999,999,999 inclusive.
                 "seconds": "A String", # Span of time at a resolution of a second. Must be from 0 to 315,576,000,000 inclusive. Note: these bounds are computed from: 60 sec/min * 60 min/hr * 24 hr/day * 365.25 days/year * 10000 years
               },
-              "retryConditions": [ # Specfies one or more conditions when this retry rule applies. Valid values are:
+              "retryConditions": [ # Specifies 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.
                   # -
@@ -4847,10 +4847,10 @@
             },
             "faultInjectionPolicy": { # The specification for fault injection introduced into traffic to test the resiliency of clients to backend service failure. As part of fault injection, when clients send requests to a backend service, delays can be introduced by Loadbalancer on a percentage of requests before sending those request to the backend service. Similarly requests from clients can be aborted by the Loadbalancer for a percentage of requests. # The specification for fault injection introduced into traffic to test the resiliency of clients to backend service failure. As part of fault injection, when clients send requests to a backend service, delays can be introduced by Loadbalancer on a percentage of requests before sending those request to the backend service. Similarly requests from clients can be aborted by the Loadbalancer for a percentage of requests.
                 # timeout and retry_policy will be ignored by clients that are configured with a fault_injection_policy.
-                # Not supported when the URL map is bound to target gRPC proxy that has validateForProxyless field set to true.
               "abort": { # Specification for how requests are aborted as part of fault injection. # The specification for how client requests are aborted as part of fault injection.
                 "httpStatus": 42, # The HTTP status code used to abort the request.
                     # The value must be between 200 and 599 inclusive.
+                    # For gRPC protocol, the gRPC status code is mapped to HTTP status code according to this  mapping table. HTTP status 200 is mapped to gRPC status UNKNOWN. Injecting an OK status is currently not supported by Traffic Director.
                 "percentage": 3.14, # The percentage of traffic (connections/operations/requests) which will be aborted as part of fault injection.
                     # The value must be between 0.0 and 100.0 inclusive.
               },
@@ -4881,7 +4881,7 @@
                 "nanos": 42, # Span of time that's a fraction of a second at nanosecond resolution. Durations less than one second are represented with a 0 `seconds` field and a positive `nanos` field. Must be from 0 to 999,999,999 inclusive.
                 "seconds": "A String", # Span of time at a resolution of a second. Must be from 0 to 315,576,000,000 inclusive. Note: these bounds are computed from: 60 sec/min * 60 min/hr * 24 hr/day * 365.25 days/year * 10000 years
               },
-              "retryConditions": [ # Specfies one or more conditions when this retry rule applies. Valid values are:
+              "retryConditions": [ # Specifies 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.
                   # -
@@ -5160,10 +5160,10 @@
     },
     "faultInjectionPolicy": { # The specification for fault injection introduced into traffic to test the resiliency of clients to backend service failure. As part of fault injection, when clients send requests to a backend service, delays can be introduced by Loadbalancer on a percentage of requests before sending those request to the backend service. Similarly requests from clients can be aborted by the Loadbalancer for a percentage of requests. # The specification for fault injection introduced into traffic to test the resiliency of clients to backend service failure. As part of fault injection, when clients send requests to a backend service, delays can be introduced by Loadbalancer on a percentage of requests before sending those request to the backend service. Similarly requests from clients can be aborted by the Loadbalancer for a percentage of requests.
         # timeout and retry_policy will be ignored by clients that are configured with a fault_injection_policy.
-        # Not supported when the URL map is bound to target gRPC proxy that has validateForProxyless field set to true.
       "abort": { # Specification for how requests are aborted as part of fault injection. # The specification for how client requests are aborted as part of fault injection.
         "httpStatus": 42, # The HTTP status code used to abort the request.
             # The value must be between 200 and 599 inclusive.
+            # For gRPC protocol, the gRPC status code is mapped to HTTP status code according to this  mapping table. HTTP status 200 is mapped to gRPC status UNKNOWN. Injecting an OK status is currently not supported by Traffic Director.
         "percentage": 3.14, # The percentage of traffic (connections/operations/requests) which will be aborted as part of fault injection.
             # The value must be between 0.0 and 100.0 inclusive.
       },
@@ -5194,7 +5194,7 @@
         "nanos": 42, # Span of time that's a fraction of a second at nanosecond resolution. Durations less than one second are represented with a 0 `seconds` field and a positive `nanos` field. Must be from 0 to 999,999,999 inclusive.
         "seconds": "A String", # Span of time at a resolution of a second. Must be from 0 to 315,576,000,000 inclusive. Note: these bounds are computed from: 60 sec/min * 60 min/hr * 24 hr/day * 365.25 days/year * 10000 years
       },
-      "retryConditions": [ # Specfies one or more conditions when this retry rule applies. Valid values are:
+      "retryConditions": [ # Specifies 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.
           # -
@@ -5361,10 +5361,10 @@
         },
         "faultInjectionPolicy": { # The specification for fault injection introduced into traffic to test the resiliency of clients to backend service failure. As part of fault injection, when clients send requests to a backend service, delays can be introduced by Loadbalancer on a percentage of requests before sending those request to the backend service. Similarly requests from clients can be aborted by the Loadbalancer for a percentage of requests. # The specification for fault injection introduced into traffic to test the resiliency of clients to backend service failure. As part of fault injection, when clients send requests to a backend service, delays can be introduced by Loadbalancer on a percentage of requests before sending those request to the backend service. Similarly requests from clients can be aborted by the Loadbalancer for a percentage of requests.
             # timeout and retry_policy will be ignored by clients that are configured with a fault_injection_policy.
-            # Not supported when the URL map is bound to target gRPC proxy that has validateForProxyless field set to true.
           "abort": { # Specification for how requests are aborted as part of fault injection. # The specification for how client requests are aborted as part of fault injection.
             "httpStatus": 42, # The HTTP status code used to abort the request.
                 # The value must be between 200 and 599 inclusive.
+                # For gRPC protocol, the gRPC status code is mapped to HTTP status code according to this  mapping table. HTTP status 200 is mapped to gRPC status UNKNOWN. Injecting an OK status is currently not supported by Traffic Director.
             "percentage": 3.14, # The percentage of traffic (connections/operations/requests) which will be aborted as part of fault injection.
                 # The value must be between 0.0 and 100.0 inclusive.
           },
@@ -5395,7 +5395,7 @@
             "nanos": 42, # Span of time that's a fraction of a second at nanosecond resolution. Durations less than one second are represented with a 0 `seconds` field and a positive `nanos` field. Must be from 0 to 999,999,999 inclusive.
             "seconds": "A String", # Span of time at a resolution of a second. Must be from 0 to 315,576,000,000 inclusive. Note: these bounds are computed from: 60 sec/min * 60 min/hr * 24 hr/day * 365.25 days/year * 10000 years
           },
-          "retryConditions": [ # Specfies one or more conditions when this retry rule applies. Valid values are:
+          "retryConditions": [ # Specifies 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.
               # -
@@ -5557,10 +5557,10 @@
             },
             "faultInjectionPolicy": { # The specification for fault injection introduced into traffic to test the resiliency of clients to backend service failure. As part of fault injection, when clients send requests to a backend service, delays can be introduced by Loadbalancer on a percentage of requests before sending those request to the backend service. Similarly requests from clients can be aborted by the Loadbalancer for a percentage of requests. # The specification for fault injection introduced into traffic to test the resiliency of clients to backend service failure. As part of fault injection, when clients send requests to a backend service, delays can be introduced by Loadbalancer on a percentage of requests before sending those request to the backend service. Similarly requests from clients can be aborted by the Loadbalancer for a percentage of requests.
                 # timeout and retry_policy will be ignored by clients that are configured with a fault_injection_policy.
-                # Not supported when the URL map is bound to target gRPC proxy that has validateForProxyless field set to true.
               "abort": { # Specification for how requests are aborted as part of fault injection. # The specification for how client requests are aborted as part of fault injection.
                 "httpStatus": 42, # The HTTP status code used to abort the request.
                     # The value must be between 200 and 599 inclusive.
+                    # For gRPC protocol, the gRPC status code is mapped to HTTP status code according to this  mapping table. HTTP status 200 is mapped to gRPC status UNKNOWN. Injecting an OK status is currently not supported by Traffic Director.
                 "percentage": 3.14, # The percentage of traffic (connections/operations/requests) which will be aborted as part of fault injection.
                     # The value must be between 0.0 and 100.0 inclusive.
               },
@@ -5591,7 +5591,7 @@
                 "nanos": 42, # Span of time that's a fraction of a second at nanosecond resolution. Durations less than one second are represented with a 0 `seconds` field and a positive `nanos` field. Must be from 0 to 999,999,999 inclusive.
                 "seconds": "A String", # Span of time at a resolution of a second. Must be from 0 to 315,576,000,000 inclusive. Note: these bounds are computed from: 60 sec/min * 60 min/hr * 24 hr/day * 365.25 days/year * 10000 years
               },
-              "retryConditions": [ # Specfies one or more conditions when this retry rule applies. Valid values are:
+              "retryConditions": [ # Specifies 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.
                   # -
@@ -5851,10 +5851,10 @@
             },
             "faultInjectionPolicy": { # The specification for fault injection introduced into traffic to test the resiliency of clients to backend service failure. As part of fault injection, when clients send requests to a backend service, delays can be introduced by Loadbalancer on a percentage of requests before sending those request to the backend service. Similarly requests from clients can be aborted by the Loadbalancer for a percentage of requests. # The specification for fault injection introduced into traffic to test the resiliency of clients to backend service failure. As part of fault injection, when clients send requests to a backend service, delays can be introduced by Loadbalancer on a percentage of requests before sending those request to the backend service. Similarly requests from clients can be aborted by the Loadbalancer for a percentage of requests.
                 # timeout and retry_policy will be ignored by clients that are configured with a fault_injection_policy.
-                # Not supported when the URL map is bound to target gRPC proxy that has validateForProxyless field set to true.
               "abort": { # Specification for how requests are aborted as part of fault injection. # The specification for how client requests are aborted as part of fault injection.
                 "httpStatus": 42, # The HTTP status code used to abort the request.
                     # The value must be between 200 and 599 inclusive.
+                    # For gRPC protocol, the gRPC status code is mapped to HTTP status code according to this  mapping table. HTTP status 200 is mapped to gRPC status UNKNOWN. Injecting an OK status is currently not supported by Traffic Director.
                 "percentage": 3.14, # The percentage of traffic (connections/operations/requests) which will be aborted as part of fault injection.
                     # The value must be between 0.0 and 100.0 inclusive.
               },
@@ -5885,7 +5885,7 @@
                 "nanos": 42, # Span of time that's a fraction of a second at nanosecond resolution. Durations less than one second are represented with a 0 `seconds` field and a positive `nanos` field. Must be from 0 to 999,999,999 inclusive.
                 "seconds": "A String", # Span of time at a resolution of a second. Must be from 0 to 315,576,000,000 inclusive. Note: these bounds are computed from: 60 sec/min * 60 min/hr * 24 hr/day * 365.25 days/year * 10000 years
               },
-              "retryConditions": [ # Specfies one or more conditions when this retry rule applies. Valid values are:
+              "retryConditions": [ # Specifies 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.
                   # -
@@ -6138,10 +6138,10 @@
       },
       "faultInjectionPolicy": { # The specification for fault injection introduced into traffic to test the resiliency of clients to backend service failure. As part of fault injection, when clients send requests to a backend service, delays can be introduced by Loadbalancer on a percentage of requests before sending those request to the backend service. Similarly requests from clients can be aborted by the Loadbalancer for a percentage of requests. # The specification for fault injection introduced into traffic to test the resiliency of clients to backend service failure. As part of fault injection, when clients send requests to a backend service, delays can be introduced by Loadbalancer on a percentage of requests before sending those request to the backend service. Similarly requests from clients can be aborted by the Loadbalancer for a percentage of requests.
           # timeout and retry_policy will be ignored by clients that are configured with a fault_injection_policy.
-          # Not supported when the URL map is bound to target gRPC proxy that has validateForProxyless field set to true.
         "abort": { # Specification for how requests are aborted as part of fault injection. # The specification for how client requests are aborted as part of fault injection.
           "httpStatus": 42, # The HTTP status code used to abort the request.
               # The value must be between 200 and 599 inclusive.
+              # For gRPC protocol, the gRPC status code is mapped to HTTP status code according to this  mapping table. HTTP status 200 is mapped to gRPC status UNKNOWN. Injecting an OK status is currently not supported by Traffic Director.
           "percentage": 3.14, # The percentage of traffic (connections/operations/requests) which will be aborted as part of fault injection.
               # The value must be between 0.0 and 100.0 inclusive.
         },
@@ -6172,7 +6172,7 @@
           "nanos": 42, # Span of time that's a fraction of a second at nanosecond resolution. Durations less than one second are represented with a 0 `seconds` field and a positive `nanos` field. Must be from 0 to 999,999,999 inclusive.
           "seconds": "A String", # Span of time at a resolution of a second. Must be from 0 to 315,576,000,000 inclusive. Note: these bounds are computed from: 60 sec/min * 60 min/hr * 24 hr/day * 365.25 days/year * 10000 years
         },
-        "retryConditions": [ # Specfies one or more conditions when this retry rule applies. Valid values are:
+        "retryConditions": [ # Specifies 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.
             # -
@@ -6339,10 +6339,10 @@
           },
           "faultInjectionPolicy": { # The specification for fault injection introduced into traffic to test the resiliency of clients to backend service failure. As part of fault injection, when clients send requests to a backend service, delays can be introduced by Loadbalancer on a percentage of requests before sending those request to the backend service. Similarly requests from clients can be aborted by the Loadbalancer for a percentage of requests. # The specification for fault injection introduced into traffic to test the resiliency of clients to backend service failure. As part of fault injection, when clients send requests to a backend service, delays can be introduced by Loadbalancer on a percentage of requests before sending those request to the backend service. Similarly requests from clients can be aborted by the Loadbalancer for a percentage of requests.
               # timeout and retry_policy will be ignored by clients that are configured with a fault_injection_policy.
-              # Not supported when the URL map is bound to target gRPC proxy that has validateForProxyless field set to true.
             "abort": { # Specification for how requests are aborted as part of fault injection. # The specification for how client requests are aborted as part of fault injection.
               "httpStatus": 42, # The HTTP status code used to abort the request.
                   # The value must be between 200 and 599 inclusive.
+                  # For gRPC protocol, the gRPC status code is mapped to HTTP status code according to this  mapping table. HTTP status 200 is mapped to gRPC status UNKNOWN. Injecting an OK status is currently not supported by Traffic Director.
               "percentage": 3.14, # The percentage of traffic (connections/operations/requests) which will be aborted as part of fault injection.
                   # The value must be between 0.0 and 100.0 inclusive.
             },
@@ -6373,7 +6373,7 @@
               "nanos": 42, # Span of time that's a fraction of a second at nanosecond resolution. Durations less than one second are represented with a 0 `seconds` field and a positive `nanos` field. Must be from 0 to 999,999,999 inclusive.
               "seconds": "A String", # Span of time at a resolution of a second. Must be from 0 to 315,576,000,000 inclusive. Note: these bounds are computed from: 60 sec/min * 60 min/hr * 24 hr/day * 365.25 days/year * 10000 years
             },
-            "retryConditions": [ # Specfies one or more conditions when this retry rule applies. Valid values are:
+            "retryConditions": [ # Specifies 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.
                 # -
@@ -6535,10 +6535,10 @@
               },
               "faultInjectionPolicy": { # The specification for fault injection introduced into traffic to test the resiliency of clients to backend service failure. As part of fault injection, when clients send requests to a backend service, delays can be introduced by Loadbalancer on a percentage of requests before sending those request to the backend service. Similarly requests from clients can be aborted by the Loadbalancer for a percentage of requests. # The specification for fault injection introduced into traffic to test the resiliency of clients to backend service failure. As part of fault injection, when clients send requests to a backend service, delays can be introduced by Loadbalancer on a percentage of requests before sending those request to the backend service. Similarly requests from clients can be aborted by the Loadbalancer for a percentage of requests.
                   # timeout and retry_policy will be ignored by clients that are configured with a fault_injection_policy.
-                  # Not supported when the URL map is bound to target gRPC proxy that has validateForProxyless field set to true.
                 "abort": { # Specification for how requests are aborted as part of fault injection. # The specification for how client requests are aborted as part of fault injection.
                   "httpStatus": 42, # The HTTP status code used to abort the request.
                       # The value must be between 200 and 599 inclusive.
+                      # For gRPC protocol, the gRPC status code is mapped to HTTP status code according to this  mapping table. HTTP status 200 is mapped to gRPC status UNKNOWN. Injecting an OK status is currently not supported by Traffic Director.
                   "percentage": 3.14, # The percentage of traffic (connections/operations/requests) which will be aborted as part of fault injection.
                       # The value must be between 0.0 and 100.0 inclusive.
                 },
@@ -6569,7 +6569,7 @@
                   "nanos": 42, # Span of time that's a fraction of a second at nanosecond resolution. Durations less than one second are represented with a 0 `seconds` field and a positive `nanos` field. Must be from 0 to 999,999,999 inclusive.
                   "seconds": "A String", # Span of time at a resolution of a second. Must be from 0 to 315,576,000,000 inclusive. Note: these bounds are computed from: 60 sec/min * 60 min/hr * 24 hr/day * 365.25 days/year * 10000 years
                 },
-                "retryConditions": [ # Specfies one or more conditions when this retry rule applies. Valid values are:
+                "retryConditions": [ # Specifies 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.
                     # -
@@ -6829,10 +6829,10 @@
               },
               "faultInjectionPolicy": { # The specification for fault injection introduced into traffic to test the resiliency of clients to backend service failure. As part of fault injection, when clients send requests to a backend service, delays can be introduced by Loadbalancer on a percentage of requests before sending those request to the backend service. Similarly requests from clients can be aborted by the Loadbalancer for a percentage of requests. # The specification for fault injection introduced into traffic to test the resiliency of clients to backend service failure. As part of fault injection, when clients send requests to a backend service, delays can be introduced by Loadbalancer on a percentage of requests before sending those request to the backend service. Similarly requests from clients can be aborted by the Loadbalancer for a percentage of requests.
                   # timeout and retry_policy will be ignored by clients that are configured with a fault_injection_policy.
-                  # Not supported when the URL map is bound to target gRPC proxy that has validateForProxyless field set to true.
                 "abort": { # Specification for how requests are aborted as part of fault injection. # The specification for how client requests are aborted as part of fault injection.
                   "httpStatus": 42, # The HTTP status code used to abort the request.
                       # The value must be between 200 and 599 inclusive.
+                      # For gRPC protocol, the gRPC status code is mapped to HTTP status code according to this  mapping table. HTTP status 200 is mapped to gRPC status UNKNOWN. Injecting an OK status is currently not supported by Traffic Director.
                   "percentage": 3.14, # The percentage of traffic (connections/operations/requests) which will be aborted as part of fault injection.
                       # The value must be between 0.0 and 100.0 inclusive.
                 },
@@ -6863,7 +6863,7 @@
                   "nanos": 42, # Span of time that's a fraction of a second at nanosecond resolution. Durations less than one second are represented with a 0 `seconds` field and a positive `nanos` field. Must be from 0 to 999,999,999 inclusive.
                   "seconds": "A String", # Span of time at a resolution of a second. Must be from 0 to 315,576,000,000 inclusive. Note: these bounds are computed from: 60 sec/min * 60 min/hr * 24 hr/day * 365.25 days/year * 10000 years
                 },
-                "retryConditions": [ # Specfies one or more conditions when this retry rule applies. Valid values are:
+                "retryConditions": [ # Specifies 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.
                     # -