Regenerate client from commit 060dc917 of spec repo

.apigentools-info

@@ -4,13 +4,13 @@
     "spec_versions": {
         "v1": {
             "apigentools_version": "1.6.4",
-            "regenerated": "2023-06-01 14:05:08.660999",
-            "spec_repo_commit": "c70ecd2f"
+            "regenerated": "2023-06-05 14:46:47.877237",
+            "spec_repo_commit": "060dc917"
         },
         "v2": {
             "apigentools_version": "1.6.4",
-            "regenerated": "2023-06-01 14:05:08.676337",
-            "spec_repo_commit": "c70ecd2f"
+            "regenerated": "2023-06-05 14:46:47.891094",
+            "spec_repo_commit": "060dc917"
         }
     }
 }

cassettes/features/v2/metrics/List-active-tags-and-aggregations-returns-Success-response.frozen

@@ -1 +1 @@
-2022-09-01T12:00:27.800Z
+2023-06-05T14:44:05.398Z

cassettes/features/v2/metrics/List-distinct-metric-volumes-by-metric-name-returns-Success-response.frozen

@@ -1 +1 @@
-2022-05-12T11:28:32.184Z
+2023-06-02T15:15:47.326Z

examples/v2/metrics/ListActiveMetricConfigurations.rb

@@ -2,4 +2,4 @@
 
 require "datadog_api_client"
 api_instance = DatadogAPIClient::V2::MetricsAPI.new
-p api_instance.list_active_metric_configurations("ExampleMetric")
+p api_instance.list_active_metric_configurations("static_test_metric_donotdelete")

examples/v2/metrics/ListVolumesByMetricName.rb

@@ -2,4 +2,4 @@
 
 require "datadog_api_client"
 api_instance = DatadogAPIClient::V2::MetricsAPI.new
-p api_instance.list_volumes_by_metric_name("ExampleMetric")
+p api_instance.list_volumes_by_metric_name("static_test_metric_donotdelete")

features/v1/given.json

@@ -159,6 +159,18 @@
     "tag": "Metrics",
     "operationId": "SubmitMetrics"
   },
+  {
+    "parameters": [
+      {
+        "name": "body",
+        "value": "{\n  \"series\": [\n    {\n      \"metric\": \"static_test_metric_donotdelete\",\n      \"type\": \"gauge\",\n      \"points\": [\n        [\n          {{ timestamp(\"now\") }},\n          1.1\n        ]\n      ],\n      \"tags\": [\n        \"test:static_test_metric_donotdelete\"\n      ]\n    }\n  ]\n}\n"
+      }
+    ],
+    "step": "there is a valid \"metric_static\" in the system",
+    "key": "metric_static",
+    "tag": "Metrics",
+    "operationId": "SubmitMetrics"
+  },
   {
     "parameters": [
       {

features/v1/metric_payload_static.json

@@ -0,0 +1,17 @@
+{
+  "series": [
+    {
+      "metric": "static_test_metric_donotdelete",
+      "type": "gauge",
+      "points": [
+        [
+          {{ timestamp("now") }},
+          1.1
+        ]
+      ],
+      "tags": [
+        "test:static_test_metric_donotdelete"
+      ]
+    }
+  ]
+}

features/v2/metrics.feature

@@ -160,12 +160,13 @@ Feature: Metrics
   @skip-validation @team:DataDog/metrics-experience
   Scenario: List active tags and aggregations returns "Success" response
     Given a valid "appKeyAuth" key in the system
-    And there is a valid "metric" in the system
+    And there is a valid "metric_static" in the system
     And new "ListActiveMetricConfigurations" request
-    And request contains "metric_name" parameter with value "{{ unique_alnum }}"
+    And request contains "metric_name" parameter with value "static_test_metric_donotdelete"
     When the request is sent
     Then the response status is 200 Success
     And the response "data.type" is equal to "actively_queried_configurations"
+    And the response "data.id" is equal to "static_test_metric_donotdelete"
 
   @generated @skip @team:DataDog/metrics-experience
   Scenario: List distinct metric volumes by metric name returns "Bad Request" response
@@ -186,13 +187,13 @@ Feature: Metrics
   @skip-validation @team:DataDog/metrics-experience
   Scenario: List distinct metric volumes by metric name returns "Success" response
     Given a valid "appKeyAuth" key in the system
-    And there is a valid "metric" in the system
-    And there is a valid "metric_tag_configuration" in the system
+    And there is a valid "metric_static" in the system
     And new "ListVolumesByMetricName" request
-    And request contains "metric_name" parameter with value "{{ unique_alnum }}"
+    And request contains "metric_name" parameter with value "static_test_metric_donotdelete"
     When the request is sent
     Then the response status is 200 Success
     And the response "data.type" is equal to "metric_volumes"
+    And the response "data.id" is equal to "static_test_metric_donotdelete"
 
   @generated @skip @team:DataDog/metrics-experience
   Scenario: List tag configuration by name returns "Not Found" response