Regenerate client from commit 1e692e4 of spec repo

Author: ci.datadog-api-spec

.generator/schemas/v2/openapi.yaml

@@ -232,6 +232,48 @@ Feature: Fleet Automation
     When the request is sent
     Then the response status is 200 OK
 
+  @generated @skip @team:DataDog/fleet-automation
+  Scenario: List all fleet clusters returns "Bad Request" response
+    Given operation "ListFleetClusters" enabled
+    And new "ListFleetClusters" request
+    When the request is sent
+    Then the response status is 400 Bad Request
+
+  @generated @skip @team:DataDog/fleet-automation
+  Scenario: List all fleet clusters returns "Not Found" response
+    Given operation "ListFleetClusters" enabled
+    And new "ListFleetClusters" request
+    When the request is sent
+    Then the response status is 404 Not Found
+
+  @generated @skip @team:DataDog/fleet-automation
+  Scenario: List all fleet clusters returns "OK" response
+    Given operation "ListFleetClusters" enabled
+    And new "ListFleetClusters" request
+    When the request is sent
+    Then the response status is 200 OK
+
+  @generated @skip @team:DataDog/fleet-automation
+  Scenario: List all fleet tracers returns "Bad Request" response
+    Given operation "ListFleetTracers" enabled
+    And new "ListFleetTracers" request
+    When the request is sent
+    Then the response status is 400 Bad Request
+
+  @generated @skip @team:DataDog/fleet-automation
+  Scenario: List all fleet tracers returns "Not Found" response
+    Given operation "ListFleetTracers" enabled
+    And new "ListFleetTracers" request
+    When the request is sent
+    Then the response status is 404 Not Found
+
+  @generated @skip @team:DataDog/fleet-automation
+  Scenario: List all fleet tracers returns "OK" response
+    Given operation "ListFleetTracers" enabled
+    And new "ListFleetTracers" request
+    When the request is sent
+    Then the response status is 200 OK
+
   @generated @skip @team:DataDog/fleet-automation
   Scenario: List all schedules returns "Bad Request" response
     Given operation "ListFleetSchedules" enabled
@@ -246,6 +288,54 @@ Feature: Fleet Automation
     When the request is sent
     Then the response status is 200 OK
 
+  @generated @skip @team:DataDog/fleet-automation
+  Scenario: List instrumented pods for a cluster returns "Bad Request" response
+    Given operation "ListFleetInstrumentedPods" enabled
+    And new "ListFleetInstrumentedPods" request
+    And request contains "cluster_name" parameter from "REPLACE.ME"
+    When the request is sent
+    Then the response status is 400 Bad Request
+
+  @generated @skip @team:DataDog/fleet-automation
+  Scenario: List instrumented pods for a cluster returns "Not Found" response
+    Given operation "ListFleetInstrumentedPods" enabled
+    And new "ListFleetInstrumentedPods" request
+    And request contains "cluster_name" parameter from "REPLACE.ME"
+    When the request is sent
+    Then the response status is 404 Not Found
+
+  @generated @skip @team:DataDog/fleet-automation
+  Scenario: List instrumented pods for a cluster returns "OK" response
+    Given operation "ListFleetInstrumentedPods" enabled
+    And new "ListFleetInstrumentedPods" request
+    And request contains "cluster_name" parameter from "REPLACE.ME"
+    When the request is sent
+    Then the response status is 200 OK
+
+  @generated @skip @team:DataDog/fleet-automation
+  Scenario: List tracers for a specific agent returns "Bad Request" response
+    Given operation "ListFleetAgentTracers" enabled
+    And new "ListFleetAgentTracers" request
+    And request contains "agent_key" parameter from "REPLACE.ME"
+    When the request is sent
+    Then the response status is 400 Bad Request
+
+  @generated @skip @team:DataDog/fleet-automation
+  Scenario: List tracers for a specific agent returns "Not Found" response
+    Given operation "ListFleetAgentTracers" enabled
+    And new "ListFleetAgentTracers" request
+    And request contains "agent_key" parameter from "REPLACE.ME"
+    When the request is sent
+    Then the response status is 404 Not Found
+
+  @generated @skip @team:DataDog/fleet-automation
+  Scenario: List tracers for a specific agent returns "OK" response
+    Given operation "ListFleetAgentTracers" enabled
+    And new "ListFleetAgentTracers" request
+    And request contains "agent_key" parameter from "REPLACE.ME"
+    When the request is sent
+    Then the response status is 200 OK
+
   @generated @skip @team:DataDog/fleet-automation
   Scenario: Trigger a schedule deployment returns "Bad Request" response
     Given operation "TriggerFleetSchedule" enabled

features/v2/fleet_automation.feature

@@ -17,6 +17,24 @@
       "type": "safe"
     }
   },
+  "ListFleetAgentTracers": {
+    "tag": "Fleet Automation",
+    "undo": {
+      "type": "safe"
+    }
+  },
+  "ListFleetClusters": {
+    "tag": "Fleet Automation",
+    "undo": {
+      "type": "safe"
+    }
+  },
+  "ListFleetInstrumentedPods": {
+    "tag": "Fleet Automation",
+    "undo": {
+      "type": "safe"
+    }
+  },
   "ListFleetDeployments": {
     "tag": "Fleet Automation",
     "undo": {
@@ -111,6 +129,12 @@
       "type": "unsafe"
     }
   },
+  "ListFleetTracers": {
+    "tag": "Fleet Automation",
+    "undo": {
+      "type": "safe"
+    }
+  },
   "ListDatastores": {
     "tag": "Actions Datastores",
     "undo": {

features/v2/undo.json

@@ -322,9 +322,8 @@ Then(
 Then(
   "the response {string} does not have field {string}",
   function (this: World, responsePath: string, field: string) {
-    expect(
-      pathLookup(this.response, responsePath)[field.toAttributeName()],
-    ).to.be.undefined;
+    expect(pathLookup(this.response, responsePath)[field.toAttributeName()]).to
+      .be.undefined;
   },
 );
 

private/bdd_runner/src/step_definitions/request_steps.ts

@@ -2391,6 +2391,63 @@ export const ScenariosModelMappings: { [key: string]: OperationMapping } = {
     },
     operationResponseType: "FleetAgentInfoResponse",
   },
+  "FleetAutomationApi.V2.ListFleetAgentTracers": {
+    agentKey: {
+      type: "string",
+      format: "",
+    },
+    pageNumber: {
+      type: "number",
+      format: "int64",
+    },
+    pageSize: {
+      type: "number",
+      format: "int64",
+    },
+    sortAttribute: {
+      type: "string",
+      format: "",
+    },
+    sortDescending: {
+      type: "boolean",
+      format: "",
+    },
+    operationResponseType: "FleetTracersResponse",
+  },
+  "FleetAutomationApi.V2.ListFleetClusters": {
+    pageNumber: {
+      type: "number",
+      format: "int64",
+    },
+    pageSize: {
+      type: "number",
+      format: "int64",
+    },
+    sortAttribute: {
+      type: "string",
+      format: "",
+    },
+    sortDescending: {
+      type: "boolean",
+      format: "",
+    },
+    filter: {
+      type: "string",
+      format: "",
+    },
+    tags: {
+      type: "string",
+      format: "",
+    },
+    operationResponseType: "FleetClustersResponse",
+  },
+  "FleetAutomationApi.V2.ListFleetInstrumentedPods": {
+    clusterName: {
+      type: "string",
+      format: "",
+    },
+    operationResponseType: "FleetInstrumentedPodsResponse",
+  },
   "FleetAutomationApi.V2.ListFleetDeployments": {
     pageSize: {
       type: "number",
@@ -2480,6 +2537,29 @@ export const ScenariosModelMappings: { [key: string]: OperationMapping } = {
     },
     operationResponseType: "FleetDeploymentResponse",
   },
+  "FleetAutomationApi.V2.ListFleetTracers": {
+    pageNumber: {
+      type: "number",
+      format: "int64",
+    },
+    pageSize: {
+      type: "number",
+      format: "int64",
+    },
+    sortAttribute: {
+      type: "string",
+      format: "",
+    },
+    sortDescending: {
+      type: "boolean",
+      format: "",
+    },
+    filter: {
+      type: "string",
+      format: "",
+    },
+    operationResponseType: "FleetTracersResponse",
+  },
   "ActionsDatastoresApi.V2.ListDatastores": {
     operationResponseType: "DatastoreArray",
   },