Skip to content

Commit d1b5c7b

Browse files
author
ci.datadog-api-spec
committed
Regenerate client from commit caa1ae9 of spec repo
1 parent 75f4c7f commit d1b5c7b

24 files changed

+2915
-3290
lines changed

.generator/schemas/v2/openapi.yaml

Lines changed: 840 additions & 2501 deletions
Large diffs are not rendered by default.

features/v2/fleet_automation.feature

Lines changed: 90 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -232,6 +232,48 @@ Feature: Fleet Automation
232232
When the request is sent
233233
Then the response status is 200 OK
234234

235+
@generated @skip @team:DataDog/fleet-automation
236+
Scenario: List all fleet clusters returns "Bad Request" response
237+
Given operation "ListFleetClusters" enabled
238+
And new "ListFleetClusters" request
239+
When the request is sent
240+
Then the response status is 400 Bad Request
241+
242+
@generated @skip @team:DataDog/fleet-automation
243+
Scenario: List all fleet clusters returns "Not Found" response
244+
Given operation "ListFleetClusters" enabled
245+
And new "ListFleetClusters" request
246+
When the request is sent
247+
Then the response status is 404 Not Found
248+
249+
@generated @skip @team:DataDog/fleet-automation
250+
Scenario: List all fleet clusters returns "OK" response
251+
Given operation "ListFleetClusters" enabled
252+
And new "ListFleetClusters" request
253+
When the request is sent
254+
Then the response status is 200 OK
255+
256+
@generated @skip @team:DataDog/fleet-automation
257+
Scenario: List all fleet tracers returns "Bad Request" response
258+
Given operation "ListFleetTracers" enabled
259+
And new "ListFleetTracers" request
260+
When the request is sent
261+
Then the response status is 400 Bad Request
262+
263+
@generated @skip @team:DataDog/fleet-automation
264+
Scenario: List all fleet tracers returns "Not Found" response
265+
Given operation "ListFleetTracers" enabled
266+
And new "ListFleetTracers" request
267+
When the request is sent
268+
Then the response status is 404 Not Found
269+
270+
@generated @skip @team:DataDog/fleet-automation
271+
Scenario: List all fleet tracers returns "OK" response
272+
Given operation "ListFleetTracers" enabled
273+
And new "ListFleetTracers" request
274+
When the request is sent
275+
Then the response status is 200 OK
276+
235277
@generated @skip @team:DataDog/fleet-automation
236278
Scenario: List all schedules returns "Bad Request" response
237279
Given operation "ListFleetSchedules" enabled
@@ -246,6 +288,54 @@ Feature: Fleet Automation
246288
When the request is sent
247289
Then the response status is 200 OK
248290

291+
@generated @skip @team:DataDog/fleet-automation
292+
Scenario: List instrumented pods for a cluster returns "Bad Request" response
293+
Given operation "ListFleetInstrumentedPods" enabled
294+
And new "ListFleetInstrumentedPods" request
295+
And request contains "cluster_name" parameter from "REPLACE.ME"
296+
When the request is sent
297+
Then the response status is 400 Bad Request
298+
299+
@generated @skip @team:DataDog/fleet-automation
300+
Scenario: List instrumented pods for a cluster returns "Not Found" response
301+
Given operation "ListFleetInstrumentedPods" enabled
302+
And new "ListFleetInstrumentedPods" request
303+
And request contains "cluster_name" parameter from "REPLACE.ME"
304+
When the request is sent
305+
Then the response status is 404 Not Found
306+
307+
@generated @skip @team:DataDog/fleet-automation
308+
Scenario: List instrumented pods for a cluster returns "OK" response
309+
Given operation "ListFleetInstrumentedPods" enabled
310+
And new "ListFleetInstrumentedPods" request
311+
And request contains "cluster_name" parameter from "REPLACE.ME"
312+
When the request is sent
313+
Then the response status is 200 OK
314+
315+
@generated @skip @team:DataDog/fleet-automation
316+
Scenario: List tracers for a specific agent returns "Bad Request" response
317+
Given operation "ListFleetAgentTracers" enabled
318+
And new "ListFleetAgentTracers" request
319+
And request contains "agent_key" parameter from "REPLACE.ME"
320+
When the request is sent
321+
Then the response status is 400 Bad Request
322+
323+
@generated @skip @team:DataDog/fleet-automation
324+
Scenario: List tracers for a specific agent returns "Not Found" response
325+
Given operation "ListFleetAgentTracers" enabled
326+
And new "ListFleetAgentTracers" request
327+
And request contains "agent_key" parameter from "REPLACE.ME"
328+
When the request is sent
329+
Then the response status is 404 Not Found
330+
331+
@generated @skip @team:DataDog/fleet-automation
332+
Scenario: List tracers for a specific agent returns "OK" response
333+
Given operation "ListFleetAgentTracers" enabled
334+
And new "ListFleetAgentTracers" request
335+
And request contains "agent_key" parameter from "REPLACE.ME"
336+
When the request is sent
337+
Then the response status is 200 OK
338+
249339
@generated @skip @team:DataDog/fleet-automation
250340
Scenario: Trigger a schedule deployment returns "Bad Request" response
251341
Given operation "TriggerFleetSchedule" enabled

0 commit comments

Comments
 (0)