Regenerate client from commit e1764101 of spec repo (#998)

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-17 14:59:00.575916",
-            "spec_repo_commit": "6f5f750c"
+            "regenerated": "2022-05-18 14:23:46.312017",
+            "spec_repo_commit": "e1764101"
         },
         "v2": {
             "apigentools_version": "1.6.2",
-            "regenerated": "2022-05-17 14:59:00.587584",
-            "spec_repo_commit": "6f5f750c"
+            "regenerated": "2022-05-18 14:23:46.328977",
+            "spec_repo_commit": "e1764101"
         }
     }
 }

.generator/schemas/v2/openapi.yaml

@@ -9752,12 +9752,13 @@ paths:
         type: safe
   /api/v2/metrics/{metric_name}/estimate:
     get:
-      description: Returns a cardinality estimate for a metric with a given tag, percentile,
-        and number of aggregations configuration.
+      description: Returns the estimated cardinality for a metric with a given tag,
+        percentile and number of aggregations configuration using Metrics without
+        Limits™.
       operationId: EstimateMetricsOutputSeries
       parameters:
       - $ref: '#/components/parameters/MetricName'
-      - description: Filtered tag groups that the metric is configured to query with.
+      - description: Filtered tag keys that the metric is configured to query with.
         example: app,host
         in: query
         name: filter[groups]
@@ -9831,7 +9832,7 @@ paths:
       - apiKeyAuth: []
         appKeyAuth: []
       - AuthZ: []
-      summary: Estimate Output Series - Public v2 API
+      summary: Tag Configuration Cardinality Estimator
       tags:
       - Metrics
       x-dd-ownership:

examples/v2/metrics/EstimateMetricsOutputSeries.py

@@ -1,5 +1,5 @@
 """
-Estimate Output Series - Public v2 API returns "Success" response
+Tag Configuration Cardinality Estimator returns "Success" response
 """
 
 from datadog_api_client.v2 import ApiClient, Configuration

src/datadog_api_client/v2/api/metrics_api.py

@@ -89,23 +89,6 @@ Feature: Metrics
     When the request is sent
     Then the response status is 404 Not found
 
-  @generated @skip @team:DataDog/points-aggregation
-  Scenario: Estimate Output Series - Public v2 API returns "API error response." response
-    Given a valid "appKeyAuth" key in the system
-    And new "EstimateMetricsOutputSeries" request
-    And request contains "metric_name" parameter from "REPLACE.ME"
-    When the request is sent
-    Then the response status is 404 API error response.
-
-  @replay-only @team:DataDog/points-aggregation
-  Scenario: Estimate Output Series - Public v2 API returns "Success" response
-    Given new "EstimateMetricsOutputSeries" request
-    And request contains "metric_name" parameter with value "system.cpu.idle"
-    And request contains "filter[groups]" parameter with value "app,host"
-    And request contains "filter[num_aggregations]" parameter with value 4
-    When the request is sent
-    Then the response status is 200 Success
-
   @generated @skip @team:DataDog/points-aggregation
   Scenario: List distinct metric volumes by metric name returns "Bad Request" response
     Given a valid "appKeyAuth" key in the system
@@ -243,6 +226,23 @@ Feature: Metrics
     When the request is sent
     Then the response status is 408 Request timeout
 
+  @generated @skip @team:DataDog/points-aggregation
+  Scenario: Tag Configuration Cardinality Estimator returns "API error response." response
+    Given a valid "appKeyAuth" key in the system
+    And new "EstimateMetricsOutputSeries" request
+    And request contains "metric_name" parameter from "REPLACE.ME"
+    When the request is sent
+    Then the response status is 404 API error response.
+
+  @replay-only @team:DataDog/points-aggregation
+  Scenario: Tag Configuration Cardinality Estimator returns "Success" response
+    Given new "EstimateMetricsOutputSeries" request
+    And request contains "metric_name" parameter with value "system.cpu.idle"
+    And request contains "filter[groups]" parameter with value "app,host"
+    And request contains "filter[num_aggregations]" parameter with value 4
+    When the request is sent
+    Then the response status is 200 Success
+
   @generated @skip @team:DataDog/points-aggregation
   Scenario: Update a tag configuration returns "Bad Request" response
     Given a valid "appKeyAuth" key in the system