WARNING: THIS SITE IS A MIRROR OF GITHUB.COM / IT CANNOT LOGIN OR REGISTER ACCOUNTS / THE CONTENTS ARE PROVIDED AS-IS / THIS SITE ASSUMES NO RESPONSIBILITY FOR ANY DISPLAYED CONTENT OR LINKS / IF YOU FOUND SOMETHING MAY NOT GOOD FOR EVERYONE, CONTACT ADMIN AT ilovescratch@foxmail.com
Skip to content

Commit 1026baa

Browse files
author
ci.datadog-api-spec
committed
Regenerate client from commit 4a9638a of spec repo
1 parent 4243f11 commit 1026baa

File tree

41 files changed

+0
-2904
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

41 files changed

+0
-2904
lines changed

.generator/schemas/v2/openapi.yaml

Lines changed: 0 additions & 216 deletions
Original file line numberDiff line numberDiff line change
@@ -5300,49 +5300,6 @@ components:
53005300
required:
53015301
- findings
53025302
type: object
5303-
AttachJiraIssueRequest:
5304-
description: Request for attaching security findings to a Jira issue.
5305-
properties:
5306-
data:
5307-
$ref: '#/components/schemas/AttachJiraIssueRequestData'
5308-
type: object
5309-
AttachJiraIssueRequestData:
5310-
description: Data of the Jira issue to attach security findings to.
5311-
properties:
5312-
attributes:
5313-
$ref: '#/components/schemas/AttachJiraIssueRequestDataAttributes'
5314-
id:
5315-
description: The unique identifier of the Jira issue attachment request.
5316-
example: j1234567-89ab-cdef-0123-456789abcdef
5317-
type: string
5318-
relationships:
5319-
$ref: '#/components/schemas/AttachJiraIssueRequestDataRelationships'
5320-
type:
5321-
$ref: '#/components/schemas/JiraIssuesDataType'
5322-
required:
5323-
- type
5324-
type: object
5325-
AttachJiraIssueRequestDataAttributes:
5326-
description: Attributes of the Jira issue to attach security findings to.
5327-
properties:
5328-
jira_issue_url:
5329-
description: The URL of the Jira issue to attach security findings to.
5330-
example: https://domain.atlassian.net/browse/PROJ-123
5331-
type: string
5332-
required:
5333-
- jira_issue_url
5334-
type: object
5335-
AttachJiraIssueRequestDataRelationships:
5336-
description: Relationships of the Jira issue to attach security findings to.
5337-
properties:
5338-
findings:
5339-
$ref: '#/components/schemas/Findings'
5340-
project:
5341-
$ref: '#/components/schemas/CaseManagementProject'
5342-
required:
5343-
- findings
5344-
- project
5345-
type: object
53465303
AuditLogsEvent:
53475304
description: Object description of an Audit Logs event after it is processed
53485305
and stored by Datadog.
@@ -13200,89 +13157,6 @@ components:
1320013157
required:
1320113158
- data
1320213159
type: object
13203-
CreateJiraIssueRequestArray:
13204-
description: List of requests to create Jira issues for security findings.
13205-
properties:
13206-
data:
13207-
items:
13208-
$ref: '#/components/schemas/CreateJiraIssueRequestData'
13209-
type: array
13210-
included:
13211-
items:
13212-
$ref: '#/components/schemas/CreateJiraIssueRequestArrayIncluded'
13213-
type: array
13214-
required:
13215-
- data
13216-
type: object
13217-
CreateJiraIssueRequestArrayIncluded:
13218-
description: 'Attributes and relationships of the case linked to the Jira issue.
13219-
Should contain all of the following: case, project, and security findings.'
13220-
oneOf:
13221-
- $ref: '#/components/schemas/CreateCaseRequestData'
13222-
- $ref: '#/components/schemas/CaseManagementProjectData'
13223-
- $ref: '#/components/schemas/FindingData'
13224-
CreateJiraIssueRequestData:
13225-
description: Data of the Jira issue to create.
13226-
properties:
13227-
attributes:
13228-
$ref: '#/components/schemas/CreateJiraIssueRequestDataAttributes'
13229-
id:
13230-
description: The unique identifier of the Jira issue creation request.
13231-
example: j1234567-89ab-cdef-0123-456789abcdef
13232-
type: string
13233-
relationships:
13234-
$ref: '#/components/schemas/CreateJiraIssueRequestDataRelationships'
13235-
type:
13236-
$ref: '#/components/schemas/JiraIssuesDataType'
13237-
required:
13238-
- type
13239-
type: object
13240-
CreateJiraIssueRequestDataAttributes:
13241-
description: Attributes of the Jira issue to create.
13242-
properties:
13243-
fields:
13244-
$ref: '#/components/schemas/CreateJiraIssueRequestDataAttributesFields'
13245-
type: object
13246-
CreateJiraIssueRequestDataAttributesFields:
13247-
description: Custom fields of the Jira issue to create. For the list of available
13248-
fields, see [Jira documentation](https://developer.atlassian.com/cloud/jira/platform/rest/v2/api-group-issues/#api-rest-api-2-issue-createmeta-projectidorkey-issuetypes-issuetypeid-get).
13249-
properties:
13250-
fields:
13251-
example:
13252-
customfield_10001: Value 1
13253-
customfield_10002:
13254-
- Value 2
13255-
- Value 3
13256-
type: object
13257-
type: object
13258-
CreateJiraIssueRequestDataRelationships:
13259-
description: Relationships of the Jira issue to create.
13260-
properties:
13261-
case:
13262-
$ref: '#/components/schemas/CreateJiraIssueRequestDataRelationshipsCase'
13263-
required:
13264-
- case
13265-
type: object
13266-
CreateJiraIssueRequestDataRelationshipsCase:
13267-
description: Case linked to the Jira issue.
13268-
properties:
13269-
data:
13270-
$ref: '#/components/schemas/CreateJiraIssueRequestDataRelationshipsCaseData'
13271-
required:
13272-
- data
13273-
type: object
13274-
CreateJiraIssueRequestDataRelationshipsCaseData:
13275-
description: Case linked to the Jira issue.
13276-
properties:
13277-
id:
13278-
example: c1234567-89ab-cdef-0123-456789abcdef
13279-
type: string
13280-
type:
13281-
$ref: '#/components/schemas/CaseDataType'
13282-
required:
13283-
- type
13284-
- id
13285-
type: object
1328613160
CreateNotificationRuleParameters:
1328713161
description: Body of the notification rule create request.
1328813162
properties:
@@ -29414,15 +29288,6 @@ components:
2941429288
description: Jira project key
2941529289
type: string
2941629290
type: object
29417-
JiraIssuesDataType:
29418-
default: jira_issues
29419-
description: Jira issues resource type.
29420-
enum:
29421-
- jira_issues
29422-
example: jira_issues
29423-
type: string
29424-
x-enum-varnames:
29425-
- JIRA_ISSUES
2942629291
JobCreateResponse:
2942729292
description: Run a threat hunting job response.
2942829293
properties:
@@ -79797,87 +79662,6 @@ paths:
7979779662
permissions:
7979879663
- security_monitoring_findings_write
7979979664
- appsec_vm_write
79800-
/api/v2/security/findings/jira_issues:
79801-
patch:
79802-
description: Attach security findings to a Jira issue by providing the Jira
79803-
issue URL. You can attach up to 50 security findings per Jira issue. If the
79804-
Jira issue is not linked to any case, this operation will create a case for
79805-
the security findings and link the Jira issue to the newly created case. Security
79806-
findings that are already attached to another Jira issue will be detached
79807-
from their previous Jira issue and attached to the specified Jira issue.
79808-
operationId: AttachJiraIssue
79809-
requestBody:
79810-
content:
79811-
application/json:
79812-
schema:
79813-
$ref: '#/components/schemas/AttachJiraIssueRequest'
79814-
required: true
79815-
responses:
79816-
'200':
79817-
content:
79818-
application/json:
79819-
schema:
79820-
$ref: '#/components/schemas/FindingCaseResponse'
79821-
description: OK
79822-
'400':
79823-
$ref: '#/components/responses/BadRequestResponse'
79824-
'404':
79825-
$ref: '#/components/responses/NotFoundResponse'
79826-
'429':
79827-
$ref: '#/components/responses/TooManyRequestsResponse'
79828-
security:
79829-
- apiKeyAuth: []
79830-
appKeyAuth: []
79831-
- AuthZ: []
79832-
summary: Attach security findings to a Jira issue
79833-
tags:
79834-
- Security Monitoring
79835-
x-codegen-request-body-name: body
79836-
x-permission:
79837-
operator: OR
79838-
permissions:
79839-
- security_monitoring_findings_write
79840-
- appsec_vm_write
79841-
post:
79842-
description: Create Jira issues for security findings. This operation creates
79843-
a case in Datadog and a Jira issue linked to that case for bidirectional sync
79844-
between Datadog and Jira. You can create up to 50 Jira issues per request
79845-
and associate up to 50 security findings per Jira issue. Security findings
79846-
that are already attached to another Jira issue will be detached from their
79847-
previous Jira issue and attached to the newly created Jira issue.
79848-
operationId: CreateJiraIssues
79849-
requestBody:
79850-
content:
79851-
application/json:
79852-
schema:
79853-
$ref: '#/components/schemas/CreateJiraIssueRequestArray'
79854-
required: true
79855-
responses:
79856-
'201':
79857-
content:
79858-
application/json:
79859-
schema:
79860-
$ref: '#/components/schemas/FindingCaseResponseArray'
79861-
description: Created
79862-
'400':
79863-
$ref: '#/components/responses/BadRequestResponse'
79864-
'404':
79865-
$ref: '#/components/responses/NotFoundResponse'
79866-
'429':
79867-
$ref: '#/components/responses/TooManyRequestsResponse'
79868-
security:
79869-
- apiKeyAuth: []
79870-
appKeyAuth: []
79871-
- AuthZ: []
79872-
summary: Create Jira issues for security findings
79873-
tags:
79874-
- Security Monitoring
79875-
x-codegen-request-body-name: body
79876-
x-permission:
79877-
operator: OR
79878-
permissions:
79879-
- security_monitoring_findings_write
79880-
- appsec_vm_write
7988179665
/api/v2/security/sboms:
7988279666
get:
7988379667
description: 'Get a list of assets SBOMs for an organization.

0 commit comments

Comments
 (0)