Skip to content

Commit 48ea258

Browse files
author
ci.datadog-api-spec
committed
Regenerate client from commit 5fe872b4 of spec repo
1 parent 457818b commit 48ea258

File tree

2 files changed

+6
-6
lines changed

2 files changed

+6
-6
lines changed

.apigentools-info

+4-4
Original file line numberDiff line numberDiff line change
@@ -4,13 +4,13 @@
44
"spec_versions": {
55
"v1": {
66
"apigentools_version": "1.6.6",
7-
"regenerated": "2025-04-14 16:33:07.855657",
8-
"spec_repo_commit": "c0287407"
7+
"regenerated": "2025-04-15 01:04:52.623740",
8+
"spec_repo_commit": "5fe872b4"
99
},
1010
"v2": {
1111
"apigentools_version": "1.6.6",
12-
"regenerated": "2025-04-14 16:33:07.871722",
13-
"spec_repo_commit": "c0287407"
12+
"regenerated": "2025-04-15 01:04:52.639334",
13+
"spec_repo_commit": "5fe872b4"
1414
}
1515
}
1616
}

src/test/resources/com/datadog/api/client/v2/api/on-call.feature

+2-2
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ Feature: On-Call
1616
When the request is sent
1717
Then the response status is 400 Bad Request
1818

19-
@skip-python @team:DataDog/bugle
19+
@team:DataDog/bugle
2020
Scenario: Create on-call schedule returns "Created" response
2121
Given new "CreateOnCallSchedule" request
2222
And there is a valid "user" in the system
@@ -71,7 +71,7 @@ Feature: On-Call
7171
When the request is sent
7272
Then the response status is 404 Not Found
7373

74-
@skip-python @team:DataDog/bugle
74+
@team:DataDog/bugle
7575
Scenario: Update on-call schedule returns "OK" response
7676
Given new "UpdateOnCallSchedule" request
7777
And there is a valid "schedule" in the system

0 commit comments

Comments
 (0)