Skip to content

Commit

Permalink
Regenerate client from commit 3c19b3ae of spec repo
Browse files Browse the repository at this point in the history
  • Loading branch information
ci.datadog-api-spec committed Dec 13, 2024
1 parent 7c7141d commit 54e55bc
Show file tree
Hide file tree
Showing 2 changed files with 5 additions and 5 deletions.
8 changes: 4 additions & 4 deletions .apigentools-info
Original file line number Diff line number Diff line change
Expand Up @@ -4,13 +4,13 @@
"spec_versions": {
"v1": {
"apigentools_version": "1.6.6",
"regenerated": "2024-12-13 16:09:25.555961",
"spec_repo_commit": "936a5463"
"regenerated": "2024-12-13 22:22:56.163163",
"spec_repo_commit": "3c19b3ae"
},
"v2": {
"apigentools_version": "1.6.6",
"regenerated": "2024-12-13 16:09:25.575458",
"spec_repo_commit": "936a5463"
"regenerated": "2024-12-13 22:22:56.181421",
"spec_repo_commit": "3c19b3ae"
}
}
}
Original file line number Diff line number Diff line change
Expand Up @@ -108,7 +108,7 @@ Feature: CI Visibility Pipelines
When the request is sent
Then the response status is 202 Request accepted for processing

@skip @team:Datadog/ci-app-backend
@skip-typescript @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"}}
Expand Down

0 comments on commit 54e55bc

Please sign in to comment.