Update logs submission timestamp info (#1407)

Co-authored-by: ci.datadog-api-spec <[email protected]>

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

.apigentools-info

@@ -4,13 +4,13 @@
     "spec_versions": {
         "v1": {
             "apigentools_version": "1.6.4",
-            "regenerated": "2023-05-04 19:21:05.351305",
-            "spec_repo_commit": "c0cc4b41"
+            "regenerated": "2023-05-04 20:08:39.268868",
+            "spec_repo_commit": "ff8b9894"
         },
         "v2": {
             "apigentools_version": "1.6.4",
-            "regenerated": "2023-05-04 19:21:05.364430",
-            "spec_repo_commit": "c0cc4b41"
+            "regenerated": "2023-05-04 20:08:39.281631",
+            "spec_repo_commit": "ff8b9894"
         }
     }
 }

.generator/schemas/v2/openapi.yaml

@@ -17702,8 +17702,8 @@ paths:
         Add the `Content-Encoding: gzip` header to the request when sending compressed
         logs.
 
-        Log events can be submitted up to 18 hours in the past and 2 hours in the
-        future.
+        Log events can be submitted with a timestamp that is up to 18 hours in the
+        past.
 
 
         The status codes answered by the HTTP API are:

src/datadog_api_client/v2/api/logs_api.py

@@ -460,7 +460,7 @@ def submit_log(
 
         Datadog recommends sending your logs compressed.
         Add the ``Content-Encoding: gzip`` header to the request when sending compressed logs.
-        Log events can be submitted up to 18 hours in the past and 2 hours in the future.
+        Log events can be submitted with a timestamp that is up to 18 hours in the past.
 
         The status codes answered by the HTTP API are: