diff --git a/.apigentools-info b/.apigentools-info index 67b3bf7598a..9f71db5277f 100644 --- a/.apigentools-info +++ b/.apigentools-info @@ -4,13 +4,13 @@ "spec_versions": { "v1": { "apigentools_version": "1.6.6", - "regenerated": "2024-01-25 15:52:44.093364", - "spec_repo_commit": "bdb7b215" + "regenerated": "2024-01-25 20:06:15.455125", + "spec_repo_commit": "29ecc007" }, "v2": { "apigentools_version": "1.6.6", - "regenerated": "2024-01-25 15:52:44.107943", - "spec_repo_commit": "bdb7b215" + "regenerated": "2024-01-25 20:06:15.472532", + "spec_repo_commit": "29ecc007" } } } \ No newline at end of file diff --git a/tests/scenarios/features/v1/pagerduty_integration.feature b/tests/scenarios/features/v1/pagerduty_integration.feature index df786f66c6f..96fce416874 100644 --- a/tests/scenarios/features/v1/pagerduty_integration.feature +++ b/tests/scenarios/features/v1/pagerduty_integration.feature @@ -9,49 +9,49 @@ Feature: PagerDuty Integration And a valid "appKeyAuth" key in the system And an instance of "PagerDutyIntegration" API - @generated @skip @team:Datadog/web-integrations + @generated @skip @team:DataDog/saas-integrations @team:DataDog/web-integrations Scenario: Create a new service object returns "Bad Request" response Given new "CreatePagerDutyIntegrationService" request And body with value {"service_key": "", "service_name": ""} When the request is sent Then the response status is 400 Bad Request - @generated @skip @team:Datadog/web-integrations + @generated @skip @team:DataDog/saas-integrations @team:DataDog/web-integrations Scenario: Create a new service object returns "OK" response Given new "CreatePagerDutyIntegrationService" request And body with value {"service_key": "", "service_name": ""} When the request is sent Then the response status is 201 OK - @generated @skip @team:Datadog/web-integrations + @generated @skip @team:DataDog/saas-integrations @team:DataDog/web-integrations Scenario: Delete a single service object returns "Item Not Found" response Given new "DeletePagerDutyIntegrationService" request And request contains "service_name" parameter from "REPLACE.ME" When the request is sent Then the response status is 404 Item Not Found - @generated @skip @team:Datadog/web-integrations + @generated @skip @team:DataDog/saas-integrations @team:DataDog/web-integrations Scenario: Delete a single service object returns "No Content" response Given new "DeletePagerDutyIntegrationService" request And request contains "service_name" parameter from "REPLACE.ME" When the request is sent Then the response status is 204 No Content - @generated @skip @team:Datadog/web-integrations + @generated @skip @team:DataDog/saas-integrations @team:DataDog/web-integrations Scenario: Get a single service object returns "Item Not Found" response Given new "GetPagerDutyIntegrationService" request And request contains "service_name" parameter from "REPLACE.ME" When the request is sent Then the response status is 404 Item Not Found - @generated @skip @team:Datadog/web-integrations + @generated @skip @team:DataDog/saas-integrations @team:DataDog/web-integrations Scenario: Get a single service object returns "OK" response Given new "GetPagerDutyIntegrationService" request And request contains "service_name" parameter from "REPLACE.ME" When the request is sent Then the response status is 200 OK - @generated @skip @team:Datadog/web-integrations + @generated @skip @team:DataDog/saas-integrations @team:DataDog/web-integrations Scenario: Update a single service object returns "Bad Request" response Given new "UpdatePagerDutyIntegrationService" request And request contains "service_name" parameter from "REPLACE.ME" @@ -59,7 +59,7 @@ Feature: PagerDuty Integration When the request is sent Then the response status is 400 Bad Request - @generated @skip @team:Datadog/web-integrations + @generated @skip @team:DataDog/saas-integrations @team:DataDog/web-integrations Scenario: Update a single service object returns "Item Not Found" response Given new "UpdatePagerDutyIntegrationService" request And request contains "service_name" parameter from "REPLACE.ME" @@ -67,7 +67,7 @@ Feature: PagerDuty Integration When the request is sent Then the response status is 404 Item Not Found - @generated @skip @team:Datadog/web-integrations + @generated @skip @team:DataDog/saas-integrations @team:DataDog/web-integrations Scenario: Update a single service object returns "OK" response Given new "UpdatePagerDutyIntegrationService" request And request contains "service_name" parameter from "REPLACE.ME" diff --git a/tests/scenarios/features/v1/slack_integration.feature b/tests/scenarios/features/v1/slack_integration.feature index d6e8e86cd08..2235888ee60 100644 --- a/tests/scenarios/features/v1/slack_integration.feature +++ b/tests/scenarios/features/v1/slack_integration.feature @@ -9,7 +9,7 @@ Feature: Slack Integration And a valid "appKeyAuth" key in the system And an instance of "SlackIntegration" API - @generated @skip @team:Datadog/web-integrations + @generated @skip @team:DataDog/saas-integrations @team:DataDog/web-integrations Scenario: Create a Slack integration channel returns "Bad Request" response Given new "CreateSlackIntegrationChannel" request And request contains "account_name" parameter from "REPLACE.ME" @@ -17,7 +17,7 @@ Feature: Slack Integration When the request is sent Then the response status is 400 Bad Request - @generated @skip @team:Datadog/web-integrations + @generated @skip @team:DataDog/saas-integrations @team:DataDog/web-integrations Scenario: Create a Slack integration channel returns "Item Not Found" response Given new "CreateSlackIntegrationChannel" request And request contains "account_name" parameter from "REPLACE.ME" @@ -25,7 +25,7 @@ Feature: Slack Integration When the request is sent Then the response status is 404 Item Not Found - @generated @skip @team:Datadog/web-integrations + @generated @skip @team:DataDog/saas-integrations @team:DataDog/web-integrations Scenario: Create a Slack integration channel returns "OK" response Given new "CreateSlackIntegrationChannel" request And request contains "account_name" parameter from "REPLACE.ME" @@ -33,7 +33,7 @@ Feature: Slack Integration When the request is sent Then the response status is 200 OK - @generated @skip @team:Datadog/web-integrations + @generated @skip @team:DataDog/saas-integrations @team:DataDog/web-integrations Scenario: Get a Slack integration channel returns "Bad Request" response Given new "GetSlackIntegrationChannel" request And request contains "account_name" parameter from "REPLACE.ME" @@ -41,7 +41,7 @@ Feature: Slack Integration When the request is sent Then the response status is 400 Bad Request - @generated @skip @team:Datadog/web-integrations + @generated @skip @team:DataDog/saas-integrations @team:DataDog/web-integrations Scenario: Get a Slack integration channel returns "Item Not Found" response Given new "GetSlackIntegrationChannel" request And request contains "account_name" parameter from "REPLACE.ME" @@ -49,7 +49,7 @@ Feature: Slack Integration When the request is sent Then the response status is 404 Item Not Found - @generated @skip @team:Datadog/web-integrations + @generated @skip @team:DataDog/saas-integrations @team:DataDog/web-integrations Scenario: Get a Slack integration channel returns "OK" response Given new "GetSlackIntegrationChannel" request And request contains "account_name" parameter from "REPLACE.ME" @@ -57,28 +57,28 @@ Feature: Slack Integration When the request is sent Then the response status is 200 OK - @generated @skip @team:Datadog/web-integrations + @generated @skip @team:DataDog/saas-integrations @team:DataDog/web-integrations Scenario: Get all channels in a Slack integration returns "Bad Request" response Given new "GetSlackIntegrationChannels" request And request contains "account_name" parameter from "REPLACE.ME" When the request is sent Then the response status is 400 Bad Request - @generated @skip @team:Datadog/web-integrations + @generated @skip @team:DataDog/saas-integrations @team:DataDog/web-integrations Scenario: Get all channels in a Slack integration returns "Item Not Found" response Given new "GetSlackIntegrationChannels" request And request contains "account_name" parameter from "REPLACE.ME" When the request is sent Then the response status is 404 Item Not Found - @generated @skip @team:Datadog/web-integrations + @generated @skip @team:DataDog/saas-integrations @team:DataDog/web-integrations Scenario: Get all channels in a Slack integration returns "OK" response Given new "GetSlackIntegrationChannels" request And request contains "account_name" parameter from "REPLACE.ME" When the request is sent Then the response status is 200 OK - @generated @skip @team:Datadog/web-integrations + @generated @skip @team:DataDog/saas-integrations @team:DataDog/web-integrations Scenario: Remove a Slack integration channel returns "Bad Request" response Given new "RemoveSlackIntegrationChannel" request And request contains "account_name" parameter from "REPLACE.ME" @@ -86,7 +86,7 @@ Feature: Slack Integration When the request is sent Then the response status is 400 Bad Request - @generated @skip @team:Datadog/web-integrations + @generated @skip @team:DataDog/saas-integrations @team:DataDog/web-integrations Scenario: Remove a Slack integration channel returns "Item Not Found" response Given new "RemoveSlackIntegrationChannel" request And request contains "account_name" parameter from "REPLACE.ME" @@ -94,7 +94,7 @@ Feature: Slack Integration When the request is sent Then the response status is 404 Item Not Found - @generated @skip @team:Datadog/web-integrations + @generated @skip @team:DataDog/saas-integrations @team:DataDog/web-integrations Scenario: Remove a Slack integration channel returns "The channel was removed successfully." response Given new "RemoveSlackIntegrationChannel" request And request contains "account_name" parameter from "REPLACE.ME" @@ -102,7 +102,7 @@ Feature: Slack Integration When the request is sent Then the response status is 204 The channel was removed successfully. - @generated @skip @team:Datadog/web-integrations + @generated @skip @team:DataDog/saas-integrations @team:DataDog/web-integrations Scenario: Update a Slack integration channel returns "Bad Request" response Given new "UpdateSlackIntegrationChannel" request And request contains "account_name" parameter from "REPLACE.ME" @@ -111,7 +111,7 @@ Feature: Slack Integration When the request is sent Then the response status is 400 Bad Request - @generated @skip @team:Datadog/web-integrations + @generated @skip @team:DataDog/saas-integrations @team:DataDog/web-integrations Scenario: Update a Slack integration channel returns "Item Not Found" response Given new "UpdateSlackIntegrationChannel" request And request contains "account_name" parameter from "REPLACE.ME" @@ -120,7 +120,7 @@ Feature: Slack Integration When the request is sent Then the response status is 404 Item Not Found - @generated @skip @team:Datadog/web-integrations + @generated @skip @team:DataDog/saas-integrations @team:DataDog/web-integrations Scenario: Update a Slack integration channel returns "OK" response Given new "UpdateSlackIntegrationChannel" request And request contains "account_name" parameter from "REPLACE.ME" diff --git a/tests/scenarios/features/v2/cloudflare_integration.feature b/tests/scenarios/features/v2/cloudflare_integration.feature index 281dbcf9f2f..b988ec92a14 100644 --- a/tests/scenarios/features/v2/cloudflare_integration.feature +++ b/tests/scenarios/features/v2/cloudflare_integration.feature @@ -10,28 +10,28 @@ Feature: Cloudflare Integration And a valid "appKeyAuth" key in the system And an instance of "CloudflareIntegration" API - @generated @skip @team:Datadog/web-integrations + @generated @skip @team:DataDog/saas-integrations @team:DataDog/web-integrations Scenario: Add Cloudflare account returns "Bad Request" response Given new "CreateCloudflareAccount" request And body with value {"data": {"attributes": {"api_key": "a94a8fe5ccb19ba61c4c0873d391e987982fbbd3", "email": "test-email@example.com", "name": "test-name", "resources": ["web", "dns"], "zones": ["zone_id_1", "zone_id_2"]}, "type": "cloudflare-accounts"}} When the request is sent Then the response status is 400 Bad Request - @replay-only @team:Datadog/web-integrations + @replay-only @team:DataDog/saas-integrations @team:DataDog/web-integrations Scenario: Add Cloudflare account returns "Bad Request" response due to missing email Given new "CreateCloudflareAccount" request And body with value {"data": {"attributes": {"api_key": "fakekey", "name": "{{ unique_lower_alnum }}"}, "type": "cloudflare-accounts"}} When the request is sent Then the response status is 400 Bad Request - @replay-only @team:Datadog/web-integrations + @replay-only @team:DataDog/saas-integrations @team:DataDog/web-integrations Scenario: Add Cloudflare account returns "Bad Request" response using invalid auth key Given new "CreateCloudflareAccount" request And body with value {"data": {"attributes": {"api_key": "aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa", "name": "{{ unique_lower_alnum }}"}, "type": "cloudflare-accounts"}} When the request is sent Then the response status is 400 Bad Request - @replay-only @team:Datadog/web-integrations + @replay-only @team:DataDog/saas-integrations @team:DataDog/web-integrations Scenario: Add Cloudflare account returns "CREATED" response Given new "CreateCloudflareAccount" request And body with value {"data": {"attributes": {"api_key": "fakekey", "email": "dev@datadoghq.com", "name": "{{ unique_lower_alnum }}"}, "type": "cloudflare-accounts"}} @@ -41,49 +41,49 @@ Feature: Cloudflare Integration And the response "data.attributes.email" is equal to "dev@datadoghq.com" And the response "data.attributes.name" is equal to "{{ unique_lower_alnum }}" - @generated @skip @team:Datadog/web-integrations + @generated @skip @team:DataDog/saas-integrations @team:DataDog/web-integrations Scenario: Add Cloudflare account returns "Not Found" response Given new "CreateCloudflareAccount" request And body with value {"data": {"attributes": {"api_key": "a94a8fe5ccb19ba61c4c0873d391e987982fbbd3", "email": "test-email@example.com", "name": "test-name", "resources": ["web", "dns"], "zones": ["zone_id_1", "zone_id_2"]}, "type": "cloudflare-accounts"}} When the request is sent Then the response status is 404 Not Found - @generated @skip @team:Datadog/web-integrations + @generated @skip @team:DataDog/saas-integrations @team:DataDog/web-integrations Scenario: Delete Cloudflare account returns "Bad Request" response Given new "DeleteCloudflareAccount" request And request contains "account_id" parameter from "REPLACE.ME" When the request is sent Then the response status is 400 Bad Request - @generated @skip @team:Datadog/web-integrations + @generated @skip @team:DataDog/saas-integrations @team:DataDog/web-integrations Scenario: Delete Cloudflare account returns "Not Found" response Given new "DeleteCloudflareAccount" request And request contains "account_id" parameter from "REPLACE.ME" When the request is sent Then the response status is 404 Not Found - @generated @skip @team:Datadog/web-integrations + @generated @skip @team:DataDog/saas-integrations @team:DataDog/web-integrations Scenario: Delete Cloudflare account returns "OK" response Given new "DeleteCloudflareAccount" request And request contains "account_id" parameter from "REPLACE.ME" When the request is sent Then the response status is 204 OK - @generated @skip @team:Datadog/web-integrations + @generated @skip @team:DataDog/saas-integrations @team:DataDog/web-integrations Scenario: Get Cloudflare account returns "Bad Request" response Given new "GetCloudflareAccount" request And request contains "account_id" parameter from "REPLACE.ME" When the request is sent Then the response status is 400 Bad Request - @generated @skip @team:Datadog/web-integrations + @generated @skip @team:DataDog/saas-integrations @team:DataDog/web-integrations Scenario: Get Cloudflare account returns "Not Found" response Given new "GetCloudflareAccount" request And request contains "account_id" parameter from "REPLACE.ME" When the request is sent Then the response status is 404 Not Found - @replay-only @team:Datadog/web-integrations + @replay-only @team:DataDog/saas-integrations @team:DataDog/web-integrations Scenario: Get Cloudflare account returns "OK" response Given there is a valid "cloudflare_account" in the system And new "GetCloudflareAccount" request @@ -94,19 +94,19 @@ Feature: Cloudflare Integration And the response "data.attributes.email" is equal to "dev@datadog.com" And the response "data.attributes.name" is equal to "{{ unique_lower_alnum }}" - @generated @skip @team:Datadog/web-integrations + @generated @skip @team:DataDog/saas-integrations @team:DataDog/web-integrations Scenario: List Cloudflare accounts returns "Bad Request" response Given new "ListCloudflareAccounts" request When the request is sent Then the response status is 400 Bad Request - @generated @skip @team:Datadog/web-integrations + @generated @skip @team:DataDog/saas-integrations @team:DataDog/web-integrations Scenario: List Cloudflare accounts returns "Not Found" response Given new "ListCloudflareAccounts" request When the request is sent Then the response status is 404 Not Found - @replay-only @team:Datadog/web-integrations + @replay-only @team:DataDog/saas-integrations @team:DataDog/web-integrations Scenario: List Cloudflare accounts returns "OK" response Given there is a valid "cloudflare_account" in the system And new "ListCloudflareAccounts" request @@ -114,7 +114,7 @@ Feature: Cloudflare Integration Then the response status is 200 OK And the response "data[0].type" is equal to "cloudflare-accounts" - @generated @skip @team:Datadog/web-integrations + @generated @skip @team:DataDog/saas-integrations @team:DataDog/web-integrations Scenario: Update Cloudflare account returns "Bad Request" response Given new "UpdateCloudflareAccount" request And request contains "account_id" parameter from "REPLACE.ME" @@ -122,7 +122,7 @@ Feature: Cloudflare Integration When the request is sent Then the response status is 400 Bad Request - @replay-only @team:Datadog/web-integrations + @replay-only @team:DataDog/saas-integrations @team:DataDog/web-integrations Scenario: Update Cloudflare account returns "Bad Request" response due to invalid api key Given there is a valid "cloudflare_account" in the system And new "UpdateCloudflareAccount" request @@ -131,7 +131,7 @@ Feature: Cloudflare Integration When the request is sent Then the response status is 400 Bad Request - @replay-only @team:Datadog/web-integrations + @replay-only @team:DataDog/saas-integrations @team:DataDog/web-integrations Scenario: Update Cloudflare account returns "Bad Request" response due to missing required email Given there is a valid "cloudflare_account" in the system And new "UpdateCloudflareAccount" request @@ -140,7 +140,7 @@ Feature: Cloudflare Integration When the request is sent Then the response status is 400 Bad Request - @generated @skip @team:Datadog/web-integrations + @generated @skip @team:DataDog/saas-integrations @team:DataDog/web-integrations Scenario: Update Cloudflare account returns "Not Found" response Given new "UpdateCloudflareAccount" request And request contains "account_id" parameter from "REPLACE.ME" @@ -148,7 +148,7 @@ Feature: Cloudflare Integration When the request is sent Then the response status is 404 Not Found - @replay-only @team:Datadog/web-integrations + @replay-only @team:DataDog/saas-integrations @team:DataDog/web-integrations Scenario: Update Cloudflare account returns "OK" response Given there is a valid "cloudflare_account" in the system And new "UpdateCloudflareAccount" request diff --git a/tests/scenarios/features/v2/confluent_cloud.feature b/tests/scenarios/features/v2/confluent_cloud.feature index a936d45c1fd..498db076a06 100644 --- a/tests/scenarios/features/v2/confluent_cloud.feature +++ b/tests/scenarios/features/v2/confluent_cloud.feature @@ -8,28 +8,28 @@ Feature: Confluent Cloud And a valid "appKeyAuth" key in the system And an instance of "ConfluentCloud" API - @generated @skip @team:Datadog/web-integrations + @generated @skip @team:DataDog/saas-integrations @team:DataDog/web-integrations Scenario: Add Confluent account returns "Bad Request" response Given new "CreateConfluentAccount" request And body with value {"data": {"attributes": {"api_key": "TESTAPIKEY123", "api_secret": "test-api-secret-123", "resources": [{"enable_custom_metrics": false, "id": "resource-id-123", "resource_type": "kafka", "tags": ["myTag", "myTag2:myValue"]}], "tags": ["myTag", "myTag2:myValue"]}, "type": "confluent-cloud-accounts"}} When the request is sent Then the response status is 400 Bad Request - @generated @skip @team:Datadog/web-integrations + @generated @skip @team:DataDog/saas-integrations @team:DataDog/web-integrations Scenario: Add Confluent account returns "Not Found" response Given new "CreateConfluentAccount" request And body with value {"data": {"attributes": {"api_key": "TESTAPIKEY123", "api_secret": "test-api-secret-123", "resources": [{"enable_custom_metrics": false, "id": "resource-id-123", "resource_type": "kafka", "tags": ["myTag", "myTag2:myValue"]}], "tags": ["myTag", "myTag2:myValue"]}, "type": "confluent-cloud-accounts"}} When the request is sent Then the response status is 404 Not Found - @generated @skip @team:Datadog/web-integrations + @generated @skip @team:DataDog/saas-integrations @team:DataDog/web-integrations Scenario: Add Confluent account returns "OK" response Given new "CreateConfluentAccount" request And body with value {"data": {"attributes": {"api_key": "TESTAPIKEY123", "api_secret": "test-api-secret-123", "resources": [{"enable_custom_metrics": false, "id": "resource-id-123", "resource_type": "kafka", "tags": ["myTag", "myTag2:myValue"]}], "tags": ["myTag", "myTag2:myValue"]}, "type": "confluent-cloud-accounts"}} When the request is sent Then the response status is 201 OK - @generated @skip @team:Datadog/web-integrations + @generated @skip @team:DataDog/saas-integrations @team:DataDog/web-integrations Scenario: Add resource to Confluent account returns "Bad Request" response Given new "CreateConfluentResource" request And request contains "account_id" parameter from "REPLACE.ME" @@ -37,7 +37,7 @@ Feature: Confluent Cloud When the request is sent Then the response status is 400 Bad Request - @generated @skip @team:Datadog/web-integrations + @generated @skip @team:DataDog/saas-integrations @team:DataDog/web-integrations Scenario: Add resource to Confluent account returns "Not Found" response Given new "CreateConfluentResource" request And request contains "account_id" parameter from "REPLACE.ME" @@ -45,7 +45,7 @@ Feature: Confluent Cloud When the request is sent Then the response status is 404 Not Found - @team:Datadog/web-integrations + @team:DataDog/saas-integrations @team:DataDog/web-integrations Scenario: Add resource to Confluent account returns "OK" response Given there is a valid "confluent_account" in the system And new "CreateConfluentResource" request @@ -57,21 +57,21 @@ Feature: Confluent Cloud And the response "data.attributes.resource_type" is equal to "kafka" And the response "data.attributes.tags[0]" is equal to "mytag" - @generated @skip @team:Datadog/web-integrations + @generated @skip @team:DataDog/saas-integrations @team:DataDog/web-integrations Scenario: Delete Confluent account returns "Bad Request" response Given new "DeleteConfluentAccount" request And request contains "account_id" parameter from "REPLACE.ME" When the request is sent Then the response status is 400 Bad Request - @generated @skip @team:Datadog/web-integrations + @generated @skip @team:DataDog/saas-integrations @team:DataDog/web-integrations Scenario: Delete Confluent account returns "Not Found" response Given new "DeleteConfluentAccount" request And request contains "account_id" parameter from "REPLACE.ME" When the request is sent Then the response status is 404 Not Found - @team:Datadog/web-integrations + @team:DataDog/saas-integrations @team:DataDog/web-integrations Scenario: Delete Confluent account returns "OK" response Given there is a valid "confluent_account" in the system And new "DeleteConfluentAccount" request @@ -79,7 +79,7 @@ Feature: Confluent Cloud When the request is sent Then the response status is 204 OK - @generated @skip @team:Datadog/web-integrations + @generated @skip @team:DataDog/saas-integrations @team:DataDog/web-integrations Scenario: Delete resource from Confluent account returns "Bad Request" response Given new "DeleteConfluentResource" request And request contains "account_id" parameter from "REPLACE.ME" @@ -87,7 +87,7 @@ Feature: Confluent Cloud When the request is sent Then the response status is 400 Bad Request - @generated @skip @team:Datadog/web-integrations + @generated @skip @team:DataDog/saas-integrations @team:DataDog/web-integrations Scenario: Delete resource from Confluent account returns "Not Found" response Given new "DeleteConfluentResource" request And request contains "account_id" parameter from "REPLACE.ME" @@ -95,7 +95,7 @@ Feature: Confluent Cloud When the request is sent Then the response status is 404 Not Found - @generated @skip @team:Datadog/web-integrations + @generated @skip @team:DataDog/saas-integrations @team:DataDog/web-integrations Scenario: Delete resource from Confluent account returns "OK" response Given new "DeleteConfluentResource" request And request contains "account_id" parameter from "REPLACE.ME" @@ -103,21 +103,21 @@ Feature: Confluent Cloud When the request is sent Then the response status is 204 OK - @generated @skip @team:Datadog/web-integrations + @generated @skip @team:DataDog/saas-integrations @team:DataDog/web-integrations Scenario: Get Confluent account returns "Bad Request" response Given new "GetConfluentAccount" request And request contains "account_id" parameter from "REPLACE.ME" When the request is sent Then the response status is 400 Bad Request - @generated @skip @team:Datadog/web-integrations + @generated @skip @team:DataDog/saas-integrations @team:DataDog/web-integrations Scenario: Get Confluent account returns "Not Found" response Given new "GetConfluentAccount" request And request contains "account_id" parameter from "REPLACE.ME" When the request is sent Then the response status is 404 Not Found - @team:Datadog/web-integrations + @team:DataDog/saas-integrations @team:DataDog/web-integrations Scenario: Get Confluent account returns "OK" response Given there is a valid "confluent_account" in the system And new "GetConfluentAccount" request @@ -129,7 +129,7 @@ Feature: Confluent Cloud And the response "data.attributes.resources[0].resource_type" is equal to "kafka" And the response "data.attributes.resources[0].enable_custom_metrics" is equal to false - @generated @skip @team:Datadog/web-integrations + @generated @skip @team:DataDog/saas-integrations @team:DataDog/web-integrations Scenario: Get resource from Confluent account returns "Bad Request" response Given new "GetConfluentResource" request And request contains "account_id" parameter from "REPLACE.ME" @@ -137,7 +137,7 @@ Feature: Confluent Cloud When the request is sent Then the response status is 400 Bad Request - @generated @skip @team:Datadog/web-integrations + @generated @skip @team:DataDog/saas-integrations @team:DataDog/web-integrations Scenario: Get resource from Confluent account returns "Not Found" response Given new "GetConfluentResource" request And request contains "account_id" parameter from "REPLACE.ME" @@ -145,7 +145,7 @@ Feature: Confluent Cloud When the request is sent Then the response status is 404 Not Found - @generated @skip @team:Datadog/web-integrations + @generated @skip @team:DataDog/saas-integrations @team:DataDog/web-integrations Scenario: Get resource from Confluent account returns "OK" response Given new "GetConfluentResource" request And request contains "account_id" parameter from "REPLACE.ME" @@ -153,40 +153,40 @@ Feature: Confluent Cloud When the request is sent Then the response status is 200 OK - @generated @skip @team:Datadog/web-integrations + @generated @skip @team:DataDog/saas-integrations @team:DataDog/web-integrations Scenario: List Confluent Account resources returns "Bad Request" response Given new "ListConfluentResource" request And request contains "account_id" parameter from "REPLACE.ME" When the request is sent Then the response status is 400 Bad Request - @generated @skip @team:Datadog/web-integrations + @generated @skip @team:DataDog/saas-integrations @team:DataDog/web-integrations Scenario: List Confluent Account resources returns "Not Found" response Given new "ListConfluentResource" request And request contains "account_id" parameter from "REPLACE.ME" When the request is sent Then the response status is 404 Not Found - @generated @skip @team:Datadog/web-integrations + @generated @skip @team:DataDog/saas-integrations @team:DataDog/web-integrations Scenario: List Confluent Account resources returns "OK" response Given new "ListConfluentResource" request And request contains "account_id" parameter from "REPLACE.ME" When the request is sent Then the response status is 200 OK - @generated @skip @team:Datadog/web-integrations + @generated @skip @team:DataDog/saas-integrations @team:DataDog/web-integrations Scenario: List Confluent accounts returns "Bad Request" response Given new "ListConfluentAccount" request When the request is sent Then the response status is 400 Bad Request - @generated @skip @team:Datadog/web-integrations + @generated @skip @team:DataDog/saas-integrations @team:DataDog/web-integrations Scenario: List Confluent accounts returns "Not Found" response Given new "ListConfluentAccount" request When the request is sent Then the response status is 404 Not Found - @team:Datadog/web-integrations + @team:DataDog/saas-integrations @team:DataDog/web-integrations Scenario: List Confluent accounts returns "OK" response Given there is a valid "confluent_account" in the system And new "ListConfluentAccount" request @@ -194,7 +194,7 @@ Feature: Confluent Cloud Then the response status is 200 OK And the response "data[0].type" is equal to "confluent-cloud-accounts" - @generated @skip @team:Datadog/web-integrations + @generated @skip @team:DataDog/saas-integrations @team:DataDog/web-integrations Scenario: Update Confluent account returns "Bad Request" response Given new "UpdateConfluentAccount" request And request contains "account_id" parameter from "REPLACE.ME" @@ -202,7 +202,7 @@ Feature: Confluent Cloud When the request is sent Then the response status is 400 Bad Request - @generated @skip @team:Datadog/web-integrations + @generated @skip @team:DataDog/saas-integrations @team:DataDog/web-integrations Scenario: Update Confluent account returns "Not Found" response Given new "UpdateConfluentAccount" request And request contains "account_id" parameter from "REPLACE.ME" @@ -210,7 +210,7 @@ Feature: Confluent Cloud When the request is sent Then the response status is 404 Not Found - @team:Datadog/web-integrations + @team:DataDog/saas-integrations @team:DataDog/web-integrations Scenario: Update Confluent account returns "OK" response Given there is a valid "confluent_account" in the system And new "UpdateConfluentAccount" request @@ -221,7 +221,7 @@ Feature: Confluent Cloud And the response "data.attributes.tags[0]" is equal to "updated_tag:val" And the response "data.attributes.api_key" is equal to "{{ confluent_account.data.attributes.api_key }}" - @generated @skip @team:Datadog/web-integrations + @generated @skip @team:DataDog/saas-integrations @team:DataDog/web-integrations Scenario: Update resource in Confluent account returns "Bad Request" response Given new "UpdateConfluentResource" request And request contains "account_id" parameter from "REPLACE.ME" @@ -230,7 +230,7 @@ Feature: Confluent Cloud When the request is sent Then the response status is 400 Bad Request - @generated @skip @team:Datadog/web-integrations + @generated @skip @team:DataDog/saas-integrations @team:DataDog/web-integrations Scenario: Update resource in Confluent account returns "Not Found" response Given new "UpdateConfluentResource" request And request contains "account_id" parameter from "REPLACE.ME" @@ -239,7 +239,7 @@ Feature: Confluent Cloud When the request is sent Then the response status is 404 Not Found - @generated @skip @team:Datadog/web-integrations + @generated @skip @team:DataDog/saas-integrations @team:DataDog/web-integrations Scenario: Update resource in Confluent account returns "OK" response Given new "UpdateConfluentResource" request And request contains "account_id" parameter from "REPLACE.ME" diff --git a/tests/scenarios/features/v2/fastly_integration.feature b/tests/scenarios/features/v2/fastly_integration.feature index 349beb0061f..a42378363a1 100644 --- a/tests/scenarios/features/v2/fastly_integration.feature +++ b/tests/scenarios/features/v2/fastly_integration.feature @@ -8,14 +8,14 @@ Feature: Fastly Integration And a valid "appKeyAuth" key in the system And an instance of "FastlyIntegration" API - @generated @skip @team:Datadog/web-integrations + @generated @skip @team:DataDog/saas-integrations @team:DataDog/web-integrations Scenario: Add Fastly account returns "Bad Request" response Given new "CreateFastlyAccount" request And body with value {"data": {"attributes": {"api_key": "ABCDEFG123", "name": "test-name", "services": [{"id": "6abc7de6893AbcDe9fghIj", "tags": ["myTag", "myTag2:myValue"]}]}, "type": "fastly-accounts"}} When the request is sent Then the response status is 400 Bad Request - @team:Datadog/web-integrations + @team:DataDog/saas-integrations @team:DataDog/web-integrations Scenario: Add Fastly account returns "CREATED" response Given new "CreateFastlyAccount" request And body with value {"data": {"attributes": {"api_key": "{{ unique_alnum }}", "name": "{{ unique }}", "services": []}, "type": "fastly-accounts"}} @@ -25,14 +25,14 @@ Feature: Fastly Integration And the response "data.attributes.name" is equal to "{{ unique }}" And the response "data.attributes.services" has length 0 - @generated @skip @team:Datadog/web-integrations + @generated @skip @team:DataDog/saas-integrations @team:DataDog/web-integrations Scenario: Add Fastly account returns "Not Found" response Given new "CreateFastlyAccount" request And body with value {"data": {"attributes": {"api_key": "ABCDEFG123", "name": "test-name", "services": [{"id": "6abc7de6893AbcDe9fghIj", "tags": ["myTag", "myTag2:myValue"]}]}, "type": "fastly-accounts"}} When the request is sent Then the response status is 404 Not Found - @generated @skip @team:Datadog/web-integrations + @generated @skip @team:DataDog/saas-integrations @team:DataDog/web-integrations Scenario: Add Fastly service returns "Bad Request" response Given new "CreateFastlyService" request And request contains "account_id" parameter from "REPLACE.ME" @@ -40,7 +40,7 @@ Feature: Fastly Integration When the request is sent Then the response status is 400 Bad Request - @generated @skip @team:Datadog/web-integrations + @generated @skip @team:DataDog/saas-integrations @team:DataDog/web-integrations Scenario: Add Fastly service returns "CREATED" response Given new "CreateFastlyService" request And request contains "account_id" parameter from "REPLACE.ME" @@ -48,7 +48,7 @@ Feature: Fastly Integration When the request is sent Then the response status is 201 CREATED - @generated @skip @team:Datadog/web-integrations + @generated @skip @team:DataDog/saas-integrations @team:DataDog/web-integrations Scenario: Add Fastly service returns "Not Found" response Given new "CreateFastlyService" request And request contains "account_id" parameter from "REPLACE.ME" @@ -56,28 +56,28 @@ Feature: Fastly Integration When the request is sent Then the response status is 404 Not Found - @generated @skip @team:Datadog/web-integrations + @generated @skip @team:DataDog/saas-integrations @team:DataDog/web-integrations Scenario: Delete Fastly account returns "Bad Request" response Given new "DeleteFastlyAccount" request And request contains "account_id" parameter from "REPLACE.ME" When the request is sent Then the response status is 400 Bad Request - @generated @skip @team:Datadog/web-integrations + @generated @skip @team:DataDog/saas-integrations @team:DataDog/web-integrations Scenario: Delete Fastly account returns "Not Found" response Given new "DeleteFastlyAccount" request And request contains "account_id" parameter from "REPLACE.ME" When the request is sent Then the response status is 404 Not Found - @generated @skip @team:Datadog/web-integrations + @generated @skip @team:DataDog/saas-integrations @team:DataDog/web-integrations Scenario: Delete Fastly account returns "OK" response Given new "DeleteFastlyAccount" request And request contains "account_id" parameter from "REPLACE.ME" When the request is sent Then the response status is 204 OK - @generated @skip @team:Datadog/web-integrations + @generated @skip @team:DataDog/saas-integrations @team:DataDog/web-integrations Scenario: Delete Fastly service returns "Bad Request" response Given new "DeleteFastlyService" request And request contains "account_id" parameter from "REPLACE.ME" @@ -85,7 +85,7 @@ Feature: Fastly Integration When the request is sent Then the response status is 400 Bad Request - @generated @skip @team:Datadog/web-integrations + @generated @skip @team:DataDog/saas-integrations @team:DataDog/web-integrations Scenario: Delete Fastly service returns "Not Found" response Given new "DeleteFastlyService" request And request contains "account_id" parameter from "REPLACE.ME" @@ -93,7 +93,7 @@ Feature: Fastly Integration When the request is sent Then the response status is 404 Not Found - @generated @skip @team:Datadog/web-integrations + @generated @skip @team:DataDog/saas-integrations @team:DataDog/web-integrations Scenario: Delete Fastly service returns "OK" response Given new "DeleteFastlyService" request And request contains "account_id" parameter from "REPLACE.ME" @@ -101,21 +101,21 @@ Feature: Fastly Integration When the request is sent Then the response status is 204 OK - @generated @skip @team:Datadog/web-integrations + @generated @skip @team:DataDog/saas-integrations @team:DataDog/web-integrations Scenario: Get Fastly account returns "Bad Request" response Given new "GetFastlyAccount" request And request contains "account_id" parameter from "REPLACE.ME" When the request is sent Then the response status is 400 Bad Request - @generated @skip @team:Datadog/web-integrations + @generated @skip @team:DataDog/saas-integrations @team:DataDog/web-integrations Scenario: Get Fastly account returns "Not Found" response Given new "GetFastlyAccount" request And request contains "account_id" parameter from "REPLACE.ME" When the request is sent Then the response status is 404 Not Found - @team:Datadog/web-integrations + @team:DataDog/saas-integrations @team:DataDog/web-integrations Scenario: Get Fastly account returns "OK" response Given there is a valid "fastly_account" in the system And new "GetFastlyAccount" request @@ -126,7 +126,7 @@ Feature: Fastly Integration And the response "data.attributes.name" is equal to "{{ unique }}" And the response "data.attributes.services" has length 0 - @generated @skip @team:Datadog/web-integrations + @generated @skip @team:DataDog/saas-integrations @team:DataDog/web-integrations Scenario: Get Fastly service returns "Bad Request" response Given new "GetFastlyService" request And request contains "account_id" parameter from "REPLACE.ME" @@ -134,7 +134,7 @@ Feature: Fastly Integration When the request is sent Then the response status is 400 Bad Request - @generated @skip @team:Datadog/web-integrations + @generated @skip @team:DataDog/saas-integrations @team:DataDog/web-integrations Scenario: Get Fastly service returns "Not Found" response Given new "GetFastlyService" request And request contains "account_id" parameter from "REPLACE.ME" @@ -142,7 +142,7 @@ Feature: Fastly Integration When the request is sent Then the response status is 404 Not Found - @generated @skip @team:Datadog/web-integrations + @generated @skip @team:DataDog/saas-integrations @team:DataDog/web-integrations Scenario: Get Fastly service returns "OK" response Given new "GetFastlyService" request And request contains "account_id" parameter from "REPLACE.ME" @@ -150,19 +150,19 @@ Feature: Fastly Integration When the request is sent Then the response status is 200 OK - @generated @skip @team:Datadog/web-integrations + @generated @skip @team:DataDog/saas-integrations @team:DataDog/web-integrations Scenario: List Fastly accounts returns "Bad Request" response Given new "ListFastlyAccounts" request When the request is sent Then the response status is 400 Bad Request - @generated @skip @team:Datadog/web-integrations + @generated @skip @team:DataDog/saas-integrations @team:DataDog/web-integrations Scenario: List Fastly accounts returns "Not Found" response Given new "ListFastlyAccounts" request When the request is sent Then the response status is 404 Not Found - @team:Datadog/web-integrations + @team:DataDog/saas-integrations @team:DataDog/web-integrations Scenario: List Fastly accounts returns "OK" response Given there is a valid "fastly_account" in the system And new "ListFastlyAccounts" request @@ -170,28 +170,28 @@ Feature: Fastly Integration Then the response status is 200 OK And the response "data[0].type" is equal to "fastly-accounts" - @generated @skip @team:Datadog/web-integrations + @generated @skip @team:DataDog/saas-integrations @team:DataDog/web-integrations Scenario: List Fastly services returns "Bad Request" response Given new "ListFastlyServices" request And request contains "account_id" parameter from "REPLACE.ME" When the request is sent Then the response status is 400 Bad Request - @generated @skip @team:Datadog/web-integrations + @generated @skip @team:DataDog/saas-integrations @team:DataDog/web-integrations Scenario: List Fastly services returns "Not Found" response Given new "ListFastlyServices" request And request contains "account_id" parameter from "REPLACE.ME" When the request is sent Then the response status is 404 Not Found - @generated @skip @team:Datadog/web-integrations + @generated @skip @team:DataDog/saas-integrations @team:DataDog/web-integrations Scenario: List Fastly services returns "OK" response Given new "ListFastlyServices" request And request contains "account_id" parameter from "REPLACE.ME" When the request is sent Then the response status is 200 OK - @generated @skip @team:Datadog/web-integrations + @generated @skip @team:DataDog/saas-integrations @team:DataDog/web-integrations Scenario: Update Fastly account returns "Bad Request" response Given new "UpdateFastlyAccount" request And request contains "account_id" parameter from "REPLACE.ME" @@ -199,7 +199,7 @@ Feature: Fastly Integration When the request is sent Then the response status is 400 Bad Request - @generated @skip @team:Datadog/web-integrations + @generated @skip @team:DataDog/saas-integrations @team:DataDog/web-integrations Scenario: Update Fastly account returns "Not Found" response Given new "UpdateFastlyAccount" request And request contains "account_id" parameter from "REPLACE.ME" @@ -207,7 +207,7 @@ Feature: Fastly Integration When the request is sent Then the response status is 404 Not Found - @team:Datadog/web-integrations + @team:DataDog/saas-integrations @team:DataDog/web-integrations Scenario: Update Fastly account returns "OK" response Given there is a valid "fastly_account" in the system And new "UpdateFastlyAccount" request @@ -218,7 +218,7 @@ Feature: Fastly Integration And the response "data.id" is equal to "{{fastly_account.data.id }}" And the response "data.attributes.name" is equal to "{{fastly_account.data.attributes.name }}" - @generated @skip @team:Datadog/web-integrations + @generated @skip @team:DataDog/saas-integrations @team:DataDog/web-integrations Scenario: Update Fastly service returns "Bad Request" response Given new "UpdateFastlyService" request And request contains "account_id" parameter from "REPLACE.ME" @@ -227,7 +227,7 @@ Feature: Fastly Integration When the request is sent Then the response status is 400 Bad Request - @generated @skip @team:Datadog/web-integrations + @generated @skip @team:DataDog/saas-integrations @team:DataDog/web-integrations Scenario: Update Fastly service returns "Not Found" response Given new "UpdateFastlyService" request And request contains "account_id" parameter from "REPLACE.ME" @@ -236,7 +236,7 @@ Feature: Fastly Integration When the request is sent Then the response status is 404 Not Found - @generated @skip @team:Datadog/web-integrations + @generated @skip @team:DataDog/saas-integrations @team:DataDog/web-integrations Scenario: Update Fastly service returns "OK" response Given new "UpdateFastlyService" request And request contains "account_id" parameter from "REPLACE.ME" diff --git a/tests/scenarios/features/v2/okta_integration.feature b/tests/scenarios/features/v2/okta_integration.feature index a623c27e544..7b1a44c2f17 100644 --- a/tests/scenarios/features/v2/okta_integration.feature +++ b/tests/scenarios/features/v2/okta_integration.feature @@ -7,63 +7,63 @@ Feature: Okta Integration And a valid "appKeyAuth" key in the system And an instance of "OktaIntegration" API - @generated @skip @team:Datadog/web-integrations + @generated @skip @team:DataDog/saas-integrations @team:DataDog/web-integrations Scenario: Add Okta account returns "Bad Request" response Given new "CreateOktaAccount" request And body with value {"data": {"attributes": {"auth_method": "oauth", "domain": "https://example.okta.com/", "name": "Okta-Prod"}, "id": "f749daaf-682e-4208-a38d-c9b43162c609", "type": "okta-accounts"}} When the request is sent Then the response status is 400 Bad Request - @generated @skip @team:Datadog/web-integrations + @generated @skip @team:DataDog/saas-integrations @team:DataDog/web-integrations Scenario: Add Okta account returns "Not Found" response Given new "CreateOktaAccount" request And body with value {"data": {"attributes": {"auth_method": "oauth", "domain": "https://example.okta.com/", "name": "Okta-Prod"}, "id": "f749daaf-682e-4208-a38d-c9b43162c609", "type": "okta-accounts"}} When the request is sent Then the response status is 404 Not Found - @team:Datadog/web-integrations + @team:DataDog/saas-integrations @team:DataDog/web-integrations Scenario: Add Okta account returns "OK" response Given new "CreateOktaAccount" request And body with value {"data": {"attributes": {"auth_method": "oauth", "domain": "https://example.okta.com/", "name": "Okta_Prod", "client_id": "client_id", "client_secret":"client_secret"},"id": "f749daaf-682e-4208-a38d-c9b43162c609", "type": "okta-accounts"}} When the request is sent Then the response status is 201 OK - @generated @skip @team:Datadog/web-integrations + @generated @skip @team:DataDog/saas-integrations @team:DataDog/web-integrations Scenario: Delete Okta account returns "Bad Request" response Given new "DeleteOktaAccount" request And request contains "account_id" parameter from "REPLACE.ME" When the request is sent Then the response status is 400 Bad Request - @generated @skip @team:Datadog/web-integrations + @generated @skip @team:DataDog/saas-integrations @team:DataDog/web-integrations Scenario: Delete Okta account returns "Not Found" response Given new "DeleteOktaAccount" request And request contains "account_id" parameter from "REPLACE.ME" When the request is sent Then the response status is 404 Not Found - @generated @skip @team:Datadog/web-integrations + @generated @skip @team:DataDog/saas-integrations @team:DataDog/web-integrations Scenario: Delete Okta account returns "OK" response Given new "DeleteOktaAccount" request And request contains "account_id" parameter from "REPLACE.ME" When the request is sent Then the response status is 204 OK - @generated @skip @team:Datadog/web-integrations + @generated @skip @team:DataDog/saas-integrations @team:DataDog/web-integrations Scenario: Get Okta account returns "Bad Request" response Given new "GetOktaAccount" request And request contains "account_id" parameter from "REPLACE.ME" When the request is sent Then the response status is 400 Bad Request - @generated @skip @team:Datadog/web-integrations + @generated @skip @team:DataDog/saas-integrations @team:DataDog/web-integrations Scenario: Get Okta account returns "Not Found" response Given new "GetOktaAccount" request And request contains "account_id" parameter from "REPLACE.ME" When the request is sent Then the response status is 404 Not Found - @team:Datadog/web-integrations + @team:DataDog/saas-integrations @team:DataDog/web-integrations Scenario: Get Okta account returns "OK" response Given there is a valid "okta_account" in the system And new "GetOktaAccount" request @@ -72,26 +72,26 @@ Feature: Okta Integration Then the response status is 200 OK And the response "data.type" is equal to "okta-accounts" - @generated @skip @team:Datadog/web-integrations + @generated @skip @team:DataDog/saas-integrations @team:DataDog/web-integrations Scenario: List Okta accounts returns "Bad Request" response Given new "ListOktaAccounts" request When the request is sent Then the response status is 400 Bad Request - @generated @skip @team:Datadog/web-integrations + @generated @skip @team:DataDog/saas-integrations @team:DataDog/web-integrations Scenario: List Okta accounts returns "Not Found" response Given new "ListOktaAccounts" request When the request is sent Then the response status is 404 Not Found - @team:Datadog/web-integrations + @team:DataDog/saas-integrations @team:DataDog/web-integrations Scenario: List Okta accounts returns "OK" response Given there is a valid "okta_account" in the system And new "ListOktaAccounts" request When the request is sent Then the response status is 200 OK - @generated @skip @team:Datadog/web-integrations + @generated @skip @team:DataDog/saas-integrations @team:DataDog/web-integrations Scenario: Update Okta account returns "Bad Request" response Given new "UpdateOktaAccount" request And request contains "account_id" parameter from "REPLACE.ME" @@ -99,7 +99,7 @@ Feature: Okta Integration When the request is sent Then the response status is 400 Bad Request - @generated @skip @team:Datadog/web-integrations + @generated @skip @team:DataDog/saas-integrations @team:DataDog/web-integrations Scenario: Update Okta account returns "Not Found" response Given new "UpdateOktaAccount" request And request contains "account_id" parameter from "REPLACE.ME" @@ -107,7 +107,7 @@ Feature: Okta Integration When the request is sent Then the response status is 404 Not Found - @team:Datadog/web-integrations + @team:DataDog/saas-integrations @team:DataDog/web-integrations Scenario: Update Okta account returns "OK" response Given there is a valid "okta_account" in the system And new "UpdateOktaAccount" request