Regenerate client from commit 38f019bb of spec repo

DataDog · Oct 31, 2023 · bc4711d · bc4711d
1 parent 4f79062
commit bc4711d
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": "2023-10-30 20:47:58.772338",
-            "spec_repo_commit": "98cfa2fd"
+            "regenerated": "2023-10-31 15:36:19.500650",
+            "spec_repo_commit": "38f019bb"
         },
         "v2": {
             "apigentools_version": "1.6.6",
-            "regenerated": "2023-10-30 20:47:58.789093",
-            "spec_repo_commit": "98cfa2fd"
+            "regenerated": "2023-10-31 15:36:19.519919",
+            "spec_repo_commit": "38f019bb"
         }
     }
 }
diff --git a/tests/scenarios/features/v2/apm_retention_filters.feature b/tests/scenarios/features/v2/apm_retention_filters.feature
@@ -68,7 +68,7 @@ Feature: APM Retention Filters
     And new "ListApmRetentionFilters" request
     When the request is sent
     Then the response status is 200 OK
-    And the response "data[2].id" has the same value as "retention_filter.data.id"
+    And the response "data" has item with field "id" with value "{{ retention_filter.data.id }}"
 
   @generated @skip @team:DataDog/apm-trace-intake
   Scenario: Re-order retention filters returns "Bad Request" response