Skip to content

Commit 14ba80c

Browse files
author
ci.datadog-api-spec
committed
Regenerate client from commit f86caad5 of spec repo
1 parent 17d1de4 commit 14ba80c

20 files changed

+1534
-4
lines changed

‎.apigentools-info‎

Lines changed: 4 additions & 4 deletions
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-05-02 04:31:13.587503",
8-
"spec_repo_commit": "272cce39"
7+
"regenerated": "2025-05-05 16:42:27.124627",
8+
"spec_repo_commit": "f86caad5"
99
},
1010
"v2": {
1111
"apigentools_version": "1.6.6",
12-
"regenerated": "2025-05-02 04:31:13.603582",
13-
"spec_repo_commit": "272cce39"
12+
"regenerated": "2025-05-05 16:42:27.140163",
13+
"spec_repo_commit": "f86caad5"
1414
}
1515
}
1616
}

‎.generator/schemas/v2/openapi.yaml‎

Lines changed: 237 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -9200,6 +9200,111 @@ components:
92009200
id:
92019201
$ref: '#/components/schemas/ApiID'
92029202
type: object
9203+
CreatePageRequest:
9204+
description: Full request to trigger an On-Call page.
9205+
example:
9206+
data:
9207+
attributes:
9208+
description: Page details.
9209+
tags:
9210+
- service:test
9211+
target:
9212+
identifier: my-team
9213+
type: team_handle
9214+
title: Page title
9215+
urgency: low
9216+
type: pages
9217+
properties:
9218+
data:
9219+
$ref: '#/components/schemas/CreatePageRequestData'
9220+
type: object
9221+
CreatePageRequestData:
9222+
description: The main request body, including attributes and resource type.
9223+
properties:
9224+
attributes:
9225+
$ref: '#/components/schemas/CreatePageRequestDataAttributes'
9226+
type:
9227+
$ref: '#/components/schemas/CreatePageRequestDataType'
9228+
required:
9229+
- type
9230+
type: object
9231+
CreatePageRequestDataAttributes:
9232+
description: Details about the On-Call Page you want to create.
9233+
properties:
9234+
description:
9235+
description: A short summary of the issue or context.
9236+
type: string
9237+
tags:
9238+
description: Tags to help categorize or filter the page.
9239+
items:
9240+
type: string
9241+
type: array
9242+
target:
9243+
$ref: '#/components/schemas/CreatePageRequestDataAttributesTarget'
9244+
title:
9245+
description: The title of the page.
9246+
example: 'Service: Test is down'
9247+
type: string
9248+
urgency:
9249+
description: The level of urgency for the alert. Possible value `low` or
9250+
`high`.
9251+
example: high
9252+
type: string
9253+
required:
9254+
- target
9255+
- title
9256+
- urgency
9257+
type: object
9258+
CreatePageRequestDataAttributesTarget:
9259+
description: Information about the target to notify (such as a team or user).
9260+
properties:
9261+
identifier:
9262+
description: A unique ID for the target (for example, team handle or user
9263+
UUID).
9264+
type: string
9265+
type:
9266+
description: The kind of target, `team_uuid` | `team_handle` | `user_uuid`.
9267+
type: string
9268+
type: object
9269+
CreatePageRequestDataType:
9270+
default: pages
9271+
description: The type of resource used when creating an On-Call page.
9272+
enum:
9273+
- pages
9274+
example: pages
9275+
type: string
9276+
x-enum-varnames:
9277+
- PAGES
9278+
CreatePageResponse:
9279+
description: The full response object after creating a new On-Call page.
9280+
example:
9281+
data:
9282+
id: 15e74b8b-f865-48d0-bcc5-453323ed2c8f
9283+
type: pages
9284+
properties:
9285+
data:
9286+
$ref: '#/components/schemas/CreatePageResponseData'
9287+
type: object
9288+
CreatePageResponseData:
9289+
description: The information returned after successfully creating a page.
9290+
properties:
9291+
id:
9292+
description: The unique ID of the created page.
9293+
type: string
9294+
type:
9295+
$ref: '#/components/schemas/CreatePageResponseDataType'
9296+
required:
9297+
- type
9298+
type: object
9299+
CreatePageResponseDataType:
9300+
default: pages
9301+
description: The type of resource used when creating an On-Call page.
9302+
enum:
9303+
- pages
9304+
example: pages
9305+
type: string
9306+
x-enum-varnames:
9307+
- PAGES
92039308
CreateRuleRequest:
92049309
description: Scorecard create rule request.
92059310
properties:
@@ -50952,6 +51057,136 @@ paths:
5095251057
summary: Update on-call escalation policy
5095351058
tags:
5095451059
- On-Call
51060+
/api/v2/on-call/pages:
51061+
post:
51062+
description: Trigger a new On-Call page.
51063+
operationId: CreateOnCallPage
51064+
requestBody:
51065+
content:
51066+
application/json:
51067+
schema:
51068+
$ref: '#/components/schemas/CreatePageRequest'
51069+
required: true
51070+
responses:
51071+
'200':
51072+
content:
51073+
application/json:
51074+
schema:
51075+
$ref: '#/components/schemas/CreatePageResponse'
51076+
description: OK.
51077+
'429':
51078+
$ref: '#/components/responses/TooManyRequestsResponse'
51079+
security:
51080+
- apiKeyAuth: []
51081+
appKeyAuth: []
51082+
- AuthZ: []
51083+
summary: Create on call page
51084+
tags:
51085+
- On-Call Paging
51086+
/api/v2/on-call/pages/{page_id}/acknowledge:
51087+
post:
51088+
description: Acknowledges an On-Call page.
51089+
operationId: AcknowledgeOnCallPage
51090+
parameters:
51091+
- description: The page ID.
51092+
in: path
51093+
name: page_id
51094+
required: true
51095+
schema:
51096+
example: 15e74b8b-f865-48d0-bcc5-453323ed2c8f
51097+
format: uuid
51098+
type: string
51099+
responses:
51100+
'202':
51101+
description: Accepted.
51102+
'429':
51103+
$ref: '#/components/responses/TooManyRequestsResponse'
51104+
security:
51105+
- apiKeyAuth: []
51106+
appKeyAuth: []
51107+
- AuthZ: []
51108+
summary: Acknowledge on call page
51109+
tags:
51110+
- On-Call Paging
51111+
/api/v2/on-call/pages/{page_id}/escalate:
51112+
post:
51113+
description: Escalates an On-Call page.
51114+
operationId: EscalateOnCallPage
51115+
parameters:
51116+
- description: The page ID.
51117+
in: path
51118+
name: page_id
51119+
required: true
51120+
schema:
51121+
example: 15e74b8b-f865-48d0-bcc5-453323ed2c8f
51122+
format: uuid
51123+
type: string
51124+
responses:
51125+
'202':
51126+
description: Accepted.
51127+
'429':
51128+
$ref: '#/components/responses/TooManyRequestsResponse'
51129+
security:
51130+
- apiKeyAuth: []
51131+
appKeyAuth: []
51132+
- AuthZ: []
51133+
servers:
51134+
- url: https://{site}
51135+
variables:
51136+
site:
51137+
default: navy.oncall.datadoghq.com
51138+
description: The globally available endpoint for On-Call.
51139+
enum:
51140+
- saffron.oncall.datadoghq.com
51141+
- navy.oncall.datadoghq.com
51142+
- coral.oncall.datadoghq.com
51143+
- teal.oncall.datadoghq.com
51144+
- ivory.oncall.datadoghq.eu
51145+
- beige.oncall.datadoghq.eu
51146+
- url: '{protocol}://{name}'
51147+
variables:
51148+
name:
51149+
default: api.datadoghq.com
51150+
description: Full site DNS name.
51151+
protocol:
51152+
default: https
51153+
description: The protocol for accessing the API.
51154+
- url: https://{subdomain}.{site}
51155+
variables:
51156+
site:
51157+
default: datadoghq.com
51158+
description: Any Datadog deployment.
51159+
subdomain:
51160+
default: api
51161+
description: The subdomain where the API is deployed.
51162+
summary: Escalate on call page
51163+
tags:
51164+
- On-Call Paging
51165+
/api/v2/on-call/pages/{page_id}/resolve:
51166+
post:
51167+
description: Resolves an On-Call page.
51168+
operationId: ResolveOnCallPage
51169+
parameters:
51170+
- description: The page ID.
51171+
in: path
51172+
name: page_id
51173+
required: true
51174+
schema:
51175+
example: 15e74b8b-f865-48d0-bcc5-453323ed2c8f
51176+
format: uuid
51177+
type: string
51178+
responses:
51179+
'202':
51180+
description: Accepted.
51181+
'429':
51182+
$ref: '#/components/responses/TooManyRequestsResponse'
51183+
security:
51184+
- apiKeyAuth: []
51185+
appKeyAuth: []
51186+
- AuthZ: []
51187+
summary: Resolve on call page
51188+
tags:
51189+
- On-Call Paging
5095551190
/api/v2/on-call/schedules:
5095651191
post:
5095751192
description: Create a new on-call schedule
@@ -60865,6 +61100,8 @@ tags:
6086561100
externalDocs:
6086661101
url: https://docs.datadoghq.com/service_management/on-call/
6086761102
name: On-Call
61103+
- description: Auto-generated tag On-Call Paging.
61104+
name: On-Call Paging
6086861105
- description: 'Configure your [Datadog Opsgenie integration](https://docs.datadoghq.com/integrations/opsgenie/)
6086961106

6087061107
directly through the Datadog API.'

‎examples/v2/on-call-paging/AcknowledgeOnCallPage.rb‎

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,5 @@
1+
# Acknowledge on call page returns "Accepted." response
2+
3+
require "datadog_api_client"
4+
api_instance = DatadogAPIClient::V2::On - CallPagingAPI.new
5+
p api_instance.acknowledge_on_call_page("15e74b8b-f865-48d0-bcc5-453323ed2c8f")

‎examples/v2/on-call-paging/CreateOnCallPage.rb‎

Lines changed: 23 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,23 @@
1+
# Create on call page returns "OK." response
2+
3+
require "datadog_api_client"
4+
api_instance = DatadogAPIClient::V2::On - CallPagingAPI.new
5+
6+
body = DatadogAPIClient::V2::CreatePageRequest.new({
7+
data: DatadogAPIClient::V2::CreatePageRequestData.new({
8+
attributes: DatadogAPIClient::V2::CreatePageRequestDataAttributes.new({
9+
description: "Page details.",
10+
tags: [
11+
"service:test",
12+
],
13+
target: DatadogAPIClient::V2::CreatePageRequestDataAttributesTarget.new({
14+
identifier: "my-team",
15+
type: "team_handle",
16+
}),
17+
title: "Page title",
18+
urgency: "low",
19+
}),
20+
type: DatadogAPIClient::V2::CreatePageRequestDataType::PAGES,
21+
}),
22+
})
23+
p api_instance.create_on_call_page(body)

‎examples/v2/on-call-paging/EscalateOnCallPage.rb‎

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,5 @@
1+
# Escalate on call page returns "Accepted." response
2+
3+
require "datadog_api_client"
4+
api_instance = DatadogAPIClient::V2::On - CallPagingAPI.new
5+
p api_instance.escalate_on_call_page("15e74b8b-f865-48d0-bcc5-453323ed2c8f")

‎examples/v2/on-call-paging/ResolveOnCallPage.rb‎

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,5 @@
1+
# Resolve on call page returns "Accepted." response
2+
3+
require "datadog_api_client"
4+
api_instance = DatadogAPIClient::V2::On - CallPagingAPI.new
5+
p api_instance.resolve_on_call_page("15e74b8b-f865-48d0-bcc5-453323ed2c8f")

‎features/scenarios_model_mapping.rb‎

Lines changed: 12 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -2071,6 +2071,18 @@
20712071
"schedule_id" => "String",
20722072
"body" => "ScheduleUpdateRequest",
20732073
},
2074+
"v2.CreateOnCallPage" => {
2075+
"body" => "CreatePageRequest",
2076+
},
2077+
"v2.AcknowledgeOnCallPage" => {
2078+
"page_id" => "UUID",
2079+
},
2080+
"v2.EscalateOnCallPage" => {
2081+
"page_id" => "UUID",
2082+
},
2083+
"v2.ResolveOnCallPage" => {
2084+
"page_id" => "UUID",
2085+
},
20742086
"v2.GetOrgConfig" => {
20752087
"org_config_name" => "String",
20762088
},

‎features/v2/on-call_paging.feature‎

Lines changed: 36 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,36 @@
1+
@endpoint(on-call-paging) @endpoint(on-call-paging-v2)
2+
Feature: On-Call Paging
3+
Auto-generated tag On-Call Paging.
4+
5+
Background:
6+
Given a valid "apiKeyAuth" key in the system
7+
And a valid "appKeyAuth" key in the system
8+
And an instance of "On-CallPaging" API
9+
10+
@generated @skip @team:DataDog/bugle
11+
Scenario: Acknowledge on call page returns "Accepted." response
12+
Given new "AcknowledgeOnCallPage" request
13+
And request contains "page_id" parameter from "REPLACE.ME"
14+
When the request is sent
15+
Then the response status is 202 Accepted.
16+
17+
@generated @skip @team:DataDog/bugle
18+
Scenario: Create on call page returns "OK." response
19+
Given new "CreateOnCallPage" request
20+
And body with value {"data": {"attributes": {"description": "Page details.", "tags": ["service:test"], "target": {"identifier": "my-team", "type": "team_handle"}, "title": "Page title", "urgency": "low"}, "type": "pages"}}
21+
When the request is sent
22+
Then the response status is 200 OK.
23+
24+
@generated @skip @team:DataDog/bugle
25+
Scenario: Escalate on call page returns "Accepted." response
26+
Given new "EscalateOnCallPage" request
27+
And request contains "page_id" parameter from "REPLACE.ME"
28+
When the request is sent
29+
Then the response status is 202 Accepted.
30+
31+
@generated @skip @team:DataDog/bugle
32+
Scenario: Resolve on call page returns "Accepted." response
33+
Given new "ResolveOnCallPage" request
34+
And request contains "page_id" parameter from "REPLACE.ME"
35+
When the request is sent
36+
Then the response status is 202 Accepted.

0 commit comments

Comments
 (0)