Skip to content

Commit 55fa1d7

Browse files
author
ci.datadog-api-spec
committed
Regenerate client from commit 72c09d6 of spec repo
1 parent 80a160e commit 55fa1d7

26 files changed

Lines changed: 1724 additions & 0 deletions

.generator/schemas/v2/openapi.yaml

Lines changed: 281 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -435,6 +435,14 @@ components:
435435
schema:
436436
example: "service:myservice"
437437
type: string
438+
EntityIntegrationConfigID:
439+
description: The identifier of the integration whose configuration is being managed. Supported values are `github`, `jira`, and `pagerduty`.
440+
in: path
441+
name: integration_id
442+
required: true
443+
schema:
444+
example: github
445+
type: string
438446
FastlyAccountID:
439447
description: Fastly Account id.
440448
in: path
@@ -27090,6 +27098,103 @@ components:
2709027098
description: Entity.
2709127099
type: string
2709227100
type: object
27101+
EntityIntegrationConfigAttributes:
27102+
description: The organization ID, integration identifier, and integration-specific configuration payload for an entity integration configuration.
27103+
properties:
27104+
config:
27105+
$ref: "#/components/schemas/EntityIntegrationConfigPayload"
27106+
integration_id:
27107+
description: The identifier of the integration this configuration applies to (for example, `github`, `jira`, or `pagerduty`).
27108+
example: github
27109+
type: string
27110+
org_id:
27111+
description: The Datadog organization identifier that owns this configuration.
27112+
example: 1234
27113+
format: int64
27114+
type: integer
27115+
required:
27116+
- org_id
27117+
- integration_id
27118+
- config
27119+
type: object
27120+
EntityIntegrationConfigData:
27121+
description: JSON:API resource object for an entity integration configuration.
27122+
properties:
27123+
attributes:
27124+
$ref: "#/components/schemas/EntityIntegrationConfigAttributes"
27125+
id:
27126+
description: Unique identifier of the entity integration configuration.
27127+
example: 01HJABCD12345678ABCDEFGHIJ
27128+
type: string
27129+
type:
27130+
$ref: "#/components/schemas/EntityIntegrationConfigType"
27131+
required:
27132+
- id
27133+
- type
27134+
- attributes
27135+
type: object
27136+
EntityIntegrationConfigPayload:
27137+
additionalProperties: {}
27138+
description: Integration-specific configuration payload. The shape of this object depends on the integration identified by the path parameter. For `github`, the object must contain an `enabled_repos` array. For `jira`, it must contain an `enabled_projects` array. For `pagerduty`, it must contain an `accounts` array.
27139+
example:
27140+
enabled_repos:
27141+
- github_org_name: myorg
27142+
hostname: github.com
27143+
repo_name: myrepo
27144+
type: object
27145+
EntityIntegrationConfigRequest:
27146+
description: Request body used to create or replace the configuration for a given integration.
27147+
properties:
27148+
data:
27149+
$ref: "#/components/schemas/EntityIntegrationConfigRequestData"
27150+
required:
27151+
- data
27152+
type: object
27153+
EntityIntegrationConfigRequestAttributes:
27154+
description: Attributes used to create or update an entity integration configuration.
27155+
properties:
27156+
config:
27157+
$ref: "#/components/schemas/EntityIntegrationConfigPayload"
27158+
required:
27159+
- config
27160+
type: object
27161+
EntityIntegrationConfigRequestData:
27162+
description: JSON:API resource object used in a request to create or update an entity integration configuration.
27163+
properties:
27164+
attributes:
27165+
$ref: "#/components/schemas/EntityIntegrationConfigRequestAttributes"
27166+
type:
27167+
$ref: "#/components/schemas/EntityIntegrationConfigRequestType"
27168+
required:
27169+
- type
27170+
- attributes
27171+
type: object
27172+
EntityIntegrationConfigRequestType:
27173+
default: entity_integration_config_requests
27174+
description: JSON:API resource type for the entity integration configuration create or update request. Always `entity_integration_config_requests`.
27175+
enum:
27176+
- entity_integration_config_requests
27177+
example: entity_integration_config_requests
27178+
type: string
27179+
x-enum-varnames:
27180+
- ENTITY_INTEGRATION_CONFIG_REQUESTS
27181+
EntityIntegrationConfigResponse:
27182+
description: JSON:API document containing a single entity integration configuration resource.
27183+
properties:
27184+
data:
27185+
$ref: "#/components/schemas/EntityIntegrationConfigData"
27186+
required:
27187+
- data
27188+
type: object
27189+
EntityIntegrationConfigType:
27190+
default: entity_integration_configs
27191+
description: JSON:API resource type for an entity integration configuration. Always `entity_integration_configs`.
27192+
enum:
27193+
- entity_integration_configs
27194+
example: entity_integration_configs
27195+
type: string
27196+
x-enum-varnames:
27197+
- ENTITY_INTEGRATION_CONFIGS
2709327198
EntityMeta:
2709427199
description: Entity metadata.
2709527200
properties:
@@ -113689,6 +113794,180 @@ paths:
113689113794
x-unstable: |-
113690113795
**Note**: This endpoint is in public beta and is subject to change.
113691113796
If you have any feedback, contact [Datadog support](https://docs.datadoghq.com/help/).
113797+
/api/v2/idp/entity_integrations/{integration_id}:
113798+
delete:
113799+
description: Delete the configuration stored for a given integration in the caller's organization.
113800+
operationId: DeleteEntityIntegrationConfig
113801+
parameters:
113802+
- $ref: "#/components/parameters/EntityIntegrationConfigID"
113803+
responses:
113804+
"204":
113805+
description: No Content
113806+
"400":
113807+
content:
113808+
application/json:
113809+
schema:
113810+
$ref: "#/components/schemas/JSONAPIErrorResponse"
113811+
description: Bad Request
113812+
"403":
113813+
$ref: "#/components/responses/NotAuthorizedResponse"
113814+
"404":
113815+
content:
113816+
application/json:
113817+
schema:
113818+
$ref: "#/components/schemas/JSONAPIErrorResponse"
113819+
description: Not Found
113820+
"429":
113821+
$ref: "#/components/responses/TooManyRequestsResponse"
113822+
summary: Delete an entity integration configuration
113823+
tags:
113824+
- Entity Integration Configs
113825+
x-permission:
113826+
operator: OR
113827+
permissions:
113828+
- manage_integrations
113829+
x-unstable: |-
113830+
**Note**: This endpoint is in preview and is subject to change.
113831+
If you have any feedback, contact [Datadog support](https://docs.datadoghq.com/help/).
113832+
get:
113833+
description: Retrieve the configuration currently stored for a given integration in the caller's organization. The integration is identified by the `integration_id` path parameter.
113834+
operationId: GetEntityIntegrationConfig
113835+
parameters:
113836+
- $ref: "#/components/parameters/EntityIntegrationConfigID"
113837+
responses:
113838+
"200":
113839+
content:
113840+
application/json:
113841+
example:
113842+
data:
113843+
attributes:
113844+
config:
113845+
enabled_repos:
113846+
- github_org_name: myorg
113847+
hostname: github.com
113848+
repo_name: myrepo
113849+
integration_id: github
113850+
org_id: 1234
113851+
id: 01HJABCD12345678ABCDEFGHIJ
113852+
type: entity_integration_configs
113853+
schema:
113854+
$ref: "#/components/schemas/EntityIntegrationConfigResponse"
113855+
description: OK
113856+
"400":
113857+
content:
113858+
application/json:
113859+
schema:
113860+
$ref: "#/components/schemas/JSONAPIErrorResponse"
113861+
description: Bad Request
113862+
"403":
113863+
$ref: "#/components/responses/NotAuthorizedResponse"
113864+
"404":
113865+
content:
113866+
application/json:
113867+
schema:
113868+
$ref: "#/components/schemas/JSONAPIErrorResponse"
113869+
description: Not Found
113870+
"429":
113871+
$ref: "#/components/responses/TooManyRequestsResponse"
113872+
summary: Get an entity integration configuration
113873+
tags:
113874+
- Entity Integration Configs
113875+
x-permission:
113876+
operator: OR
113877+
permissions:
113878+
- integrations_read
113879+
x-unstable: |-
113880+
**Note**: This endpoint is in preview and is subject to change.
113881+
If you have any feedback, contact [Datadog support](https://docs.datadoghq.com/help/).
113882+
put:
113883+
description: |-
113884+
Create or replace the configuration for a given integration in the caller's organization. The shape of `data.attributes.config` depends on the integration:
113885+
113886+
- For `github`: `config` must contain an `enabled_repos` array of objects with `hostname`, `github_org_name`, and `repo_name`.
113887+
- For `jira`: `config` must contain an `enabled_projects` array of objects with `hostname`, `account_id`, and `project_key`.
113888+
- For `pagerduty`: `config` must contain an `accounts` array of objects with a required `enabled` boolean and an optional `subdomain` string.
113889+
operationId: UpdateEntityIntegrationConfig
113890+
parameters:
113891+
- $ref: "#/components/parameters/EntityIntegrationConfigID"
113892+
requestBody:
113893+
content:
113894+
application/json:
113895+
examples:
113896+
default:
113897+
summary: GitHub integration configuration
113898+
value:
113899+
data:
113900+
attributes:
113901+
config:
113902+
enabled_repos:
113903+
- github_org_name: myorg
113904+
hostname: github.com
113905+
repo_name: myrepo
113906+
type: entity_integration_config_requests
113907+
jira:
113908+
summary: Jira integration configuration
113909+
value:
113910+
data:
113911+
attributes:
113912+
config:
113913+
enabled_projects:
113914+
- account_id: "123456789"
113915+
hostname: mycompany.atlassian.net
113916+
project_key: AAA
113917+
type: entity_integration_config_requests
113918+
pagerduty:
113919+
summary: PagerDuty integration configuration
113920+
value:
113921+
data:
113922+
attributes:
113923+
config:
113924+
accounts:
113925+
- enabled: true
113926+
subdomain: mycompany
113927+
type: entity_integration_config_requests
113928+
schema:
113929+
$ref: "#/components/schemas/EntityIntegrationConfigRequest"
113930+
required: true
113931+
responses:
113932+
"200":
113933+
content:
113934+
application/json:
113935+
example:
113936+
data:
113937+
attributes:
113938+
config:
113939+
enabled_repos:
113940+
- github_org_name: myorg
113941+
hostname: github.com
113942+
repo_name: myrepo
113943+
integration_id: github
113944+
org_id: 1234
113945+
id: 01HJABCD12345678ABCDEFGHIJ
113946+
type: entity_integration_configs
113947+
schema:
113948+
$ref: "#/components/schemas/EntityIntegrationConfigResponse"
113949+
description: OK
113950+
"400":
113951+
content:
113952+
application/json:
113953+
schema:
113954+
$ref: "#/components/schemas/JSONAPIErrorResponse"
113955+
description: Bad Request
113956+
"403":
113957+
$ref: "#/components/responses/NotAuthorizedResponse"
113958+
"429":
113959+
$ref: "#/components/responses/TooManyRequestsResponse"
113960+
summary: Create or update entity integration config
113961+
tags:
113962+
- Entity Integration Configs
113963+
x-codegen-request-body-name: body
113964+
x-permission:
113965+
operator: OR
113966+
permissions:
113967+
- integrations_read
113968+
x-unstable: |-
113969+
**Note**: This endpoint is in preview and is subject to change.
113970+
If you have any feedback, contact [Datadog support](https://docs.datadoghq.com/help/).
113692113971
/api/v2/incidents:
113693113972
get:
113694113973
description: >-
@@ -160136,6 +160415,8 @@ tags:
160136160415
scopes from alerting. Downtime settings, which can be scheduled with start and
160137160416
end times, prevent all alerting related to specified Datadog tags.
160138160417
name: Downtimes
160418+
- description: Manage per-integration configurations for the Internal Developer Portal (IDP). These configurations control which external resources (for example, GitHub repositories, Jira projects, or PagerDuty services) are synced as entities into the Software Catalog.
160419+
name: Entity Integration Configs
160139160420
- description: Retrieves security risk scores for entities in your organization.
160140160421
name: Entity Risk Scores
160141160422
- description: View and manage issues within Error Tracking. See the [Error Tracking page](https://docs.datadoghq.com/error_tracking/) for more information.
Lines changed: 77 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,77 @@
1+
@endpoint(entity-integration-configs) @endpoint(entity-integration-configs-v2)
2+
Feature: Entity Integration Configs
3+
Manage per-integration configurations for the Internal Developer Portal
4+
(IDP). These configurations control which external resources (for example,
5+
GitHub repositories, Jira projects, or PagerDuty services) are synced as
6+
entities into the Software Catalog.
7+
8+
Background:
9+
Given a valid "apiKeyAuth" key in the system
10+
And a valid "appKeyAuth" key in the system
11+
And an instance of "EntityIntegrationConfigs" API
12+
13+
@generated @skip @team:DataDog/idp
14+
Scenario: Create or update entity integration config returns "Bad Request" response
15+
Given operation "UpdateEntityIntegrationConfig" enabled
16+
And new "UpdateEntityIntegrationConfig" request
17+
And request contains "integration_id" parameter from "REPLACE.ME"
18+
And body with value {"data": {"attributes": {"config": {"enabled_repos": [{"github_org_name": "myorg", "hostname": "github.com", "repo_name": "myrepo"}]}}, "type": "entity_integration_config_requests"}}
19+
When the request is sent
20+
Then the response status is 400 Bad Request
21+
22+
@generated @skip @team:DataDog/idp
23+
Scenario: Create or update entity integration config returns "OK" response
24+
Given operation "UpdateEntityIntegrationConfig" enabled
25+
And new "UpdateEntityIntegrationConfig" request
26+
And request contains "integration_id" parameter from "REPLACE.ME"
27+
And body with value {"data": {"attributes": {"config": {"enabled_repos": [{"github_org_name": "myorg", "hostname": "github.com", "repo_name": "myrepo"}]}}, "type": "entity_integration_config_requests"}}
28+
When the request is sent
29+
Then the response status is 200 OK
30+
31+
@generated @skip @team:DataDog/idp
32+
Scenario: Delete an entity integration configuration returns "Bad Request" response
33+
Given operation "DeleteEntityIntegrationConfig" enabled
34+
And new "DeleteEntityIntegrationConfig" request
35+
And request contains "integration_id" parameter from "REPLACE.ME"
36+
When the request is sent
37+
Then the response status is 400 Bad Request
38+
39+
@generated @skip @team:DataDog/idp
40+
Scenario: Delete an entity integration configuration returns "No Content" response
41+
Given operation "DeleteEntityIntegrationConfig" enabled
42+
And new "DeleteEntityIntegrationConfig" request
43+
And request contains "integration_id" parameter from "REPLACE.ME"
44+
When the request is sent
45+
Then the response status is 204 No Content
46+
47+
@generated @skip @team:DataDog/idp
48+
Scenario: Delete an entity integration configuration returns "Not Found" response
49+
Given operation "DeleteEntityIntegrationConfig" enabled
50+
And new "DeleteEntityIntegrationConfig" request
51+
And request contains "integration_id" parameter from "REPLACE.ME"
52+
When the request is sent
53+
Then the response status is 404 Not Found
54+
55+
@generated @skip @team:DataDog/idp
56+
Scenario: Get an entity integration configuration returns "Bad Request" response
57+
Given operation "GetEntityIntegrationConfig" enabled
58+
And new "GetEntityIntegrationConfig" request
59+
And request contains "integration_id" parameter from "REPLACE.ME"
60+
When the request is sent
61+
Then the response status is 400 Bad Request
62+
63+
@generated @skip @team:DataDog/idp
64+
Scenario: Get an entity integration configuration returns "Not Found" response
65+
Given operation "GetEntityIntegrationConfig" enabled
66+
And new "GetEntityIntegrationConfig" request
67+
And request contains "integration_id" parameter from "REPLACE.ME"
68+
When the request is sent
69+
Then the response status is 404 Not Found
70+
71+
@generated @skip @team:DataDog/idp
72+
Scenario: Get an entity integration configuration returns "OK" response
73+
Given operation "GetEntityIntegrationConfig" enabled
74+
And new "GetEntityIntegrationConfig" request
75+
And request contains "integration_id" parameter from "REPLACE.ME"
76+
When the request is sent
77+
Then the response status is 200 OK

0 commit comments

Comments
 (0)