|
| 1 | +@endpoint(web-integrations) @endpoint(web-integrations-v2) |
| 2 | +Feature: Web Integrations |
| 3 | + Manage web integration accounts programmatically through the Datadog API. |
| 4 | + See the [Web Integrations page](https://app.datadoghq.com/integrations) |
| 5 | + for more information. |
| 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 "WebIntegrations" API |
| 11 | + |
| 12 | + @generated @skip @team:DataDog/saas-integrations |
| 13 | + Scenario: Create a web integration account returns "Bad Request" response |
| 14 | + Given operation "CreateWebIntegrationAccount" enabled |
| 15 | + And new "CreateWebIntegrationAccount" request |
| 16 | + And request contains "integration_name" parameter from "REPLACE.ME" |
| 17 | + And body with value {"data": {"attributes": {"name": "my-databricks-account", "secrets": {"client_secret": "my-client-secret"}, "settings": {"workspace_url": "https://example.azuredatabricks.net"}}, "type": "Account"}} |
| 18 | + When the request is sent |
| 19 | + Then the response status is 400 Bad Request |
| 20 | + |
| 21 | + @generated @skip @team:DataDog/saas-integrations |
| 22 | + Scenario: Create a web integration account returns "CREATED" response |
| 23 | + Given operation "CreateWebIntegrationAccount" enabled |
| 24 | + And new "CreateWebIntegrationAccount" request |
| 25 | + And request contains "integration_name" parameter from "REPLACE.ME" |
| 26 | + And body with value {"data": {"attributes": {"name": "my-databricks-account", "secrets": {"client_secret": "my-client-secret"}, "settings": {"workspace_url": "https://example.azuredatabricks.net"}}, "type": "Account"}} |
| 27 | + When the request is sent |
| 28 | + Then the response status is 201 CREATED |
| 29 | + |
| 30 | + @generated @skip @team:DataDog/saas-integrations |
| 31 | + Scenario: Create a web integration account returns "Not Found" response |
| 32 | + Given operation "CreateWebIntegrationAccount" enabled |
| 33 | + And new "CreateWebIntegrationAccount" request |
| 34 | + And request contains "integration_name" parameter from "REPLACE.ME" |
| 35 | + And body with value {"data": {"attributes": {"name": "my-databricks-account", "secrets": {"client_secret": "my-client-secret"}, "settings": {"workspace_url": "https://example.azuredatabricks.net"}}, "type": "Account"}} |
| 36 | + When the request is sent |
| 37 | + Then the response status is 404 Not Found |
| 38 | + |
| 39 | + @generated @skip @team:DataDog/saas-integrations |
| 40 | + Scenario: Create a web integration account returns "The server cannot process the request because it contains invalid data." response |
| 41 | + Given operation "CreateWebIntegrationAccount" enabled |
| 42 | + And new "CreateWebIntegrationAccount" request |
| 43 | + And request contains "integration_name" parameter from "REPLACE.ME" |
| 44 | + And body with value {"data": {"attributes": {"name": "my-databricks-account", "secrets": {"client_secret": "my-client-secret"}, "settings": {"workspace_url": "https://example.azuredatabricks.net"}}, "type": "Account"}} |
| 45 | + When the request is sent |
| 46 | + Then the response status is 422 The server cannot process the request because it contains invalid data. |
| 47 | + |
| 48 | + @generated @skip @team:DataDog/saas-integrations |
| 49 | + Scenario: Delete a web integration account returns "Bad Request" response |
| 50 | + Given operation "DeleteWebIntegrationAccount" enabled |
| 51 | + And new "DeleteWebIntegrationAccount" request |
| 52 | + And request contains "integration_name" parameter from "REPLACE.ME" |
| 53 | + And request contains "account_id" parameter from "REPLACE.ME" |
| 54 | + When the request is sent |
| 55 | + Then the response status is 400 Bad Request |
| 56 | + |
| 57 | + @generated @skip @team:DataDog/saas-integrations |
| 58 | + Scenario: Delete a web integration account returns "Not Found" response |
| 59 | + Given operation "DeleteWebIntegrationAccount" enabled |
| 60 | + And new "DeleteWebIntegrationAccount" request |
| 61 | + And request contains "integration_name" parameter from "REPLACE.ME" |
| 62 | + And request contains "account_id" parameter from "REPLACE.ME" |
| 63 | + When the request is sent |
| 64 | + Then the response status is 404 Not Found |
| 65 | + |
| 66 | + @generated @skip @team:DataDog/saas-integrations |
| 67 | + Scenario: Delete a web integration account returns "OK" response |
| 68 | + Given operation "DeleteWebIntegrationAccount" enabled |
| 69 | + And new "DeleteWebIntegrationAccount" request |
| 70 | + And request contains "integration_name" parameter from "REPLACE.ME" |
| 71 | + And request contains "account_id" parameter from "REPLACE.ME" |
| 72 | + When the request is sent |
| 73 | + Then the response status is 204 OK |
| 74 | + |
| 75 | + @generated @skip @team:DataDog/saas-integrations |
| 76 | + Scenario: Get a web integration account returns "Bad Request" response |
| 77 | + Given operation "GetWebIntegrationAccount" enabled |
| 78 | + And new "GetWebIntegrationAccount" request |
| 79 | + And request contains "integration_name" parameter from "REPLACE.ME" |
| 80 | + And request contains "account_id" parameter from "REPLACE.ME" |
| 81 | + When the request is sent |
| 82 | + Then the response status is 400 Bad Request |
| 83 | + |
| 84 | + @generated @skip @team:DataDog/saas-integrations |
| 85 | + Scenario: Get a web integration account returns "Not Found" response |
| 86 | + Given operation "GetWebIntegrationAccount" enabled |
| 87 | + And new "GetWebIntegrationAccount" request |
| 88 | + And request contains "integration_name" parameter from "REPLACE.ME" |
| 89 | + And request contains "account_id" parameter from "REPLACE.ME" |
| 90 | + When the request is sent |
| 91 | + Then the response status is 404 Not Found |
| 92 | + |
| 93 | + @generated @skip @team:DataDog/saas-integrations |
| 94 | + Scenario: Get a web integration account returns "OK" response |
| 95 | + Given operation "GetWebIntegrationAccount" enabled |
| 96 | + And new "GetWebIntegrationAccount" request |
| 97 | + And request contains "integration_name" parameter from "REPLACE.ME" |
| 98 | + And request contains "account_id" parameter from "REPLACE.ME" |
| 99 | + When the request is sent |
| 100 | + Then the response status is 200 OK |
| 101 | + |
| 102 | + @generated @skip @team:DataDog/saas-integrations |
| 103 | + Scenario: List web integration accounts returns "Bad Request" response |
| 104 | + Given operation "ListWebIntegrationAccounts" enabled |
| 105 | + And new "ListWebIntegrationAccounts" request |
| 106 | + And request contains "integration_name" parameter from "REPLACE.ME" |
| 107 | + When the request is sent |
| 108 | + Then the response status is 400 Bad Request |
| 109 | + |
| 110 | + @generated @skip @team:DataDog/saas-integrations |
| 111 | + Scenario: List web integration accounts returns "Not Found" response |
| 112 | + Given operation "ListWebIntegrationAccounts" enabled |
| 113 | + And new "ListWebIntegrationAccounts" request |
| 114 | + And request contains "integration_name" parameter from "REPLACE.ME" |
| 115 | + When the request is sent |
| 116 | + Then the response status is 404 Not Found |
| 117 | + |
| 118 | + @generated @skip @team:DataDog/saas-integrations |
| 119 | + Scenario: List web integration accounts returns "OK" response |
| 120 | + Given operation "ListWebIntegrationAccounts" enabled |
| 121 | + And new "ListWebIntegrationAccounts" request |
| 122 | + And request contains "integration_name" parameter from "REPLACE.ME" |
| 123 | + When the request is sent |
| 124 | + Then the response status is 200 OK |
| 125 | + |
| 126 | + @generated @skip @team:DataDog/saas-integrations |
| 127 | + Scenario: Update a web integration account returns "Bad Request" response |
| 128 | + Given operation "UpdateWebIntegrationAccount" enabled |
| 129 | + And new "UpdateWebIntegrationAccount" request |
| 130 | + And request contains "integration_name" parameter from "REPLACE.ME" |
| 131 | + And request contains "account_id" parameter from "REPLACE.ME" |
| 132 | + And body with value {"data": {"attributes": {"name": "my-databricks-account", "secrets": {"client_secret": "my-client-secret"}, "settings": {"workspace_url": "https://example.azuredatabricks.net"}}, "type": "Account"}} |
| 133 | + When the request is sent |
| 134 | + Then the response status is 400 Bad Request |
| 135 | + |
| 136 | + @generated @skip @team:DataDog/saas-integrations |
| 137 | + Scenario: Update a web integration account returns "Not Found" response |
| 138 | + Given operation "UpdateWebIntegrationAccount" enabled |
| 139 | + And new "UpdateWebIntegrationAccount" request |
| 140 | + And request contains "integration_name" parameter from "REPLACE.ME" |
| 141 | + And request contains "account_id" parameter from "REPLACE.ME" |
| 142 | + And body with value {"data": {"attributes": {"name": "my-databricks-account", "secrets": {"client_secret": "my-client-secret"}, "settings": {"workspace_url": "https://example.azuredatabricks.net"}}, "type": "Account"}} |
| 143 | + When the request is sent |
| 144 | + Then the response status is 404 Not Found |
| 145 | + |
| 146 | + @generated @skip @team:DataDog/saas-integrations |
| 147 | + Scenario: Update a web integration account returns "OK" response |
| 148 | + Given operation "UpdateWebIntegrationAccount" enabled |
| 149 | + And new "UpdateWebIntegrationAccount" request |
| 150 | + And request contains "integration_name" parameter from "REPLACE.ME" |
| 151 | + And request contains "account_id" parameter from "REPLACE.ME" |
| 152 | + And body with value {"data": {"attributes": {"name": "my-databricks-account", "secrets": {"client_secret": "my-client-secret"}, "settings": {"workspace_url": "https://example.azuredatabricks.net"}}, "type": "Account"}} |
| 153 | + When the request is sent |
| 154 | + Then the response status is 200 OK |
| 155 | + |
| 156 | + @generated @skip @team:DataDog/saas-integrations |
| 157 | + Scenario: Update a web integration account returns "The server cannot process the request because it contains invalid data." response |
| 158 | + Given operation "UpdateWebIntegrationAccount" enabled |
| 159 | + And new "UpdateWebIntegrationAccount" request |
| 160 | + And request contains "integration_name" parameter from "REPLACE.ME" |
| 161 | + And request contains "account_id" parameter from "REPLACE.ME" |
| 162 | + And body with value {"data": {"attributes": {"name": "my-databricks-account", "secrets": {"client_secret": "my-client-secret"}, "settings": {"workspace_url": "https://example.azuredatabricks.net"}}, "type": "Account"}} |
| 163 | + When the request is sent |
| 164 | + Then the response status is 422 The server cannot process the request because it contains invalid data. |
0 commit comments