From 033bab45c88eba9fc77bf2c3b49ecb30598cc20d Mon Sep 17 00:00:00 2001 From: "ci.datadog-api-spec" Date: Thu, 6 Mar 2025 10:25:01 +0000 Subject: [PATCH] Regenerate client from commit 57729e6b of spec repo --- .apigentools-info | 8 ++--- .../v2/ci_visibility_pipelines.feature | 30 +++++++++---------- .../features/v2/ci_visibility_tests.feature | 16 +++++----- .../features/v2/dora_metrics.feature | 12 ++++---- 4 files changed, 33 insertions(+), 33 deletions(-) diff --git a/.apigentools-info b/.apigentools-info index e6a8572bf44..4e769ef7d47 100644 --- a/.apigentools-info +++ b/.apigentools-info @@ -4,13 +4,13 @@ "spec_versions": { "v1": { "apigentools_version": "1.6.6", - "regenerated": "2025-03-05 21:00:33.112254", - "spec_repo_commit": "6105a175" + "regenerated": "2025-03-06 10:23:38.659455", + "spec_repo_commit": "57729e6b" }, "v2": { "apigentools_version": "1.6.6", - "regenerated": "2025-03-05 21:00:33.127833", - "spec_repo_commit": "6105a175" + "regenerated": "2025-03-06 10:23:38.674489", + "spec_repo_commit": "57729e6b" } } } \ No newline at end of file diff --git a/tests/scenarios/features/v2/ci_visibility_pipelines.feature b/tests/scenarios/features/v2/ci_visibility_pipelines.feature index 81bd36d12d5..fa0a20d1d5f 100644 --- a/tests/scenarios/features/v2/ci_visibility_pipelines.feature +++ b/tests/scenarios/features/v2/ci_visibility_pipelines.feature @@ -9,7 +9,7 @@ Feature: CI Visibility Pipelines Given a valid "apiKeyAuth" key in the system And an instance of "CIVisibilityPipelines" API - @generated @skip @team:Datadog/ci-app-backend + @generated @skip @team:DataDog/ci-app-backend Scenario: Aggregate pipelines events returns "Bad Request" response Given a valid "appKeyAuth" key in the system And new "AggregateCIAppPipelineEvents" request @@ -17,7 +17,7 @@ Feature: CI Visibility Pipelines When the request is sent Then the response status is 400 Bad Request - @team:Datadog/ci-app-backend + @team:DataDog/ci-app-backend Scenario: Aggregate pipelines events returns "OK" response Given a valid "appKeyAuth" key in the system And new "AggregateCIAppPipelineEvents" request @@ -26,14 +26,14 @@ Feature: CI Visibility Pipelines Then the response status is 200 OK And the response "meta.status" is equal to "done" - @generated @skip @team:Datadog/ci-app-backend + @generated @skip @team:DataDog/ci-app-backend Scenario: Get a list of pipelines events returns "Bad Request" response Given a valid "appKeyAuth" key in the system And new "ListCIAppPipelineEvents" request When the request is sent Then the response status is 400 Bad Request - @team:Datadog/ci-app-backend + @team:DataDog/ci-app-backend Scenario: Get a list of pipelines events returns "OK" response Given a valid "appKeyAuth" key in the system And new "ListCIAppPipelineEvents" request @@ -44,7 +44,7 @@ Feature: CI Visibility Pipelines When the request is sent Then the response status is 200 OK - @replay-only @skip-validation @team:Datadog/ci-app-backend @with-pagination + @replay-only @skip-validation @team:DataDog/ci-app-backend @with-pagination Scenario: Get a list of pipelines events returns "OK" response with pagination Given a valid "appKeyAuth" key in the system And new "ListCIAppPipelineEvents" request @@ -55,7 +55,7 @@ Feature: CI Visibility Pipelines Then the response status is 200 OK And the response has 2 items - @generated @skip @team:Datadog/ci-app-backend + @generated @skip @team:DataDog/ci-app-backend Scenario: Search pipelines events returns "Bad Request" response Given a valid "appKeyAuth" key in the system And new "SearchCIAppPipelineEvents" request @@ -63,7 +63,7 @@ Feature: CI Visibility Pipelines When the request is sent Then the response status is 400 Bad Request - @team:Datadog/ci-app-backend + @team:DataDog/ci-app-backend Scenario: Search pipelines events returns "OK" response Given a valid "appKeyAuth" key in the system And new "SearchCIAppPipelineEvents" request @@ -71,7 +71,7 @@ Feature: CI Visibility Pipelines When the request is sent Then the response status is 200 OK - @replay-only @skip-validation @team:Datadog/ci-app-backend @with-pagination + @replay-only @skip-validation @team:DataDog/ci-app-backend @with-pagination Scenario: Search pipelines events returns "OK" response with pagination Given a valid "appKeyAuth" key in the system And new "SearchCIAppPipelineEvents" request @@ -80,49 +80,49 @@ Feature: CI Visibility Pipelines Then the response status is 200 OK And the response has 2 items - @generated @skip @team:Datadog/ci-app-backend + @generated @skip @team:DataDog/ci-app-backend Scenario: Send pipeline event returns "Bad Request" response Given new "CreateCIAppPipelineEvent" request And body with value {"data": {"attributes": {"resource": "Details TBD"}, "type": "cipipeline_resource_request"}} When the request is sent Then the response status is 400 Bad Request - @generated @skip @team:Datadog/ci-app-backend + @generated @skip @team:DataDog/ci-app-backend Scenario: Send pipeline event returns "Payload Too Large" response Given new "CreateCIAppPipelineEvent" request And body with value {"data": {"attributes": {"resource": "Details TBD"}, "type": "cipipeline_resource_request"}} When the request is sent Then the response status is 413 Payload Too Large - @generated @skip @team:Datadog/ci-app-backend + @generated @skip @team:DataDog/ci-app-backend Scenario: Send pipeline event returns "Request Timeout" response Given new "CreateCIAppPipelineEvent" request And body with value {"data": {"attributes": {"resource": "Details TBD"}, "type": "cipipeline_resource_request"}} When the request is sent Then the response status is 408 Request Timeout - @team:Datadog/ci-app-backend + @team:DataDog/ci-app-backend Scenario: Send pipeline event returns "Request accepted for processing" response Given new "CreateCIAppPipelineEvent" request And body with value {"data": {"attributes": {"resource": {"level": "pipeline","unique_id": "3eacb6f3-ff04-4e10-8a9c-46e6d054024a","name": "Deploy to AWS","url": "https://my-ci-provider.example/pipelines/my-pipeline/run/1","start": "{{ timeISO('now - 120s') }}","end": "{{ timeISO('now - 30s') }}","status": "success","partial_retry": false,"git": {"repository_url": "https://github.com/DataDog/datadog-agent","sha": "7f263865994b76066c4612fd1965215e7dcb4cd2","author_email": "john.doe@email.com"}}},"type": "cipipeline_resource_request"}} When the request is sent Then the response status is 202 Request accepted for processing - @team:Datadog/ci-app-backend + @team:DataDog/ci-app-backend Scenario: Send pipeline event with custom provider returns "Request accepted for processing" response Given new "CreateCIAppPipelineEvent" request And body with value {"data": {"attributes": {"provider_name": "example-provider", "resource": {"level": "pipeline","unique_id": "3eacb6f3-ff04-4e10-8a9c-46e6d054024a","name": "Deploy to AWS","url": "https://my-ci-provider.example/pipelines/my-pipeline/run/1","start": "{{ timeISO('now - 120s') }}","end": "{{ timeISO('now - 30s') }}","status": "success","partial_retry": false,"git": {"repository_url": "https://github.com/DataDog/datadog-agent","sha": "7f263865994b76066c4612fd1965215e7dcb4cd2","author_email": "john.doe@email.com"}}},"type": "cipipeline_resource_request"}} When the request is sent Then the response status is 202 Request accepted for processing - @skip @team:Datadog/ci-app-backend + @skip @team:DataDog/ci-app-backend Scenario: Send pipeline job event returns "Request accepted for processing" response Given new "CreateCIAppPipelineEvent" request And body with value {"data": {"attributes": {"resource": {"level": "job", "id": "cf9456de-8b9e-4c27-aa79-27b1e78c1a33", "name": "Build image", "pipeline_unique_id": "3eacb6f3-ff04-4e10-8a9c-46e6d054024a", "pipeline_name": "Deploy to AWS", "start": "{{ timeISO('now - 120s') }}", "end": "{{ timeISO('now - 30s') }}", "status": "error", "url": "https://my-ci-provider.example/jobs/my-jobs/run/1"}}, "type": "cipipeline_resource_request"}} When the request is sent Then the response status is 202 Request accepted for processing - @team:Datadog/ci-app-backend + @team:DataDog/ci-app-backend Scenario: Send running pipeline event returns "Request accepted for processing" response Given new "CreateCIAppPipelineEvent" request And body with value {"data": {"attributes": {"resource": {"level": "pipeline","unique_id": "3eacb6f3-ff04-4e10-8a9c-46e6d054024a","name": "Deploy to AWS","url": "https://my-ci-provider.example/pipelines/my-pipeline/run/1","start": "{{ timeISO('now - 120s') }}","status": "running","partial_retry": false,"git": {"repository_url": "https://github.com/DataDog/datadog-agent","sha": "7f263865994b76066c4612fd1965215e7dcb4cd2","author_email": "john.doe@email.com"}}},"type": "cipipeline_resource_request"}} diff --git a/tests/scenarios/features/v2/ci_visibility_tests.feature b/tests/scenarios/features/v2/ci_visibility_tests.feature index 9d6f849b205..612c7780532 100644 --- a/tests/scenarios/features/v2/ci_visibility_tests.feature +++ b/tests/scenarios/features/v2/ci_visibility_tests.feature @@ -9,14 +9,14 @@ Feature: CI Visibility Tests And a valid "appKeyAuth" key in the system And an instance of "CIVisibilityTests" API - @generated @skip @team:Datadog/ci-app-backend + @generated @skip @team:DataDog/ci-app-backend Scenario: Aggregate tests events returns "Bad Request" response Given new "AggregateCIAppTestEvents" request And body with value {"compute": [{"aggregation": "pc90", "interval": "5m", "metric": "@duration", "type": "total"}], "filter": {"from": "now-15m", "query": "@test.service:web-ui-tests AND @test.status:fail", "to": "now"}, "group_by": [{"facet": "@test.service", "histogram": {"interval": 10, "max": 100, "min": 50}, "limit": 10, "sort": {"aggregation": "count", "order": "asc"}, "total": false}], "options": {"timezone": "GMT"}} When the request is sent Then the response status is 400 Bad Request - @team:Datadog/ci-app-backend + @team:DataDog/ci-app-backend Scenario: Aggregate tests events returns "OK" response Given new "AggregateCIAppTestEvents" request And body with value {"compute": [{"aggregation": "count", "metric": "@test.is_flaky", "type": "total"}], "filter": {"from": "now-15m", "query": "@language:(python OR go)", "to": "now"}, "group_by": [{"facet": "@git.branch", "limit": 10, "sort": {"order": "asc"}, "total": false}], "options": {"timezone": "GMT"}} @@ -24,13 +24,13 @@ Feature: CI Visibility Tests Then the response status is 200 OK And the response "meta.status" is equal to "done" - @generated @skip @team:Datadog/ci-app-backend + @generated @skip @team:DataDog/ci-app-backend Scenario: Get a list of tests events returns "Bad Request" response Given new "ListCIAppTestEvents" request When the request is sent Then the response status is 400 Bad Request - @team:Datadog/ci-app-backend + @team:DataDog/ci-app-backend Scenario: Get a list of tests events returns "OK" response Given new "ListCIAppTestEvents" request And request contains "filter[query]" parameter with value "@test.service:web-ui-tests" @@ -40,7 +40,7 @@ Feature: CI Visibility Tests When the request is sent Then the response status is 200 OK - @replay-only @skip-validation @team:Datadog/ci-app-backend @with-pagination + @replay-only @skip-validation @team:DataDog/ci-app-backend @with-pagination Scenario: Get a list of tests events returns "OK" response with pagination Given new "ListCIAppTestEvents" request And request contains "filter[from]" parameter with value "{{ timeISO('now - 30s') }}" @@ -50,21 +50,21 @@ Feature: CI Visibility Tests Then the response status is 200 OK And the response has 2 items - @generated @skip @team:Datadog/ci-app-backend + @generated @skip @team:DataDog/ci-app-backend Scenario: Search tests events returns "Bad Request" response Given new "SearchCIAppTestEvents" request And body with value {"filter": {"from": "now-15m", "query": "@test.service:web-ui-tests AND @test.status:fail", "to": "now"}, "options": {"timezone": "GMT"}, "page": {"cursor": "eyJzdGFydEF0IjoiQVFBQUFYS2tMS3pPbm40NGV3QUFBQUJCV0V0clRFdDZVbG8zY3pCRmNsbHJiVmxDWlEifQ==", "limit": 25}, "sort": "timestamp"} When the request is sent Then the response status is 400 Bad Request - @team:Datadog/ci-app-backend + @team:DataDog/ci-app-backend Scenario: Search tests events returns "OK" response Given new "SearchCIAppTestEvents" request And body with value {"filter": {"from": "now-15m", "query": "@test.service:web-ui-tests AND @test.status:skip", "to": "now"}, "options": {"timezone": "GMT"}, "page": {"limit": 25}, "sort": "timestamp"} When the request is sent Then the response status is 200 OK - @replay-only @skip-validation @team:Datadog/ci-app-backend @with-pagination + @replay-only @skip-validation @team:DataDog/ci-app-backend @with-pagination Scenario: Search tests events returns "OK" response with pagination Given new "SearchCIAppTestEvents" request And body with value {"filter": {"from": "now-15m", "query": "@test.status:pass AND -@language:python", "to": "now"}, "page": {"limit": 2}, "sort": "timestamp"} diff --git a/tests/scenarios/features/v2/dora_metrics.feature b/tests/scenarios/features/v2/dora_metrics.feature index 0bbd31d204f..79560d2dd04 100644 --- a/tests/scenarios/features/v2/dora_metrics.feature +++ b/tests/scenarios/features/v2/dora_metrics.feature @@ -8,7 +8,7 @@ Feature: DORA Metrics Given a valid "apiKeyAuth" key in the system And an instance of "DORAMetrics" API - @skip @team:Datadog/ci-app-backend + @skip @team:DataDog/ci-app-backend Scenario: Send a deployment event for DORA Metrics returns "Bad Request" response Given operation "CreateDORADeployment" enabled And new "CreateDORADeployment" request @@ -16,7 +16,7 @@ Feature: DORA Metrics When the request is sent Then the response status is 400 Bad Request - @skip @team:Datadog/ci-app-backend + @skip @team:DataDog/ci-app-backend Scenario: Send a deployment event for DORA Metrics returns "OK - but delayed due to incident" response Given operation "CreateDORADeployment" enabled And new "CreateDORADeployment" request @@ -24,7 +24,7 @@ Feature: DORA Metrics When the request is sent Then the response status is 202 OK - but delayed due to incident - @replay-only @team:Datadog/ci-app-backend + @replay-only @team:DataDog/ci-app-backend Scenario: Send a deployment event for DORA Metrics returns "OK" response Given operation "CreateDORADeployment" enabled And new "CreateDORADeployment" request @@ -32,7 +32,7 @@ Feature: DORA Metrics When the request is sent Then the response status is 200 OK - @skip @team:Datadog/ci-app-backend + @skip @team:DataDog/ci-app-backend Scenario: Send an incident event for DORA Metrics returns "Bad Request" response Given operation "CreateDORAIncident" enabled And new "CreateDORAIncident" request @@ -40,7 +40,7 @@ Feature: DORA Metrics When the request is sent Then the response status is 400 Bad Request - @generated @skip @team:Datadog/ci-app-backend + @generated @skip @team:DataDog/ci-app-backend Scenario: Send an incident event for DORA Metrics returns "OK - but delayed due to incident" response Given operation "CreateDORAIncident" enabled And new "CreateDORAIncident" request @@ -48,7 +48,7 @@ Feature: DORA Metrics When the request is sent Then the response status is 202 OK - but delayed due to incident - @replay-only @team:Datadog/ci-app-backend + @replay-only @team:DataDog/ci-app-backend Scenario: Send an incident event for DORA Metrics returns "OK" response Given operation "CreateDORAIncident" enabled And new "CreateDORAIncident" request