From 3ef8c4ad25d166d1077c931746a4e632900dcf5d Mon Sep 17 00:00:00 2001 From: "ci.datadog-api-spec" Date: Mon, 10 Aug 2026 21:21:34 +0000 Subject: [PATCH] Regenerate client from commit fcaeb52 of spec repo --- .../api/client/v2/api/scorecards.feature | 78 +++++++++---------- .../client/v2/api/service_definition.feature | 30 +++---- .../client/v2/api/software_catalog.feature | 42 +++++----- 3 files changed, 75 insertions(+), 75 deletions(-) diff --git a/src/test/resources/com/datadog/api/client/v2/api/scorecards.feature b/src/test/resources/com/datadog/api/client/v2/api/scorecards.feature index e932599c677..316e24cd412 100644 --- a/src/test/resources/com/datadog/api/client/v2/api/scorecards.feature +++ b/src/test/resources/com/datadog/api/client/v2/api/scorecards.feature @@ -9,28 +9,28 @@ Feature: Scorecards And a valid "appKeyAuth" key in the system And an instance of "Scorecards" API - @generated @skip @team:DataDog/service-catalog + @generated @skip @team:DataDog/idp Scenario: Create a new campaign returns "Bad Request" response Given new "CreateScorecardCampaign" request And body with value {"data": {"attributes": {"description": "Campaign to improve security posture for Q1 2024.", "due_date": "2024-03-31T23:59:59Z", "entity_scope": "kind:service AND team:platform", "guidance": "Please ensure all services pass the security requirements.", "key": "q1-security-2024", "name": "Q1 Security Campaign", "owner_id": "550e8400-e29b-41d4-a716-446655440000", "rule_ids": ["q8MQxk8TCqrHnWkx", "r9NRyl9UDrsIoXly"], "start_date": "2024-01-01T00:00:00Z", "status": "in_progress"}, "type": "campaign"}} When the request is sent Then the response status is 400 Bad Request - @generated @skip @team:DataDog/service-catalog + @generated @skip @team:DataDog/idp Scenario: Create a new campaign returns "Created" response Given new "CreateScorecardCampaign" request And body with value {"data": {"attributes": {"description": "Campaign to improve security posture for Q1 2024.", "due_date": "2024-03-31T23:59:59Z", "entity_scope": "kind:service AND team:platform", "guidance": "Please ensure all services pass the security requirements.", "key": "q1-security-2024", "name": "Q1 Security Campaign", "owner_id": "550e8400-e29b-41d4-a716-446655440000", "rule_ids": ["q8MQxk8TCqrHnWkx", "r9NRyl9UDrsIoXly"], "start_date": "2024-01-01T00:00:00Z", "status": "in_progress"}, "type": "campaign"}} When the request is sent Then the response status is 201 Created - @team:DataDog/service-catalog + @team:DataDog/idp Scenario: Create a new rule returns "Bad Request" response Given new "CreateScorecardRule" request And body with value {"data": {"attributes": {"enabled": true, "level": 2, "name": "Team Defined", "scorecard_id": "NOT.FOUND"}, "type": "rule"}} When the request is sent Then the response status is 400 Bad Request - @team:DataDog/service-catalog + @team:DataDog/idp Scenario: Create a new rule returns "Created" response Given new "CreateScorecardRule" request And body with value {"data": {"attributes": {"enabled": true, "name": "{{unique}}", "scorecard_name": "Observability Best Practices"}, "type": "rule"}} @@ -39,7 +39,7 @@ Feature: Scorecards And the response "data.attributes.scorecard_name" is equal to "Observability Best Practices" And the response "data.relationships.scorecard.data" has field "id" - @team:DataDog/service-catalog + @team:DataDog/idp Scenario: Create outcomes batch returns "Bad Request" response Given there is a valid "create_scorecard_rule" in the system And operation "CreateScorecardOutcomesBatch" enabled @@ -48,7 +48,7 @@ Feature: Scorecards When the request is sent Then the response status is 400 Bad Request - @team:DataDog/service-catalog + @team:DataDog/idp Scenario: Create outcomes batch returns "OK" response Given there is a valid "create_scorecard_rule" in the system And operation "CreateScorecardOutcomesBatch" enabled @@ -57,42 +57,42 @@ Feature: Scorecards When the request is sent Then the response status is 200 OK - @generated @skip @team:DataDog/service-catalog + @generated @skip @team:DataDog/idp Scenario: Delete a campaign returns "Bad Request" response Given new "DeleteScorecardCampaign" request And request contains "campaign_id" parameter from "REPLACE.ME" When the request is sent Then the response status is 400 Bad Request - @generated @skip @team:DataDog/service-catalog + @generated @skip @team:DataDog/idp Scenario: Delete a campaign returns "No Content" response Given new "DeleteScorecardCampaign" request And request contains "campaign_id" parameter from "REPLACE.ME" When the request is sent Then the response status is 204 No Content - @generated @skip @team:DataDog/service-catalog + @generated @skip @team:DataDog/idp Scenario: Delete a campaign returns "Not Found" response Given new "DeleteScorecardCampaign" request And request contains "campaign_id" parameter from "REPLACE.ME" When the request is sent Then the response status is 404 Not Found - @generated @skip @team:DataDog/service-catalog + @generated @skip @team:DataDog/idp Scenario: Delete a rule returns "Bad Request" response Given new "DeleteScorecardRule" request And request contains "rule_id" parameter from "REPLACE.ME" When the request is sent Then the response status is 400 Bad Request - @team:DataDog/service-catalog + @team:DataDog/idp Scenario: Delete a rule returns "Not Found" response Given new "DeleteScorecardRule" request And request contains "rule_id" parameter with value "2a4f524e-168a-429d-bb75-7b1ffeab0cbb" When the request is sent Then the response status is 404 Not Found - @team:DataDog/service-catalog + @team:DataDog/idp Scenario: Delete a rule returns "OK" response Given there is a valid "create_scorecard_rule" in the system And new "DeleteScorecardRule" request @@ -100,52 +100,52 @@ Feature: Scorecards When the request is sent Then the response status is 204 OK - @generated @skip @team:DataDog/service-catalog + @generated @skip @team:DataDog/idp Scenario: Get a campaign returns "Bad Request" response Given new "GetScorecardCampaign" request And request contains "campaign_id" parameter from "REPLACE.ME" When the request is sent Then the response status is 400 Bad Request - @generated @skip @team:DataDog/service-catalog + @generated @skip @team:DataDog/idp Scenario: Get a campaign returns "Not Found" response Given new "GetScorecardCampaign" request And request contains "campaign_id" parameter from "REPLACE.ME" When the request is sent Then the response status is 404 Not Found - @generated @skip @team:DataDog/service-catalog + @generated @skip @team:DataDog/idp Scenario: Get a campaign returns "OK" response Given new "GetScorecardCampaign" request And request contains "campaign_id" parameter from "REPLACE.ME" When the request is sent Then the response status is 200 OK - @generated @skip @team:DataDog/service-catalog + @generated @skip @team:DataDog/idp Scenario: List all campaigns returns "Bad Request" response Given new "ListScorecardCampaigns" request When the request is sent Then the response status is 400 Bad Request - @generated @skip @team:DataDog/service-catalog + @generated @skip @team:DataDog/idp Scenario: List all campaigns returns "OK" response Given new "ListScorecardCampaigns" request When the request is sent Then the response status is 200 OK - @generated @skip @team:DataDog/service-catalog + @generated @skip @team:DataDog/idp Scenario: List all rule outcomes returns "Bad Request" response Given new "ListScorecardOutcomes" request When the request is sent Then the response status is 400 Bad Request - @team:DataDog/service-catalog + @team:DataDog/idp Scenario: List all rule outcomes returns "OK" response Given new "ListScorecardOutcomes" request When the request is sent Then the response status is 200 OK - @replay-only @skip-validation @team:DataDog/service-catalog @with-pagination + @replay-only @skip-validation @team:DataDog/idp @with-pagination Scenario: List all rule outcomes returns "OK" response with pagination Given new "ListScorecardOutcomes" request And request contains "page[size]" parameter with value 2 @@ -155,19 +155,19 @@ Feature: Scorecards Then the response status is 200 OK And the response has 2 items - @generated @skip @team:DataDog/service-catalog + @generated @skip @team:DataDog/idp Scenario: List all rules returns "Bad Request" response Given new "ListScorecardRules" request When the request is sent Then the response status is 400 Bad Request - @team:DataDog/service-catalog + @team:DataDog/idp Scenario: List all rules returns "OK" response Given new "ListScorecardRules" request When the request is sent Then the response status is 200 OK - @replay-only @skip-validation @team:DataDog/service-catalog @with-pagination + @replay-only @skip-validation @team:DataDog/idp @with-pagination Scenario: List all rules returns "OK" response with pagination Given new "ListScorecardRules" request And request contains "page[size]" parameter with value 2 @@ -177,27 +177,27 @@ Feature: Scorecards Then the response status is 200 OK And the response has 4 items - @generated @skip @team:DataDog/service-catalog + @generated @skip @team:DataDog/idp Scenario: List all scorecards returns "OK" response Given new "ListScorecards" request When the request is sent Then the response status is 200 OK - @generated @skip @team:DataDog/service-catalog + @generated @skip @team:DataDog/idp Scenario: List all scores returns "Bad Request" response Given new "ListScorecardScores" request And request contains "aggregation" parameter from "REPLACE.ME" When the request is sent Then the response status is 400 Bad Request - @generated @skip @team:DataDog/service-catalog + @generated @skip @team:DataDog/idp Scenario: List all scores returns "OK" response Given new "ListScorecardScores" request And request contains "aggregation" parameter from "REPLACE.ME" When the request is sent Then the response status is 200 OK - @team:DataDog/service-catalog + @team:DataDog/idp Scenario: Update Scorecard outcomes asynchronously returns "Accepted" response Given there is a valid "create_scorecard_rule" in the system And new "UpdateScorecardOutcomes" request @@ -205,7 +205,7 @@ Feature: Scorecards When the request is sent Then the response status is 202 Accepted - @team:DataDog/service-catalog + @team:DataDog/idp Scenario: Update Scorecard outcomes asynchronously returns "Bad Request" response Given there is a valid "create_scorecard_rule" in the system And new "UpdateScorecardOutcomes" request @@ -215,7 +215,7 @@ Feature: Scorecards And the response "errors" has length 1 And the response "errors[0]" has field "detail" - @team:DataDog/service-catalog + @team:DataDog/idp Scenario: Update Scorecard outcomes asynchronously returns "Conflict" response Given new "UpdateScorecardOutcomes" request And body with value {"data": {"attributes": {"results": [{"rule_id": "INVALID.RULE_ID", "entity_reference": "service:my-service", "remarks": "See: Services", "state": "pass"}]}, "type": "batched-outcome"}} @@ -223,28 +223,28 @@ Feature: Scorecards Then the response status is 409 Conflict And the response "errors" has length 1 - @generated @skip @team:DataDog/service-catalog + @generated @skip @team:DataDog/idp Scenario: Update Scorecard outcomes returns "Accepted" response Given new "UpdateScorecardOutcomes" request And body with value {"data": {"attributes": {"results": [{"entity_reference": "service:my-service", "remarks": "See: Services", "rule_id": "q8MQxk8TCqrHnWkx", "state": "pass"}]}, "type": "batched-outcome"}} When the request is sent Then the response status is 202 Accepted - @generated @skip @team:DataDog/service-catalog + @generated @skip @team:DataDog/idp Scenario: Update Scorecard outcomes returns "Bad Request" response Given new "UpdateScorecardOutcomes" request And body with value {"data": {"attributes": {"results": [{"entity_reference": "service:my-service", "remarks": "See: Services", "rule_id": "q8MQxk8TCqrHnWkx", "state": "pass"}]}, "type": "batched-outcome"}} When the request is sent Then the response status is 400 Bad Request - @generated @skip @team:DataDog/service-catalog + @generated @skip @team:DataDog/idp Scenario: Update Scorecard outcomes returns "Conflict" response Given new "UpdateScorecardOutcomes" request And body with value {"data": {"attributes": {"results": [{"entity_reference": "service:my-service", "remarks": "See: Services", "rule_id": "q8MQxk8TCqrHnWkx", "state": "pass"}]}, "type": "batched-outcome"}} When the request is sent Then the response status is 409 Conflict - @generated @skip @team:DataDog/service-catalog + @generated @skip @team:DataDog/idp Scenario: Update a campaign returns "Bad Request" response Given new "UpdateScorecardCampaign" request And request contains "campaign_id" parameter from "REPLACE.ME" @@ -252,7 +252,7 @@ Feature: Scorecards When the request is sent Then the response status is 400 Bad Request - @generated @skip @team:DataDog/service-catalog + @generated @skip @team:DataDog/idp Scenario: Update a campaign returns "Not Found" response Given new "UpdateScorecardCampaign" request And request contains "campaign_id" parameter from "REPLACE.ME" @@ -260,7 +260,7 @@ Feature: Scorecards When the request is sent Then the response status is 404 Not Found - @generated @skip @team:DataDog/service-catalog + @generated @skip @team:DataDog/idp Scenario: Update a campaign returns "OK" response Given new "UpdateScorecardCampaign" request And request contains "campaign_id" parameter from "REPLACE.ME" @@ -268,7 +268,7 @@ Feature: Scorecards When the request is sent Then the response status is 200 OK - @team:DataDog/service-catalog + @team:DataDog/idp Scenario: Update an existing rule returns "Rule updated successfully" response Given there is a valid "create_scorecard_rule" in the system And new "UpdateScorecardRule" request @@ -277,7 +277,7 @@ Feature: Scorecards When the request is sent Then the response status is 200 Rule updated successfully - @team:DataDog/service-catalog + @team:DataDog/idp Scenario: Update an existing scorecard rule returns "Bad Request" response Given there is a valid "create_scorecard_rule" in the system And new "UpdateScorecardRule" request @@ -286,7 +286,7 @@ Feature: Scorecards When the request is sent Then the response status is 400 Bad Request - @team:DataDog/service-catalog + @team:DataDog/idp Scenario: Update an existing scorecard rule returns "Not Found" response Given new "UpdateScorecardRule" request And request contains "rule_id" parameter with value "REPLACE.ME" @@ -294,7 +294,7 @@ Feature: Scorecards When the request is sent Then the response status is 404 Not Found - @generated @skip @team:DataDog/service-catalog + @generated @skip @team:DataDog/idp Scenario: Update an existing scorecard rule returns "Rule updated successfully" response Given new "UpdateScorecardRule" request And request contains "rule_id" parameter from "REPLACE.ME" diff --git a/src/test/resources/com/datadog/api/client/v2/api/service_definition.feature b/src/test/resources/com/datadog/api/client/v2/api/service_definition.feature index 20c94280874..a36431dc828 100644 --- a/src/test/resources/com/datadog/api/client/v2/api/service_definition.feature +++ b/src/test/resources/com/datadog/api/client/v2/api/service_definition.feature @@ -11,28 +11,28 @@ Feature: Service Definition And a valid "appKeyAuth" key in the system And an instance of "ServiceDefinition" API - @generated @skip @team:DataDog/service-catalog + @generated @skip @team:DataDog/idp Scenario: Create or update service definition returns "Bad Request" response Given new "CreateOrUpdateServiceDefinitions" request And body with value {"application": "my-app", "ci-pipeline-fingerprints": ["j88xdEy0J5lc", "eZ7LMljCk8vo"], "contacts": [{"contact": "https://teams.microsoft.com/myteam", "name": "My team channel", "type": "slack"}], "dd-service": "my-service", "description": "My service description", "extensions": {"myorg/extension": "extensionValue"}, "integrations": {"opsgenie": {"region": "US", "service-url": "https://my-org.opsgenie.com/service/123e4567-e89b-12d3-a456-426614174000"}, "pagerduty": {"service-url": "https://my-org.pagerduty.com/service-directory/PMyService"}}, "languages": ["dotnet", "go", "java", "js", "php", "python", "ruby", "c++"], "lifecycle": "sandbox", "links": [{"name": "Runbook", "provider": "Github", "type": "runbook", "url": "https://my-runbook"}], "schema-version": "v2.2", "tags": ["my:tag", "service:tag"], "team": "my-team", "tier": "High", "type": "web"} When the request is sent Then the response status is 400 Bad Request - @generated @skip @team:DataDog/service-catalog + @generated @skip @team:DataDog/idp Scenario: Create or update service definition returns "CREATED" response Given new "CreateOrUpdateServiceDefinitions" request And body with value {"application": "my-app", "ci-pipeline-fingerprints": ["j88xdEy0J5lc", "eZ7LMljCk8vo"], "contacts": [{"contact": "https://teams.microsoft.com/myteam", "name": "My team channel", "type": "slack"}], "dd-service": "my-service", "description": "My service description", "extensions": {"myorg/extension": "extensionValue"}, "integrations": {"opsgenie": {"region": "US", "service-url": "https://my-org.opsgenie.com/service/123e4567-e89b-12d3-a456-426614174000"}, "pagerduty": {"service-url": "https://my-org.pagerduty.com/service-directory/PMyService"}}, "languages": ["dotnet", "go", "java", "js", "php", "python", "ruby", "c++"], "lifecycle": "sandbox", "links": [{"name": "Runbook", "provider": "Github", "type": "runbook", "url": "https://my-runbook"}], "schema-version": "v2.2", "tags": ["my:tag", "service:tag"], "team": "my-team", "tier": "High", "type": "web"} When the request is sent Then the response status is 200 CREATED - @generated @skip @team:DataDog/service-catalog + @generated @skip @team:DataDog/idp Scenario: Create or update service definition returns "Conflict" response Given new "CreateOrUpdateServiceDefinitions" request And body with value {"application": "my-app", "ci-pipeline-fingerprints": ["j88xdEy0J5lc", "eZ7LMljCk8vo"], "contacts": [{"contact": "https://teams.microsoft.com/myteam", "name": "My team channel", "type": "slack"}], "dd-service": "my-service", "description": "My service description", "extensions": {"myorg/extension": "extensionValue"}, "integrations": {"opsgenie": {"region": "US", "service-url": "https://my-org.opsgenie.com/service/123e4567-e89b-12d3-a456-426614174000"}, "pagerduty": {"service-url": "https://my-org.pagerduty.com/service-directory/PMyService"}}, "languages": ["dotnet", "go", "java", "js", "php", "python", "ruby", "c++"], "lifecycle": "sandbox", "links": [{"name": "Runbook", "provider": "Github", "type": "runbook", "url": "https://my-runbook"}], "schema-version": "v2.2", "tags": ["my:tag", "service:tag"], "team": "my-team", "tier": "High", "type": "web"} When the request is sent Then the response status is 409 Conflict - @team:DataDog/service-catalog + @team:DataDog/idp Scenario: Create or update service definition using schema v2 returns "CREATED" response Given new "CreateOrUpdateServiceDefinitions" request And body with value {"contacts": [{"contact": "contact@datadoghq.com", "name": "Team Email", "type": "email"}], "dd-service": "service-{{ unique_lower_alnum }}", "dd-team": "my-team", "docs": [{"name": "Architecture", "provider": "google drive", "url": "https://gdrive/mydoc"}], "extensions": {"myorgextension": "extensionvalue"}, "integrations": {"opsgenie": {"region": "US", "service-url": "https://my-org.opsgenie.com/service/123e4567-e89b-12d3-a456-426614174000"}, "pagerduty": "https://my-org.pagerduty.com/service-directory/PMyService"}, "links": [{"name": "Runbook", "type": "runbook", "url": "https://my-runbook"}], "repos": [{"name": "Source Code", "provider": "GitHub", "url": "https://github.com/DataDog/schema"}], "schema-version": "v2", "tags": ["my:tag", "service:tag"], "team": "my-team"} @@ -41,7 +41,7 @@ Feature: Service Definition And the response "data[0].attributes.meta.ingested-schema-version" is equal to "v2" And the response "data[0].attributes.schema.dd-service" is equal to "service-{{ unique_lower_alnum }}" - @team:DataDog/service-catalog + @team:DataDog/idp Scenario: Create or update service definition using schema v2-1 returns "CREATED" response Given new "CreateOrUpdateServiceDefinitions" request And body with value {"contacts":[{"contact":"contact@datadoghq.com","name":"Team Email","type":"email"}],"dd-service":"service-{{ unique_lower_alnum }}","extensions":{"myorgextension":"extensionvalue"},"integrations":{"opsgenie":{"region":"US","service-url":"https://my-org.opsgenie.com/service/123e4567-e89b-12d3-a456-426614174000"},"pagerduty":{"service-url":"https://my-org.pagerduty.com/service-directory/PMyService"}},"links":[{"name":"Runbook","type":"runbook","url":"https://my-runbook"},{"name":"Source Code","type":"repo","provider":"GitHub","url":"https://github.com/DataDog/schema"},{"name":"Architecture","type":"doc","provider":"Gigoogle drivetHub","url":"https://my-runbook"}],"schema-version":"v2.1","tags":["my:tag","service:tag"],"team":"my-team"} @@ -50,7 +50,7 @@ Feature: Service Definition And the response "data[0].attributes.meta.ingested-schema-version" is equal to "v2.1" And the response "data[0].attributes.schema.dd-service" is equal to "service-{{ unique_lower_alnum }}" - @team:DataDog/service-catalog + @team:DataDog/idp Scenario: Create or update service definition using schema v2-2 returns "CREATED" response Given new "CreateOrUpdateServiceDefinitions" request And body with value {"contacts":[{"contact":"contact@datadoghq.com","name":"Team Email","type":"email"}],"dd-service":"service-{{ unique_lower_alnum }}","extensions":{"myorgextension":"extensionvalue"},"integrations":{"opsgenie":{"region":"US","service-url":"https://my-org.opsgenie.com/service/123e4567-e89b-12d3-a456-426614174000"},"pagerduty":{"service-url":"https://my-org.pagerduty.com/service-directory/PMyService"}},"links":[{"name":"Runbook","type":"runbook","url":"https://my-runbook"},{"name":"Source Code","type":"repo","provider":"GitHub","url":"https://github.com/DataDog/schema"},{"name":"Architecture","type":"doc","provider":"Gigoogle drivetHub","url":"https://my-runbook"}],"schema-version":"v2.2","tags":["my:tag","service:tag"],"team":"my-team"} @@ -59,14 +59,14 @@ Feature: Service Definition And the response "data[0].attributes.meta.ingested-schema-version" is equal to "v2.2" And the response "data[0].attributes.schema.dd-service" is equal to "service-{{ unique_lower_alnum }}" - @generated @skip @team:DataDog/service-catalog + @generated @skip @team:DataDog/idp Scenario: Delete a single service definition returns "Bad Request" response Given new "DeleteServiceDefinition" request And request contains "service_name" parameter from "REPLACE.ME" When the request is sent Then the response status is 400 Bad Request - @team:DataDog/service-catalog + @team:DataDog/idp Scenario: Delete a single service definition returns "Not Found" response Given new "DeleteServiceDefinition" request And request contains "service_name" parameter with value "not-a-service" @@ -74,28 +74,28 @@ Feature: Service Definition Then the response status is 404 Not Found And the response "errors[0]" is equal to "Not Found" - @replay-only @team:DataDog/service-catalog + @replay-only @team:DataDog/idp Scenario: Delete a single service definition returns "OK" response Given new "DeleteServiceDefinition" request And request contains "service_name" parameter with value "service-definition-test" When the request is sent Then the response status is 204 OK - @generated @skip @team:DataDog/service-catalog + @generated @skip @team:DataDog/idp Scenario: Get a single service definition returns "Bad Request" response Given new "GetServiceDefinition" request And request contains "service_name" parameter from "REPLACE.ME" When the request is sent Then the response status is 400 Bad Request - @generated @skip @team:DataDog/service-catalog + @generated @skip @team:DataDog/idp Scenario: Get a single service definition returns "Conflict" response Given new "GetServiceDefinition" request And request contains "service_name" parameter from "REPLACE.ME" When the request is sent Then the response status is 409 Conflict - @team:DataDog/service-catalog + @team:DataDog/idp Scenario: Get a single service definition returns "Not Found" response Given new "GetServiceDefinition" request And request contains "service_name" parameter with value "not-a-service" @@ -103,7 +103,7 @@ Feature: Service Definition Then the response status is 404 Not Found And the response "errors[0]" is equal to "Not Found" - @team:DataDog/service-catalog + @team:DataDog/idp Scenario: Get a single service definition returns "OK" response Given new "GetServiceDefinition" request And request contains "service_name" parameter with value "service-definition-test" @@ -114,7 +114,7 @@ Feature: Service Definition And the response "data.attributes.schema.schema-version" is equal to "v2.1" And the response "data.attributes.schema.dd-service" is equal to "service-definition-test" - @team:DataDog/service-catalog + @team:DataDog/idp Scenario: Get all service definitions returns "OK" response Given new "ListServiceDefinitions" request And request contains "schema_version" parameter with value "v2.1" @@ -123,7 +123,7 @@ Feature: Service Definition And the response "data[0].attributes.meta.ingestion-source" is equal to "api" And the response "data[0].attributes.schema.schema-version" is equal to "v2.1" - @replay-only @skip-validation @team:DataDog/service-catalog @with-pagination + @replay-only @skip-validation @team:DataDog/idp @with-pagination Scenario: Get all service definitions returns "OK" response with pagination Given new "ListServiceDefinitions" request And request contains "page[size]" parameter with value 2 diff --git a/src/test/resources/com/datadog/api/client/v2/api/software_catalog.feature b/src/test/resources/com/datadog/api/client/v2/api/software_catalog.feature index 34e9f95314d..27059527041 100644 --- a/src/test/resources/com/datadog/api/client/v2/api/software_catalog.feature +++ b/src/test/resources/com/datadog/api/client/v2/api/software_catalog.feature @@ -7,42 +7,42 @@ Feature: Software Catalog And a valid "appKeyAuth" key in the system And an instance of "SoftwareCatalog" API - @generated @skip @team:DataDog/service-catalog + @generated @skip @team:DataDog/idp Scenario: Create or update entities returns "ACCEPTED" response Given new "UpsertCatalogEntity" request And body with value {"apiVersion": "v3", "datadog": {"codeLocations": [{"paths": []}], "events": [{}], "logs": [{}], "performanceData": {"tags": []}, "pipelines": {"fingerprints": []}}, "integrations": {"opsgenie": {"serviceURL": "https://www.opsgenie.com/service/shopping-cart"}, "pagerduty": {"serviceURL": "https://www.pagerduty.com/service-directory/Pshopping-cart"}}, "kind": "service", "metadata": {"additionalOwners": [{"name": ""}], "contacts": [{"contact": "https://slack/", "type": "slack"}], "id": "4b163705-23c0-4573-b2fb-f6cea2163fcb", "inheritFrom": "application:default/myapp", "links": [{"name": "mylink", "type": "link", "url": "https://mylink"}], "name": "myService", "namespace": "default", "tags": ["this:tag", "that:tag"]}, "spec": {"componentOf": [], "dependsOn": [], "languages": []}} When the request is sent Then the response status is 202 ACCEPTED - @generated @skip @team:DataDog/service-catalog + @generated @skip @team:DataDog/idp Scenario: Create or update entities returns "Bad Request" response Given new "UpsertCatalogEntity" request And body with value {"apiVersion": "v3", "datadog": {"codeLocations": [{"paths": []}], "events": [{}], "logs": [{}], "performanceData": {"tags": []}, "pipelines": {"fingerprints": []}}, "integrations": {"opsgenie": {"serviceURL": "https://www.opsgenie.com/service/shopping-cart"}, "pagerduty": {"serviceURL": "https://www.pagerduty.com/service-directory/Pshopping-cart"}}, "kind": "service", "metadata": {"additionalOwners": [{"name": ""}], "contacts": [{"contact": "https://slack/", "type": "slack"}], "id": "4b163705-23c0-4573-b2fb-f6cea2163fcb", "inheritFrom": "application:default/myapp", "links": [{"name": "mylink", "type": "link", "url": "https://mylink"}], "name": "myService", "namespace": "default", "tags": ["this:tag", "that:tag"]}, "spec": {"componentOf": [], "dependsOn": [], "languages": []}} When the request is sent Then the response status is 400 Bad Request - @skip @team:DataDog/service-catalog + @skip @team:DataDog/idp Scenario: Create or update entities without metadata name returns "Internal Server Error" response Given new "UpsertCatalogEntity" request And body with value {"apiVersion": "v3", "datadog": {"codeLocations": [{"paths": []}], "events": [{}], "logs": [{}], "performanceData": {"tags": []}, "pipelines": {"fingerprints": []}}, "integrations": {"opsgenie": {"serviceURL": "https://www.opsgenie.com/service/shopping-cart"}, "pagerduty": {"serviceURL": "https://www.pagerduty.com/service-directory/Pshopping-cart"}}, "kind": "service", "metadata": {"additionalOwners": [], "contacts": [{"contact": "https://slack/", "type": "slack"}], "id": "4b163705-23c0-4573-b2fb-f6cea2163fcb", "inheritFrom": "application:default/myapp", "links": [{"name": "mylink", "type": "link", "url": "https://mylink"}], "tags": ["this:tag", "that:tag"]}, "spec": {"dependsOn": [], "languages": []}} When the request is sent Then the response status is 500 Internal Server Error - @generated @skip @team:DataDog/service-catalog + @generated @skip @team:DataDog/idp Scenario: Create or update kinds returns "ACCEPTED" response Given new "UpsertCatalogKind" request And body with value {"kind": "my-job"} When the request is sent Then the response status is 202 ACCEPTED - @generated @skip @team:DataDog/service-catalog + @generated @skip @team:DataDog/idp Scenario: Create or update kinds returns "Bad Request" response Given new "UpsertCatalogKind" request And body with value {"kind": "my-job"} When the request is sent Then the response status is 400 Bad Request - @team:DataDog/service-catalog + @team:DataDog/idp Scenario: Create or update software catalog entity using schema v3 returns "ACCEPTED" response Given new "UpsertCatalogEntity" request And body with value {"apiVersion": "v3", "datadog": {"codeLocations": [{"paths": []}], "events": [{}], "logs": [{}], "performanceData": {"tags": []}, "pipelines": {"fingerprints": []}}, "integrations": {"opsgenie": {"serviceURL": "https://www.opsgenie.com/service/shopping-cart"}, "pagerduty": {"serviceURL": "https://www.pagerduty.com/service-directory/Pshopping-cart"}}, "kind": "service", "metadata": {"additionalOwners": [], "contacts": [{"contact": "https://slack/", "type": "slack"}], "id": "4b163705-23c0-4573-b2fb-f6cea2163fcb", "inheritFrom": "application:default/myapp", "links": [{"name": "mylink", "type": "link", "url": "https://mylink"}], "name": "service-{{ unique_lower_alnum }}", "tags": ["this:tag", "that:tag"]}, "spec": {"dependsOn": [], "languages": []}} @@ -52,49 +52,49 @@ Feature: Software Catalog And the response "data[0].attributes.kind" is equal to "service" And the response "data[0].attributes.name" is equal to "service-{{ unique_lower_alnum }}" - @generated @skip @team:DataDog/service-catalog + @generated @skip @team:DataDog/idp Scenario: Delete a single entity returns "Bad Request" response Given new "DeleteCatalogEntity" request And request contains "entity_id" parameter from "REPLACE.ME" When the request is sent Then the response status is 400 Bad Request - @generated @skip @team:DataDog/service-catalog + @generated @skip @team:DataDog/idp Scenario: Delete a single entity returns "Not Found" response Given new "DeleteCatalogEntity" request And request contains "entity_id" parameter from "REPLACE.ME" When the request is sent Then the response status is 404 Not Found - @generated @skip @team:DataDog/service-catalog + @generated @skip @team:DataDog/idp Scenario: Delete a single entity returns "OK" response Given new "DeleteCatalogEntity" request And request contains "entity_id" parameter from "REPLACE.ME" When the request is sent Then the response status is 204 OK - @generated @skip @team:DataDog/service-catalog + @generated @skip @team:DataDog/idp Scenario: Delete a single kind returns "Bad Request" response Given new "DeleteCatalogKind" request And request contains "kind_id" parameter from "REPLACE.ME" When the request is sent Then the response status is 400 Bad Request - @generated @skip @team:DataDog/service-catalog + @generated @skip @team:DataDog/idp Scenario: Delete a single kind returns "Not Found" response Given new "DeleteCatalogKind" request And request contains "kind_id" parameter from "REPLACE.ME" When the request is sent Then the response status is 404 Not Found - @generated @skip @team:DataDog/service-catalog + @generated @skip @team:DataDog/idp Scenario: Delete a single kind returns "OK" response Given new "DeleteCatalogKind" request And request contains "kind_id" parameter from "REPLACE.ME" When the request is sent Then the response status is 204 OK - @skip @team:DataDog/service-catalog + @skip @team:DataDog/idp Scenario: Delete an entity returns "Not Found" response Given new "DeleteCatalogEntity" request And request contains "entity_id" parameter with value "service:not-a-service" @@ -102,50 +102,50 @@ Feature: Software Catalog Then the response status is 404 Not Found And the response "errors[0]" is equal to "Not Found" - @team:DataDog/service-catalog + @team:DataDog/idp Scenario: Get a list of entities returns "OK" response Given new "ListCatalogEntity" request When the request is sent Then the response status is 200 OK - @generated @skip @team:DataDog/service-catalog @with-pagination + @generated @skip @team:DataDog/idp @with-pagination Scenario: Get a list of entities returns "OK" response with pagination Given new "ListCatalogEntity" request When the request with pagination is sent Then the response status is 200 OK - @generated @skip @team:DataDog/service-catalog + @generated @skip @team:DataDog/idp Scenario: Get a list of entity kinds returns "Bad Request" response Given new "ListCatalogKind" request When the request is sent Then the response status is 400 Bad Request - @generated @skip @team:DataDog/service-catalog + @generated @skip @team:DataDog/idp Scenario: Get a list of entity kinds returns "OK" response Given new "ListCatalogKind" request When the request is sent Then the response status is 200 OK - @generated @skip @team:DataDog/service-catalog @with-pagination + @generated @skip @team:DataDog/idp @with-pagination Scenario: Get a list of entity kinds returns "OK" response with pagination Given new "ListCatalogKind" request When the request with pagination is sent Then the response status is 200 OK - @replay-only @team:DataDog/service-catalog + @replay-only @team:DataDog/idp Scenario: Get a list of entity relations returns "OK" response Given new "ListCatalogRelation" request When the request is sent Then the response status is 200 OK - @replay-only @skip-validation @team:DataDog/service-catalog @with-pagination + @replay-only @skip-validation @team:DataDog/idp @with-pagination Scenario: Get a list of entity relations returns "OK" response with pagination Given new "ListCatalogRelation" request And request contains "page[limit]" parameter with value 20 When the request with pagination is sent Then the response status is 200 OK - @generated @skip @team:DataDog/service-catalog + @generated @skip @team:DataDog/idp Scenario: Preview catalog entities returns "Accepted" response Given new "PreviewCatalogEntities" request When the request is sent