|
| 1 | +@endpoint(fleet-automation) @endpoint(fleet-automation-v2) |
| 2 | +Feature: Fleet Automation |
| 3 | + Manage automated deployments across your fleet of hosts. Use these |
| 4 | + endpoints to create, retrieve, and cancel deployments that apply |
| 5 | + configuration changes to multiple hosts simultaneously. |
| 6 | + |
| 7 | + Background: |
| 8 | + Given a valid "apiKeyAuth" key in the system |
| 9 | + And a valid "appKeyAuth" key in the system |
| 10 | + And an instance of "FleetAutomation" API |
| 11 | + |
| 12 | + @generated @skip @team:DataDog/fleet-automation |
| 13 | + Scenario: Cancel a configuration deployment returns "Bad Request" response |
| 14 | + Given operation "CancelFleetDeployment" enabled |
| 15 | + And new "CancelFleetDeployment" request |
| 16 | + And request contains "deployment_id" parameter from "REPLACE.ME" |
| 17 | + When the request is sent |
| 18 | + Then the response status is 400 Bad Request |
| 19 | + |
| 20 | + @generated @skip @team:DataDog/fleet-automation |
| 21 | + Scenario: Cancel a configuration deployment returns "Not Found" response |
| 22 | + Given operation "CancelFleetDeployment" enabled |
| 23 | + And new "CancelFleetDeployment" request |
| 24 | + And request contains "deployment_id" parameter from "REPLACE.ME" |
| 25 | + When the request is sent |
| 26 | + Then the response status is 404 Not Found |
| 27 | + |
| 28 | + @generated @skip @team:DataDog/fleet-automation |
| 29 | + Scenario: Cancel a configuration deployment returns "deployment successfully canceled." response |
| 30 | + Given operation "CancelFleetDeployment" enabled |
| 31 | + And new "CancelFleetDeployment" request |
| 32 | + And request contains "deployment_id" parameter from "REPLACE.ME" |
| 33 | + When the request is sent |
| 34 | + Then the response status is 204 deployment successfully canceled. |
| 35 | + |
| 36 | + @generated @skip @team:DataDog/fleet-automation |
| 37 | + Scenario: Create a deployment returns "Bad Request" response |
| 38 | + Given operation "CreateFleetDeploymentConfigure" enabled |
| 39 | + And new "CreateFleetDeploymentConfigure" request |
| 40 | + And body with value {"data": {"attributes": {"config_operations": [{"file_op": "merge-patch", "file_path": "/datadog.yaml", "patch": {"apm_config": {"enabled": true}, "log_level": "debug", "logs_enabled": true}}], "filter_query": "env:prod AND service:web"}, "type": "deployment"}} |
| 41 | + When the request is sent |
| 42 | + Then the response status is 400 Bad Request |
| 43 | + |
| 44 | + @generated @skip @team:DataDog/fleet-automation |
| 45 | + Scenario: Create a deployment returns "CREATED" response |
| 46 | + Given operation "CreateFleetDeploymentConfigure" enabled |
| 47 | + And new "CreateFleetDeploymentConfigure" request |
| 48 | + And body with value {"data": {"attributes": {"config_operations": [{"file_op": "merge-patch", "file_path": "/datadog.yaml", "patch": {"apm_config": {"enabled": true}, "log_level": "debug", "logs_enabled": true}}], "filter_query": "env:prod AND service:web"}, "type": "deployment"}} |
| 49 | + When the request is sent |
| 50 | + Then the response status is 201 CREATED |
| 51 | + |
| 52 | + @generated @skip @team:DataDog/fleet-automation |
| 53 | + Scenario: Get a deployment by ID returns "Bad Request" response |
| 54 | + Given operation "GetFleetDeployment" enabled |
| 55 | + And new "GetFleetDeployment" request |
| 56 | + And request contains "deployment_id" parameter from "REPLACE.ME" |
| 57 | + When the request is sent |
| 58 | + Then the response status is 400 Bad Request |
| 59 | + |
| 60 | + @generated @skip @team:DataDog/fleet-automation |
| 61 | + Scenario: Get a deployment by ID returns "Not Found" response |
| 62 | + Given operation "GetFleetDeployment" enabled |
| 63 | + And new "GetFleetDeployment" request |
| 64 | + And request contains "deployment_id" parameter from "REPLACE.ME" |
| 65 | + When the request is sent |
| 66 | + Then the response status is 404 Not Found |
| 67 | + |
| 68 | + @skip @team:DataDog/fleet-automation |
| 69 | + Scenario: Get a deployment by ID returns "OK" response |
| 70 | + Given operation "GetFleetDeployment" enabled |
| 71 | + And there is a valid "deployment" in the system |
| 72 | + And new "GetFleetDeployment" request |
| 73 | + And request contains "deployment_id" parameter from "deployment.id" |
| 74 | + When the request is sent |
| 75 | + Then the response status is 200 OK |
| 76 | + |
| 77 | + @generated @skip @team:DataDog/fleet-automation |
| 78 | + Scenario: List all deployments returns "Bad Request" response |
| 79 | + Given operation "ListFleetDeployments" enabled |
| 80 | + And new "ListFleetDeployments" request |
| 81 | + When the request is sent |
| 82 | + Then the response status is 400 Bad Request |
| 83 | + |
| 84 | + @generated @skip @team:DataDog/fleet-automation |
| 85 | + Scenario: List all deployments returns "OK" response |
| 86 | + Given operation "ListFleetDeployments" enabled |
| 87 | + And new "ListFleetDeployments" request |
| 88 | + When the request is sent |
| 89 | + Then the response status is 200 OK |
0 commit comments