Regenerate client from commit 60c6582 of spec repo

DataDog · Nov 29, 2021 · 50f7085 · 50f7085
1 parent 5b49812
commit 50f7085
Show file tree

Hide file tree

Showing 6 changed files with 77 additions and 28 deletions.
diff --git a/.apigentools-info b/.apigentools-info
@@ -4,13 +4,13 @@
     "spec_versions": {
         "v1": {
             "apigentools_version": "1.5.1.dev2",
-            "regenerated": "2021-11-26 10:29:43.003956",
-            "spec_repo_commit": "fdabc88"
+            "regenerated": "2021-11-29 15:07:21.926609",
+            "spec_repo_commit": "60c6582"
         },
         "v2": {
             "apigentools_version": "1.5.1.dev2",
-            "regenerated": "2021-11-26 10:29:43.022631",
-            "spec_repo_commit": "fdabc88"
+            "regenerated": "2021-11-29 15:07:21.945313",
+            "spec_repo_commit": "60c6582"
         }
     }
 }
diff --git a/api/v1/datadog/client.go b/api/v1/datadog/client.go
diff --git a/api/v2/datadog/client.go b/api/v2/datadog/client.go
diff --git a/.../v1/Feature_Events/Scenario_Post_an_event_in_the_past_returns_Bad_Request_response.freeze b/.../v1/Feature_Events/Scenario_Post_an_event_in_the_past_returns_Bad_Request_response.freeze
@@ -0,0 +1 @@
+2021-11-27T20:34:41.465Z
diff --git a/...os/v1/Feature_Events/Scenario_Post_an_event_in_the_past_returns_Bad_Request_response.yaml b/...os/v1/Feature_Events/Scenario_Post_an_event_in_the_past_returns_Bad_Request_response.yaml
@@ -0,0 +1,47 @@
+interactions:
+- request:
+    body: |
+      {"date_happened":1,"tags":["test:TestPostaneventinthepastreturnsBadRequestresponse1638045281"],"text":"A text message.","title":"Test-Post_an_event_in_the_past_returns_Bad_Request_response-1638045281"}
+    form: {}
+    headers:
+      Accept:
+      - application/json, */*;q=0.8
+      Connection:
+      - close
+      Content-Length:
+      - '201'
+      Content-Type:
+      - application/json
+      Host:
+      - api.datadoghq.com
+      User-Agent:
+      - datadog-api-client-typescript/1.0.0-beta.6 (node 14.18.1; os Linux; arch x64)
+      X-Datadog-Parent-Id:
+      - '343467568446934486'
+      X-Datadog-Trace-Id:
+      - '4038788092229867157'
+    method: POST
+    url: https://api.datadoghq.com/api/v1/events
+  response:
+    body: '{"errors": ["Event too far in the past"]}'
+    code: 400
+    duration: ''
+    headers:
+      Connection:
+      - close
+      Content-Length:
+      - '41'
+      Content-Security-Policy:
+      - frame-ancestors 'self'; report-uri https://api.datadoghq.com/csp-report
+      Content-Type:
+      - text/plain; charset=utf-8
+      Date:
+      - Sat, 27 Nov 2021 20:34:41 GMT
+      Strict-Transport-Security:
+      - max-age=15724800;
+      X-Content-Type-Options:
+      - nosniff
+      X-Frame-Options:
+      - SAMEORIGIN
+    status: 400 Bad Request
+version: 1
diff --git a/tests/scenarios/features/v1/events.feature b/tests/scenarios/features/v1/events.feature
@@ -44,6 +44,13 @@ Feature: Events
     When the request is sent
     Then the response status is 202 OK
 
+  Scenario: Post an event in the past returns "Bad Request" response
+    Given new "CreateEvent" request
+    And body with value {"title": "{{ unique }}", "text": "A text message.", "date_happened": 1, "tags": ["test:{{ unique_alnum }}"]}
+    When the request is sent
+    Then the response status is 400 Bad Request
+    And the response "errors[0]" is equal to "Event too far in the past"
+
   @generated @skip
   Scenario: Query the event stream returns "Bad Request" response
     Given a valid "appKeyAuth" key in the system