Skip to content

Commit d7ca20f

Browse files
author
ci.datadog-api-spec
committed
Regenerate client from commit 863c0c0c of spec repo
1 parent 33cb27f commit d7ca20f

20 files changed

+1532
-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-04-29 18:57:43.172744",
8-
"spec_repo_commit": "d1252b21"
7+
"regenerated": "2025-04-30 13:11:59.627733",
8+
"spec_repo_commit": "863c0c0c"
99
},
1010
"v2": {
1111
"apigentools_version": "1.6.6",
12-
"regenerated": "2025-04-29 18:57:43.188311",
13-
"spec_repo_commit": "d1252b21"
12+
"regenerated": "2025-04-30 13:11:59.644494",
13+
"spec_repo_commit": "863c0c0c"
1414
}
1515
}
1616
}

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

Lines changed: 235 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -9064,6 +9064,109 @@ components:
90649064
id:
90659065
$ref: '#/components/schemas/ApiID'
90669066
type: object
9067+
CreatePageRequest:
9068+
description: The definition of `CreatePageRequest` object.
9069+
example:
9070+
data:
9071+
attributes:
9072+
description: Page details
9073+
tags:
9074+
- service:test
9075+
target:
9076+
identifier: my-team
9077+
type: team_handle
9078+
title: Page title
9079+
urgency: low
9080+
type: pages
9081+
properties:
9082+
data:
9083+
$ref: '#/components/schemas/CreatePageRequestData'
9084+
type: object
9085+
CreatePageRequestData:
9086+
description: The definition of `CreatePageRequestData` object.
9087+
properties:
9088+
attributes:
9089+
$ref: '#/components/schemas/CreatePageRequestDataAttributes'
9090+
type:
9091+
$ref: '#/components/schemas/CreatePageRequestDataType'
9092+
required:
9093+
- type
9094+
type: object
9095+
CreatePageRequestDataAttributes:
9096+
description: The definition of `CreatePageRequestDataAttributes` object.
9097+
properties:
9098+
description:
9099+
description: The `attributes` `description`.
9100+
type: string
9101+
tags:
9102+
description: The `attributes` `tags`.
9103+
items:
9104+
type: string
9105+
type: array
9106+
target:
9107+
$ref: '#/components/schemas/CreatePageRequestDataAttributesTarget'
9108+
title:
9109+
description: The `attributes` `title`.
9110+
example: ''
9111+
type: string
9112+
urgency:
9113+
description: The `attributes` `urgency`.
9114+
example: ''
9115+
type: string
9116+
required:
9117+
- target
9118+
- title
9119+
- urgency
9120+
type: object
9121+
CreatePageRequestDataAttributesTarget:
9122+
description: The definition of `CreatePageRequestDataAttributesTarget` object.
9123+
properties:
9124+
identifier:
9125+
description: The `target` `identifier`.
9126+
type: string
9127+
type:
9128+
description: The `target` `type`.
9129+
type: string
9130+
type: object
9131+
CreatePageRequestDataType:
9132+
default: pages
9133+
description: Pages resource type.
9134+
enum:
9135+
- pages
9136+
example: pages
9137+
type: string
9138+
x-enum-varnames:
9139+
- PAGES
9140+
CreatePageResponse:
9141+
description: The definition of `CreatePageResponse` object.
9142+
example:
9143+
data:
9144+
id: 15e74b8b-f865-48d0-bcc5-453323ed2c8f
9145+
type: pages
9146+
properties:
9147+
data:
9148+
$ref: '#/components/schemas/CreatePageResponseData'
9149+
type: object
9150+
CreatePageResponseData:
9151+
description: The definition of `CreatePageResponseData` object.
9152+
properties:
9153+
id:
9154+
description: The `CreatePageResponseData` `id`.
9155+
type: string
9156+
type:
9157+
$ref: '#/components/schemas/CreatePageResponseDataType'
9158+
required:
9159+
- type
9160+
type: object
9161+
CreatePageResponseDataType:
9162+
default: pages
9163+
description: Pages resource type.
9164+
enum:
9165+
- pages
9166+
example: pages
9167+
type: string
9168+
x-enum-varnames:
9169+
- PAGES
90679170
CreateRuleRequest:
90689171
description: Scorecard create rule request.
90699172
properties:
@@ -50655,6 +50758,136 @@ paths:
5065550758
summary: Update on-call escalation policy
5065650759
tags:
5065750760
- On-Call
50761+
/api/v2/on-call/pages:
50762+
post:
50763+
description: Trigger a new On-Call page
50764+
operationId: CreateOnCallPage
50765+
requestBody:
50766+
content:
50767+
application/json:
50768+
schema:
50769+
$ref: '#/components/schemas/CreatePageRequest'
50770+
required: true
50771+
responses:
50772+
'200':
50773+
content:
50774+
application/json:
50775+
schema:
50776+
$ref: '#/components/schemas/CreatePageResponse'
50777+
description: OK
50778+
'429':
50779+
$ref: '#/components/responses/TooManyRequestsResponse'
50780+
security:
50781+
- apiKeyAuth: []
50782+
appKeyAuth: []
50783+
- AuthZ: []
50784+
summary: Create on call page
50785+
tags:
50786+
- On-Call Paging
50787+
/api/v2/on-call/pages/{page_id}/acknowledge:
50788+
post:
50789+
description: Acknowledges an On-Call page
50790+
operationId: AcknowledgeOnCallPage
50791+
parameters:
50792+
- description: The page ID
50793+
in: path
50794+
name: page_id
50795+
required: true
50796+
schema:
50797+
example: 15e74b8b-f865-48d0-bcc5-453323ed2c8f
50798+
format: uuid
50799+
type: string
50800+
responses:
50801+
'202':
50802+
description: Accepted
50803+
'429':
50804+
$ref: '#/components/responses/TooManyRequestsResponse'
50805+
security:
50806+
- apiKeyAuth: []
50807+
appKeyAuth: []
50808+
- AuthZ: []
50809+
summary: Acknowledge on call page
50810+
tags:
50811+
- On-Call Paging
50812+
/api/v2/on-call/pages/{page_id}/escalate:
50813+
post:
50814+
description: Escalates an On-Call page
50815+
operationId: EscalateOnCallPage
50816+
parameters:
50817+
- description: The page ID
50818+
in: path
50819+
name: page_id
50820+
required: true
50821+
schema:
50822+
example: 15e74b8b-f865-48d0-bcc5-453323ed2c8f
50823+
format: uuid
50824+
type: string
50825+
responses:
50826+
'202':
50827+
description: Accepted
50828+
'429':
50829+
$ref: '#/components/responses/TooManyRequestsResponse'
50830+
security:
50831+
- apiKeyAuth: []
50832+
appKeyAuth: []
50833+
- AuthZ: []
50834+
servers:
50835+
- url: https://{site}
50836+
variables:
50837+
site:
50838+
default: navy.oncall.datadoghq.com
50839+
description: The globally available endpoint for On-Call.
50840+
enum:
50841+
- saffron.oncall.datadoghq.com
50842+
- navy.oncall.datadoghq.com
50843+
- coral.oncall.datadoghq.com
50844+
- teal.oncall.datadoghq.com
50845+
- ivory.oncall.datadoghq.eu
50846+
- beige.oncall.datadoghq.eu
50847+
- url: '{protocol}://{name}'
50848+
variables:
50849+
name:
50850+
default: api.datadoghq.com
50851+
description: Full site DNS name.
50852+
protocol:
50853+
default: https
50854+
description: The protocol for accessing the API.
50855+
- url: https://{subdomain}.{site}
50856+
variables:
50857+
site:
50858+
default: datadoghq.com
50859+
description: Any Datadog deployment.
50860+
subdomain:
50861+
default: api
50862+
description: The subdomain where the API is deployed.
50863+
summary: Escalate on call page
50864+
tags:
50865+
- On-Call Paging
50866+
/api/v2/on-call/pages/{page_id}/resolve:
50867+
post:
50868+
description: Resolves an On-Call page
50869+
operationId: ResolveOnCallPage
50870+
parameters:
50871+
- description: The page ID
50872+
in: path
50873+
name: page_id
50874+
required: true
50875+
schema:
50876+
example: 15e74b8b-f865-48d0-bcc5-453323ed2c8f
50877+
format: uuid
50878+
type: string
50879+
responses:
50880+
'202':
50881+
description: Accepted
50882+
'429':
50883+
$ref: '#/components/responses/TooManyRequestsResponse'
50884+
security:
50885+
- apiKeyAuth: []
50886+
appKeyAuth: []
50887+
- AuthZ: []
50888+
summary: Resolve on call page
50889+
tags:
50890+
- On-Call Paging
5065850891
/api/v2/on-call/schedules:
5065950892
post:
5066050893
description: Create a new on-call schedule
@@ -60568,6 +60801,8 @@ tags:
6056860801
externalDocs:
6056960802
url: https://docs.datadoghq.com/service_management/on-call/
6057060803
name: On-Call
60804+
- description: Auto-generated tag On-Call Paging
60805+
name: On-Call Paging
6057160806
- description: 'Configure your [Datadog Opsgenie integration](https://docs.datadoghq.com/integrations/opsgenie/)
6057260807

6057360808
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
@@ -2062,6 +2062,18 @@
20622062
"schedule_id" => "String",
20632063
"body" => "ScheduleUpdateRequest",
20642064
},
2065+
"v2.CreateOnCallPage" => {
2066+
"body" => "CreatePageRequest",
2067+
},
2068+
"v2.AcknowledgeOnCallPage" => {
2069+
"page_id" => "UUID",
2070+
},
2071+
"v2.EscalateOnCallPage" => {
2072+
"page_id" => "UUID",
2073+
},
2074+
"v2.ResolveOnCallPage" => {
2075+
"page_id" => "UUID",
2076+
},
20652077
"v2.GetOrgConfig" => {
20662078
"org_config_name" => "String",
20672079
},

‎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)