Regenerate client from commit 8e5ea991 of spec repo (#966)

Co-authored-by: ci.datadog-api-spec <[email protected]>
Co-authored-by: api-clients-generation-pipeline[bot] <54105614+api-clients-generation-pipeline[bot]@users.noreply.github.com>

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

.apigentools-info

@@ -4,13 +4,13 @@
     "spec_versions": {
         "v1": {
             "apigentools_version": "1.6.2",
-            "regenerated": "2022-05-16 16:35:09.506917",
-            "spec_repo_commit": "e6216ca6"
+            "regenerated": "2022-05-17 12:13:30.981727",
+            "spec_repo_commit": "8e5ea991"
         },
         "v2": {
             "apigentools_version": "1.6.2",
-            "regenerated": "2022-05-16 16:35:09.518757",
-            "spec_repo_commit": "e6216ca6"
+            "regenerated": "2022-05-17 12:13:30.997064",
+            "spec_repo_commit": "8e5ea991"
         }
     }
 }

.generator/schemas/v1/openapi.yaml

@@ -2897,6 +2897,9 @@ components:
       - message
       type: object
     HTTPLogItem:
+      additionalProperties:
+        description: Additional log attributes.
+        type: string
       description: Logs that are sent over HTTP.
       properties:
         ddsource:

.generator/schemas/v2/openapi.yaml

@@ -1620,6 +1620,9 @@ components:
           type: array
       type: object
     HTTPLogItem:
+      additionalProperties:
+        description: Additional log attributes.
+        type: string
       description: Logs that are sent over HTTP.
       properties:
         ddsource:
@@ -1661,7 +1664,7 @@ components:
           example: payment
           type: string
       required:
-      - name
+      - message
       type: object
     HourlyUsageType:
       description: Usage type that is being measured.

examples/v2/logs/SubmitLog.py

@@ -15,6 +15,7 @@
             hostname="i-012345678",
             message="2019-11-19T14:37:58,995 INFO [process.name][20081] Hello World",
             service="payment",
+            status="error",
         ),
     ]
 )

src/datadog_api_client/v1/model/http_log_item.py

@@ -0,0 +1 @@
+2022-05-12T15:31:57.041Z

src/datadog_api_client/v2/model/http_log_item.py

@@ -0,0 +1,21 @@
+interactions:
+- request:
+    body: '[{"ddsource":"nginx","ddtags":"env:staging,version:5.1","hostname":"i-012345678","message":"2019-11-19T14:37:58,995
+      INFO [process.name][20081] Hello World","service":"payment","status":"error"}]'
+    headers:
+      accept:
+      - application/json
+      content-type:
+      - application/json
+    method: POST
+    uri: https://http-intake.logs.datadoghq.com/api/v2/logs
+  response:
+    body:
+      string: '{}'
+    headers:
+      content-type:
+      - application/json
+    status:
+      code: 202
+      message: Accepted
+version: 1

tests/v2/cassettes/test_scenarios/test_send_logs_returns_request_accepted_for_processing_always_202_empty_json_response.frozen

@@ -135,9 +135,9 @@ Feature: Logs
     When the request is sent
     Then the response status is 408 Request Timeout
 
-  @generated @skip @team:DataDog/logs-backend @team:DataDog/logs-intake
+  @skip-go @skip-typescript @team:DataDog/logs-backend @team:DataDog/logs-intake
   Scenario: Send logs returns "Request accepted for processing (always 202 empty JSON)." response
     Given new "SubmitLog" request
-    And body with value [{"ddsource": "nginx", "ddtags": "env:staging,version:5.1", "hostname": "i-012345678", "message": "2019-11-19T14:37:58,995 INFO [process.name][20081] Hello World", "service": "payment"}]
+    And body with value [{"ddsource": "nginx", "ddtags": "env:staging,version:5.1", "hostname": "i-012345678", "message": "2019-11-19T14:37:58,995 INFO [process.name][20081] Hello World", "service": "payment", "status": "error"}]
     When the request is sent
     Then the response status is 202 Request accepted for processing (always 202 empty JSON).