Regenerate client from commit 3ecdb0c of spec repo

DataDog · Nov 27, 2021 · 0fc7fca · 0fc7fca
1 parent 76bfb79
commit 0fc7fca
Show file tree

Hide file tree

Showing 2 changed files with 11 additions and 4 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-27 18:18:17.828430",
+            "spec_repo_commit": "3ecdb0c"
         },
         "v2": {
             "apigentools_version": "1.5.1.dev2",
-            "regenerated": "2021-11-26 10:29:43.022631",
-            "spec_repo_commit": "fdabc88"
+            "regenerated": "2021-11-27 18:18:17.846769",
+            "spec_repo_commit": "3ecdb0c"
         }
     }
 }
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