Regenerate client from commit d6f176b3 of spec repo

DataDog · Feb 20, 2024 · 46a2fb0 · 46a2fb0
1 parent 4aea472
commit 46a2fb0
Show file tree

Hide file tree

Showing 2 changed files with 5 additions and 5 deletions.
diff --git a/.apigentools-info b/.apigentools-info
@@ -4,13 +4,13 @@
     "spec_versions": {
         "v1": {
             "apigentools_version": "1.6.6",
-            "regenerated": "2024-02-20 12:21:47.886534",
-            "spec_repo_commit": "7e467650"
+            "regenerated": "2024-02-20 18:52:04.763983",
+            "spec_repo_commit": "d6f176b3"
         },
         "v2": {
             "apigentools_version": "1.6.6",
-            "regenerated": "2024-02-20 12:21:47.901998",
-            "spec_repo_commit": "7e467650"
+            "regenerated": "2024-02-20 18:52:04.780892",
+            "spec_repo_commit": "d6f176b3"
         }
     }
 }
diff --git a/tests/v2/features/metrics.feature b/tests/v2/features/metrics.feature
@@ -132,7 +132,7 @@ Feature: Metrics
     Then the response status is 200 Success
     And the response "data" has length 0
 
-  @team:DataDog/metrics-experience
+  @replay-only @team:DataDog/metrics-experience
   Scenario: Get a list of metrics with configured filter returns "Success" response
     Given a valid "appKeyAuth" key in the system
     And new "ListTagConfigurations" request