Regenerate client from commit e3e4b05 of spec repo (#648)

Co-authored-by: ci.datadog-api-spec <packages@datadoghq.com>

Author: api-clients-generation-pipeline[bot]

.apigentools-info

@@ -4,13 +4,13 @@
     "spec_versions": {
         "v1": {
             "apigentools_version": "1.4.1.dev2",
-            "regenerated": "2021-02-09 09:15:06.291046",
-            "spec_repo_commit": "104aacd"
+            "regenerated": "2021-02-09 10:32:40.316757",
+            "spec_repo_commit": "e3e4b05"
         },
         "v2": {
             "apigentools_version": "1.4.1.dev2",
-            "regenerated": "2021-02-09 09:15:15.743961",
-            "spec_repo_commit": "104aacd"
+            "regenerated": "2021-02-09 10:32:50.189458",
+            "spec_repo_commit": "e3e4b05"
         }
     }
 }

api/openapi.yaml

@@ -54,26 +54,7 @@ tags:
     description: Find out more at
     url: https://docs.datadoghq.com/account_management/api-app-keys/
   name: Key Management
-- description: |-
-    Search your logs and send them to your Datadog platform over HTTP. Limits per HTTP request are:
-
-    - Maximum content size per payload (uncompressed): 5MB
-    - Maximum size for a single log: 1MB
-    - Maximum array size if sending multiple logs in an array: 1000 entries
-
-    Any log exceeding 1MB is accepted and truncated by Datadog:
-    - For a single log request, the API truncates the log at 1MB and returns a 2xx.
-    - For a multi-logs request, the API processes all logs, truncates only logs larger than 1MB, and returns a 2xx.
-
-    Datadog recommends sending your logs compressed.
-    Add the `Content-Encoding: gzip` header to the request when sending compressed logs.
-
-    The status codes answered by the HTTP API are:
-    - 200: OK
-    - 400: Bad request (likely an issue in the payload formatting)
-    - 403: Permission issue (likely using an invalid API Key)
-    - 413: Payload too large (batch is above 5MB uncompressed)
-    - 5xx: Internal error, request should be retried after some time
+- description: Search your logs and send them to your Datadog platform over HTTP.
   name: Logs
 - description: |-
     Archives forward all the logs ingested to a cloud storage system.

src/main/java/com/datadog/api/v1/openapi.yaml

@@ -17938,42 +17938,7 @@ tags:
     description: Find out more at
     url: https://docs.datadoghq.com/account_management/api-app-keys/
   name: Key Management
-- description: 'Search your logs and send them to your Datadog platform over HTTP.
-    Limits per HTTP request are:
-
-
-    - Maximum content size per payload (uncompressed): 5MB
-
-    - Maximum size for a single log: 1MB
-
-    - Maximum array size if sending multiple logs in an array: 1000 entries
-
-
-    Any log exceeding 1MB is accepted and truncated by Datadog:
-
-    - For a single log request, the API truncates the log at 1MB and returns a 2xx.
-
-    - For a multi-logs request, the API processes all logs, truncates only logs larger
-    than 1MB, and returns a 2xx.
-
-
-    Datadog recommends sending your logs compressed.
-
-    Add the `Content-Encoding: gzip` header to the request when sending compressed
-    logs.
-
-
-    The status codes answered by the HTTP API are:
-
-    - 200: OK
-
-    - 400: Bad request (likely an issue in the payload formatting)
-
-    - 403: Permission issue (likely using an invalid API Key)
-
-    - 413: Payload too large (batch is above 5MB uncompressed)
-
-    - 5xx: Internal error, request should be retried after some time'
+- description: Search your logs and send them to your Datadog platform over HTTP.
   name: Logs
 - description: 'Manage configuration of [log indexes](https://docs.datadoghq.com/logs/indexes/).
 

src/main/java/com/datadog/api/v2/openapi.yaml

@@ -7449,42 +7449,7 @@ tags:
     description: Find out more at
     url: https://docs.datadoghq.com/account_management/api-app-keys/
   name: Key Management
-- description: 'Search your logs and send them to your Datadog platform over HTTP.
-    Limits per HTTP request are:
-
-
-    - Maximum content size per payload (uncompressed): 5MB
-
-    - Maximum size for a single log: 1MB
-
-    - Maximum array size if sending multiple logs in an array: 1000 entries
-
-
-    Any log exceeding 1MB is accepted and truncated by Datadog:
-
-    - For a single log request, the API truncates the log at 1MB and returns a 2xx.
-
-    - For a multi-logs request, the API processes all logs, truncates only logs larger
-    than 1MB, and returns a 2xx.
-
-
-    Datadog recommends sending your logs compressed.
-
-    Add the `Content-Encoding: gzip` header to the request when sending compressed
-    logs.
-
-
-    The status codes answered by the HTTP API are:
-
-    - 200: OK
-
-    - 400: Bad request (likely an issue in the payload formatting)
-
-    - 403: Permission issue (likely using an invalid API Key)
-
-    - 413: Payload too large (batch is above 5MB uncompressed)
-
-    - 5xx: Internal error, request should be retried after some time'
+- description: Search your logs and send them to your Datadog platform over HTTP.
   name: Logs
 - description: 'Archives forward all the logs ingested to a cloud storage system.
 

src/test/resources/com/datadog/api/v1/client/api/logs.feature

@@ -1,19 +1,6 @@
 @endpoint(logs)
 Feature: Logs
-  Search your logs and send them to your Datadog platform over HTTP. Limits
-  per HTTP request are:  - Maximum content size per payload (uncompressed):
-  5MB - Maximum size for a single log: 1MB - Maximum array size if sending
-  multiple logs in an array: 1000 entries  Any log exceeding 1MB is accepted
-  and truncated by Datadog: - For a single log request, the API truncates
-  the log at 1MB and returns a 2xx. - For a multi-logs request, the API
-  processes all logs, truncates only logs larger than 1MB, and returns a
-  2xx.  Datadog recommends sending your logs compressed. Add the `Content-
-  Encoding: gzip` header to the request when sending compressed logs.  The
-  status codes answered by the HTTP API are: - 200: OK - 400: Bad request
-  (likely an issue in the payload formatting) - 403: Permission issue
-  (likely using an invalid API Key) - 413: Payload too large (batch is above
-  5MB uncompressed) - 5xx: Internal error, request should be retried after
-  some time
+  Search your logs and send them to your Datadog platform over HTTP.
 
   Background:
     Given a valid "apiKeyAuth" key in the system

src/test/resources/com/datadog/api/v2/client/api/logs.feature

@@ -1,19 +1,6 @@
 @endpoint(logs)
 Feature: Logs
-  Search your logs and send them to your Datadog platform over HTTP. Limits
-  per HTTP request are:  - Maximum content size per payload (uncompressed):
-  5MB - Maximum size for a single log: 1MB - Maximum array size if sending
-  multiple logs in an array: 1000 entries  Any log exceeding 1MB is accepted
-  and truncated by Datadog: - For a single log request, the API truncates
-  the log at 1MB and returns a 2xx. - For a multi-logs request, the API
-  processes all logs, truncates only logs larger than 1MB, and returns a
-  2xx.  Datadog recommends sending your logs compressed. Add the `Content-
-  Encoding: gzip` header to the request when sending compressed logs.  The
-  status codes answered by the HTTP API are: - 200: OK - 400: Bad request
-  (likely an issue in the payload formatting) - 403: Permission issue
-  (likely using an invalid API Key) - 413: Payload too large (batch is above
-  5MB uncompressed) - 5xx: Internal error, request should be retried after
-  some time
+  Search your logs and send them to your Datadog platform over HTTP.
 
   Background:
     Given a valid "apiKeyAuth" key in the system