Regenerate client from commit f7db18b of spec repo (#234)

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.4.1.dev11",
-            "regenerated": "2021-08-06 11:34:02.239847",
-            "spec_repo_commit": "692cbbb"
+            "regenerated": "2021-08-09 14:34:40.606113",
+            "spec_repo_commit": "f7db18b"
         },
         "v2": {
             "apigentools_version": "1.4.1.dev11",
-            "regenerated": "2021-08-06 11:35:31.935726",
-            "spec_repo_commit": "692cbbb"
+            "regenerated": "2021-08-09 14:36:11.659692",
+            "spec_repo_commit": "f7db18b"
         }
     }
 }

features/v1/synthetics.feature

@@ -15,7 +15,7 @@ Feature: Synthetics
     And a valid "appKeyAuth" key in the system
     And an instance of "Synthetics" API
 
-  @replay-only @skip-python @skip-java @skip-ruby
+  @replay-only @skip-java @skip-python @skip-ruby
   Scenario: Client is resilient to enum and oneOf deserialization errors
     Given new "ListTests" request
     When the request is sent

packages/datadog-api-client-v1/models/SLOHistorySLIData.ts

@@ -29,7 +29,7 @@ export class SLOHistorySLIData {
    */
   "group"?: string;
   /**
-   * For `monitor` based SLOs, this includes the aggregated history uptime time series.
+   * For `monitor` based SLOs, this includes the aggregated history as arrays that include time series and uptime data where `0=monitor` is in `OK` state and `1=monitor` is in `alert` state.
    */
   "history"?: Array<Array<number>>;
   /**