@incident-io/sdk 2.33.0 → 2.35.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/dist/cjs/apis/EscalationsV2Api.d.ts +2 -2
- package/dist/cjs/apis/EscalationsV2Api.js +2 -2
- package/dist/cjs/models/AuditLogCodeRepositoryAccessedMetadataV2.d.ts +50 -0
- package/dist/cjs/models/AuditLogCodeRepositoryAccessedMetadataV2.js +62 -0
- package/dist/cjs/models/AuditLogsCodeRepositoryAccessedV1.d.ts +58 -0
- package/dist/cjs/models/AuditLogsCodeRepositoryAccessedV1.js +79 -0
- package/dist/cjs/models/index.d.ts +2 -0
- package/dist/cjs/models/index.js +2 -0
- package/dist/cjs/version.d.ts +1 -1
- package/dist/cjs/version.js +1 -1
- package/dist/esm/apis/EscalationsV2Api.d.ts +2 -2
- package/dist/esm/apis/EscalationsV2Api.js +2 -2
- package/dist/esm/models/AuditLogCodeRepositoryAccessedMetadataV2.d.ts +50 -0
- package/dist/esm/models/AuditLogCodeRepositoryAccessedMetadataV2.js +55 -0
- package/dist/esm/models/AuditLogsCodeRepositoryAccessedV1.d.ts +58 -0
- package/dist/esm/models/AuditLogsCodeRepositoryAccessedV1.js +72 -0
- package/dist/esm/models/index.d.ts +2 -0
- package/dist/esm/models/index.js +2 -0
- package/dist/esm/version.d.ts +1 -1
- package/dist/esm/version.js +1 -1
- package/package.json +1 -1
|
@@ -270,12 +270,12 @@ export declare class EscalationsV2Api extends runtime.BaseAPI {
|
|
|
270
270
|
*/
|
|
271
271
|
escalationsV2ReassignEscalationRequestOpts(requestParameters: EscalationsV2ReassignEscalationRequest): Promise<runtime.RequestOpts>;
|
|
272
272
|
/**
|
|
273
|
-
* Reassign an escalation to a different escalation path or set of users. Use this when a page reached the wrong people. Reassigning creates a new escalation aimed at the targets you give, linked back to the original, and carries over the original\'s title, description, priority, incident and alert so the page stays attached to the same alert and acknowledgements keep grouping under it. You must provide either an escalation_path_id OR user_ids, but not both. Both name incident.io escalation paths and users, so an escalation cannot be reassigned to an external escalator such as PagerDuty or Opsgenie. By default the original escalation is resolved, so the first targets stop being paged. Pass resolve_original=false to leave it running alongside the new one. Resolving the original additionally needs the \"escalations.respond\" permission, since it stops a page someone else may be responding to. An escalation can only be reassigned once: calling this again for the same escalation is rejected. Retrying a request whose response you never saw is safe in the sense that matters — a reassignment that already happened is never repeated, so nobody is paged twice — but the retry is rejected rather than returning the escalation the first call created, so keep the ID from the original response. To use this API, you will need an API key with the \"Create and manage escalations\" permission. The reassignment is attributed to the key; to attribute it to one of your users instead, set the X-Incident-User header, which needs the \"api_keys.act_on_behalf_of_users\" scope. If your API key\'s permissions are scoped to teams, the escalation you\'re reassigning must be owned by one of those teams, and you can only reassign via an escalation path one of them owns. Reassigning directly to user_ids needs the permission at the account level, because an escalation aimed at a person has no owning team.
|
|
273
|
+
* Reassign an escalation to a different escalation path or set of users. Use this when a page reached the wrong people. Reassigning creates a new escalation aimed at the targets you give, linked back to the original, and carries over the original\'s title, description, priority, incident and alert so the page stays attached to the same alert and acknowledgements keep grouping under it. You must provide either an escalation_path_id OR user_ids, but not both. Both name incident.io escalation paths and users, so an escalation cannot be reassigned to an external escalator such as PagerDuty or Opsgenie. By default the original escalation is resolved, so the first targets stop being paged. Pass resolve_original=false to leave it running alongside the new one. Resolving the original additionally needs the \"escalations.respond\" permission, since it stops a page someone else may be responding to. An escalation can only be reassigned once: calling this again for the same escalation is rejected. Retrying a request whose response you never saw is safe in the sense that matters — a reassignment that already happened is never repeated, so nobody is paged twice — but the retry is rejected rather than returning the escalation the first call created, so keep the ID from the original response. To use this API, you will need an API key with the \"Create and manage escalations\" permission. The reassignment is attributed to the key; to attribute it to one of your users instead, set the X-Incident-User header, which needs the \"api_keys.act_on_behalf_of_users\" scope and no team permissions on the key. If your API key\'s permissions are scoped to teams, the escalation you\'re reassigning must be owned by one of those teams, and you can only reassign via an escalation path one of them owns. Reassigning directly to user_ids needs the permission at the account level, because an escalation aimed at a person has no owning team.
|
|
274
274
|
* ReassignEscalation Escalations V2
|
|
275
275
|
*/
|
|
276
276
|
escalationsV2ReassignEscalationRaw(requestParameters: EscalationsV2ReassignEscalationRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<EscalationsReassignEscalationResultV2>>;
|
|
277
277
|
/**
|
|
278
|
-
* Reassign an escalation to a different escalation path or set of users. Use this when a page reached the wrong people. Reassigning creates a new escalation aimed at the targets you give, linked back to the original, and carries over the original\'s title, description, priority, incident and alert so the page stays attached to the same alert and acknowledgements keep grouping under it. You must provide either an escalation_path_id OR user_ids, but not both. Both name incident.io escalation paths and users, so an escalation cannot be reassigned to an external escalator such as PagerDuty or Opsgenie. By default the original escalation is resolved, so the first targets stop being paged. Pass resolve_original=false to leave it running alongside the new one. Resolving the original additionally needs the \"escalations.respond\" permission, since it stops a page someone else may be responding to. An escalation can only be reassigned once: calling this again for the same escalation is rejected. Retrying a request whose response you never saw is safe in the sense that matters — a reassignment that already happened is never repeated, so nobody is paged twice — but the retry is rejected rather than returning the escalation the first call created, so keep the ID from the original response. To use this API, you will need an API key with the \"Create and manage escalations\" permission. The reassignment is attributed to the key; to attribute it to one of your users instead, set the X-Incident-User header, which needs the \"api_keys.act_on_behalf_of_users\" scope. If your API key\'s permissions are scoped to teams, the escalation you\'re reassigning must be owned by one of those teams, and you can only reassign via an escalation path one of them owns. Reassigning directly to user_ids needs the permission at the account level, because an escalation aimed at a person has no owning team.
|
|
278
|
+
* Reassign an escalation to a different escalation path or set of users. Use this when a page reached the wrong people. Reassigning creates a new escalation aimed at the targets you give, linked back to the original, and carries over the original\'s title, description, priority, incident and alert so the page stays attached to the same alert and acknowledgements keep grouping under it. You must provide either an escalation_path_id OR user_ids, but not both. Both name incident.io escalation paths and users, so an escalation cannot be reassigned to an external escalator such as PagerDuty or Opsgenie. By default the original escalation is resolved, so the first targets stop being paged. Pass resolve_original=false to leave it running alongside the new one. Resolving the original additionally needs the \"escalations.respond\" permission, since it stops a page someone else may be responding to. An escalation can only be reassigned once: calling this again for the same escalation is rejected. Retrying a request whose response you never saw is safe in the sense that matters — a reassignment that already happened is never repeated, so nobody is paged twice — but the retry is rejected rather than returning the escalation the first call created, so keep the ID from the original response. To use this API, you will need an API key with the \"Create and manage escalations\" permission. The reassignment is attributed to the key; to attribute it to one of your users instead, set the X-Incident-User header, which needs the \"api_keys.act_on_behalf_of_users\" scope and no team permissions on the key. If your API key\'s permissions are scoped to teams, the escalation you\'re reassigning must be owned by one of those teams, and you can only reassign via an escalation path one of them owns. Reassigning directly to user_ids needs the permission at the account level, because an escalation aimed at a person has no owning team.
|
|
279
279
|
* ReassignEscalation Escalations V2
|
|
280
280
|
*/
|
|
281
281
|
escalationsV2ReassignEscalation(requestParameters: EscalationsV2ReassignEscalationRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<EscalationsReassignEscalationResultV2>;
|
|
@@ -422,7 +422,7 @@ class EscalationsV2Api extends runtime.BaseAPI {
|
|
|
422
422
|
};
|
|
423
423
|
}
|
|
424
424
|
/**
|
|
425
|
-
* Reassign an escalation to a different escalation path or set of users. Use this when a page reached the wrong people. Reassigning creates a new escalation aimed at the targets you give, linked back to the original, and carries over the original\'s title, description, priority, incident and alert so the page stays attached to the same alert and acknowledgements keep grouping under it. You must provide either an escalation_path_id OR user_ids, but not both. Both name incident.io escalation paths and users, so an escalation cannot be reassigned to an external escalator such as PagerDuty or Opsgenie. By default the original escalation is resolved, so the first targets stop being paged. Pass resolve_original=false to leave it running alongside the new one. Resolving the original additionally needs the \"escalations.respond\" permission, since it stops a page someone else may be responding to. An escalation can only be reassigned once: calling this again for the same escalation is rejected. Retrying a request whose response you never saw is safe in the sense that matters — a reassignment that already happened is never repeated, so nobody is paged twice — but the retry is rejected rather than returning the escalation the first call created, so keep the ID from the original response. To use this API, you will need an API key with the \"Create and manage escalations\" permission. The reassignment is attributed to the key; to attribute it to one of your users instead, set the X-Incident-User header, which needs the \"api_keys.act_on_behalf_of_users\" scope. If your API key\'s permissions are scoped to teams, the escalation you\'re reassigning must be owned by one of those teams, and you can only reassign via an escalation path one of them owns. Reassigning directly to user_ids needs the permission at the account level, because an escalation aimed at a person has no owning team.
|
|
425
|
+
* Reassign an escalation to a different escalation path or set of users. Use this when a page reached the wrong people. Reassigning creates a new escalation aimed at the targets you give, linked back to the original, and carries over the original\'s title, description, priority, incident and alert so the page stays attached to the same alert and acknowledgements keep grouping under it. You must provide either an escalation_path_id OR user_ids, but not both. Both name incident.io escalation paths and users, so an escalation cannot be reassigned to an external escalator such as PagerDuty or Opsgenie. By default the original escalation is resolved, so the first targets stop being paged. Pass resolve_original=false to leave it running alongside the new one. Resolving the original additionally needs the \"escalations.respond\" permission, since it stops a page someone else may be responding to. An escalation can only be reassigned once: calling this again for the same escalation is rejected. Retrying a request whose response you never saw is safe in the sense that matters — a reassignment that already happened is never repeated, so nobody is paged twice — but the retry is rejected rather than returning the escalation the first call created, so keep the ID from the original response. To use this API, you will need an API key with the \"Create and manage escalations\" permission. The reassignment is attributed to the key; to attribute it to one of your users instead, set the X-Incident-User header, which needs the \"api_keys.act_on_behalf_of_users\" scope and no team permissions on the key. If your API key\'s permissions are scoped to teams, the escalation you\'re reassigning must be owned by one of those teams, and you can only reassign via an escalation path one of them owns. Reassigning directly to user_ids needs the permission at the account level, because an escalation aimed at a person has no owning team.
|
|
426
426
|
* ReassignEscalation Escalations V2
|
|
427
427
|
*/
|
|
428
428
|
async escalationsV2ReassignEscalationRaw(requestParameters, initOverrides) {
|
|
@@ -431,7 +431,7 @@ class EscalationsV2Api extends runtime.BaseAPI {
|
|
|
431
431
|
return new runtime.JSONApiResponse(response, (jsonValue) => (0, EscalationsReassignEscalationResultV2_js_1.EscalationsReassignEscalationResultV2FromJSON)(jsonValue));
|
|
432
432
|
}
|
|
433
433
|
/**
|
|
434
|
-
* Reassign an escalation to a different escalation path or set of users. Use this when a page reached the wrong people. Reassigning creates a new escalation aimed at the targets you give, linked back to the original, and carries over the original\'s title, description, priority, incident and alert so the page stays attached to the same alert and acknowledgements keep grouping under it. You must provide either an escalation_path_id OR user_ids, but not both. Both name incident.io escalation paths and users, so an escalation cannot be reassigned to an external escalator such as PagerDuty or Opsgenie. By default the original escalation is resolved, so the first targets stop being paged. Pass resolve_original=false to leave it running alongside the new one. Resolving the original additionally needs the \"escalations.respond\" permission, since it stops a page someone else may be responding to. An escalation can only be reassigned once: calling this again for the same escalation is rejected. Retrying a request whose response you never saw is safe in the sense that matters — a reassignment that already happened is never repeated, so nobody is paged twice — but the retry is rejected rather than returning the escalation the first call created, so keep the ID from the original response. To use this API, you will need an API key with the \"Create and manage escalations\" permission. The reassignment is attributed to the key; to attribute it to one of your users instead, set the X-Incident-User header, which needs the \"api_keys.act_on_behalf_of_users\" scope. If your API key\'s permissions are scoped to teams, the escalation you\'re reassigning must be owned by one of those teams, and you can only reassign via an escalation path one of them owns. Reassigning directly to user_ids needs the permission at the account level, because an escalation aimed at a person has no owning team.
|
|
434
|
+
* Reassign an escalation to a different escalation path or set of users. Use this when a page reached the wrong people. Reassigning creates a new escalation aimed at the targets you give, linked back to the original, and carries over the original\'s title, description, priority, incident and alert so the page stays attached to the same alert and acknowledgements keep grouping under it. You must provide either an escalation_path_id OR user_ids, but not both. Both name incident.io escalation paths and users, so an escalation cannot be reassigned to an external escalator such as PagerDuty or Opsgenie. By default the original escalation is resolved, so the first targets stop being paged. Pass resolve_original=false to leave it running alongside the new one. Resolving the original additionally needs the \"escalations.respond\" permission, since it stops a page someone else may be responding to. An escalation can only be reassigned once: calling this again for the same escalation is rejected. Retrying a request whose response you never saw is safe in the sense that matters — a reassignment that already happened is never repeated, so nobody is paged twice — but the retry is rejected rather than returning the escalation the first call created, so keep the ID from the original response. To use this API, you will need an API key with the \"Create and manage escalations\" permission. The reassignment is attributed to the key; to attribute it to one of your users instead, set the X-Incident-User header, which needs the \"api_keys.act_on_behalf_of_users\" scope and no team permissions on the key. If your API key\'s permissions are scoped to teams, the escalation you\'re reassigning must be owned by one of those teams, and you can only reassign via an escalation path one of them owns. Reassigning directly to user_ids needs the permission at the account level, because an escalation aimed at a person has no owning team.
|
|
435
435
|
* ReassignEscalation Escalations V2
|
|
436
436
|
*/
|
|
437
437
|
async escalationsV2ReassignEscalation(requestParameters, initOverrides) {
|
|
@@ -0,0 +1,50 @@
|
|
|
1
|
+
/**
|
|
2
|
+
* incident.io
|
|
3
|
+
* No description provided (generated by Openapi Generator https://github.com/openapitools/openapi-generator)
|
|
4
|
+
*
|
|
5
|
+
* The version of the OpenAPI document: 1.0.0
|
|
6
|
+
*
|
|
7
|
+
*
|
|
8
|
+
* NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
|
|
9
|
+
* https://openapi-generator.tech
|
|
10
|
+
* Do not edit the class manually.
|
|
11
|
+
*/
|
|
12
|
+
/**
|
|
13
|
+
*
|
|
14
|
+
* @export
|
|
15
|
+
* @interface AuditLogCodeRepositoryAccessedMetadataV2
|
|
16
|
+
*/
|
|
17
|
+
export interface AuditLogCodeRepositoryAccessedMetadataV2 {
|
|
18
|
+
/**
|
|
19
|
+
* ID of the alert the run was for, when known
|
|
20
|
+
*/
|
|
21
|
+
alert_id?: string;
|
|
22
|
+
/**
|
|
23
|
+
* ID of the incident the run was for, when known
|
|
24
|
+
*/
|
|
25
|
+
incident_id?: string;
|
|
26
|
+
/**
|
|
27
|
+
* ID of the investigation, when an investigation read the repository
|
|
28
|
+
*/
|
|
29
|
+
investigation_id?: string;
|
|
30
|
+
/**
|
|
31
|
+
* The commit the run checked out
|
|
32
|
+
*/
|
|
33
|
+
revision_sha: string;
|
|
34
|
+
/**
|
|
35
|
+
* The kind of agent run that read the repository (investigation, chat, code_agent)
|
|
36
|
+
*/
|
|
37
|
+
run_type: string;
|
|
38
|
+
/**
|
|
39
|
+
* ID of the user who asked, when a chat read the repository
|
|
40
|
+
*/
|
|
41
|
+
user_id?: string;
|
|
42
|
+
}
|
|
43
|
+
/**
|
|
44
|
+
* Check if a given object implements the AuditLogCodeRepositoryAccessedMetadataV2 interface.
|
|
45
|
+
*/
|
|
46
|
+
export declare function instanceOfAuditLogCodeRepositoryAccessedMetadataV2(value: object): value is AuditLogCodeRepositoryAccessedMetadataV2;
|
|
47
|
+
export declare function AuditLogCodeRepositoryAccessedMetadataV2FromJSON(json: any): AuditLogCodeRepositoryAccessedMetadataV2;
|
|
48
|
+
export declare function AuditLogCodeRepositoryAccessedMetadataV2FromJSONTyped(json: any, ignoreDiscriminator: boolean): AuditLogCodeRepositoryAccessedMetadataV2;
|
|
49
|
+
export declare function AuditLogCodeRepositoryAccessedMetadataV2ToJSON(json: any): AuditLogCodeRepositoryAccessedMetadataV2;
|
|
50
|
+
export declare function AuditLogCodeRepositoryAccessedMetadataV2ToJSONTyped(value?: AuditLogCodeRepositoryAccessedMetadataV2 | null, ignoreDiscriminator?: boolean): any;
|
|
@@ -0,0 +1,62 @@
|
|
|
1
|
+
"use strict";
|
|
2
|
+
/* tslint:disable */
|
|
3
|
+
/* eslint-disable */
|
|
4
|
+
/**
|
|
5
|
+
* incident.io
|
|
6
|
+
* No description provided (generated by Openapi Generator https://github.com/openapitools/openapi-generator)
|
|
7
|
+
*
|
|
8
|
+
* The version of the OpenAPI document: 1.0.0
|
|
9
|
+
*
|
|
10
|
+
*
|
|
11
|
+
* NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
|
|
12
|
+
* https://openapi-generator.tech
|
|
13
|
+
* Do not edit the class manually.
|
|
14
|
+
*/
|
|
15
|
+
Object.defineProperty(exports, "__esModule", { value: true });
|
|
16
|
+
exports.instanceOfAuditLogCodeRepositoryAccessedMetadataV2 = instanceOfAuditLogCodeRepositoryAccessedMetadataV2;
|
|
17
|
+
exports.AuditLogCodeRepositoryAccessedMetadataV2FromJSON = AuditLogCodeRepositoryAccessedMetadataV2FromJSON;
|
|
18
|
+
exports.AuditLogCodeRepositoryAccessedMetadataV2FromJSONTyped = AuditLogCodeRepositoryAccessedMetadataV2FromJSONTyped;
|
|
19
|
+
exports.AuditLogCodeRepositoryAccessedMetadataV2ToJSON = AuditLogCodeRepositoryAccessedMetadataV2ToJSON;
|
|
20
|
+
exports.AuditLogCodeRepositoryAccessedMetadataV2ToJSONTyped = AuditLogCodeRepositoryAccessedMetadataV2ToJSONTyped;
|
|
21
|
+
/**
|
|
22
|
+
* Check if a given object implements the AuditLogCodeRepositoryAccessedMetadataV2 interface.
|
|
23
|
+
*/
|
|
24
|
+
function instanceOfAuditLogCodeRepositoryAccessedMetadataV2(value) {
|
|
25
|
+
if (!('revision_sha' in value) || value['revision_sha'] === undefined)
|
|
26
|
+
return false;
|
|
27
|
+
if (!('run_type' in value) || value['run_type'] === undefined)
|
|
28
|
+
return false;
|
|
29
|
+
return true;
|
|
30
|
+
}
|
|
31
|
+
function AuditLogCodeRepositoryAccessedMetadataV2FromJSON(json) {
|
|
32
|
+
return AuditLogCodeRepositoryAccessedMetadataV2FromJSONTyped(json, false);
|
|
33
|
+
}
|
|
34
|
+
function AuditLogCodeRepositoryAccessedMetadataV2FromJSONTyped(json, ignoreDiscriminator) {
|
|
35
|
+
if (json == null) {
|
|
36
|
+
return json;
|
|
37
|
+
}
|
|
38
|
+
return {
|
|
39
|
+
'alert_id': json['alert_id'] == null ? undefined : json['alert_id'],
|
|
40
|
+
'incident_id': json['incident_id'] == null ? undefined : json['incident_id'],
|
|
41
|
+
'investigation_id': json['investigation_id'] == null ? undefined : json['investigation_id'],
|
|
42
|
+
'revision_sha': json['revision_sha'],
|
|
43
|
+
'run_type': json['run_type'],
|
|
44
|
+
'user_id': json['user_id'] == null ? undefined : json['user_id'],
|
|
45
|
+
};
|
|
46
|
+
}
|
|
47
|
+
function AuditLogCodeRepositoryAccessedMetadataV2ToJSON(json) {
|
|
48
|
+
return AuditLogCodeRepositoryAccessedMetadataV2ToJSONTyped(json, false);
|
|
49
|
+
}
|
|
50
|
+
function AuditLogCodeRepositoryAccessedMetadataV2ToJSONTyped(value, ignoreDiscriminator = false) {
|
|
51
|
+
if (value == null) {
|
|
52
|
+
return value;
|
|
53
|
+
}
|
|
54
|
+
return {
|
|
55
|
+
'alert_id': value['alert_id'],
|
|
56
|
+
'incident_id': value['incident_id'],
|
|
57
|
+
'investigation_id': value['investigation_id'],
|
|
58
|
+
'revision_sha': value['revision_sha'],
|
|
59
|
+
'run_type': value['run_type'],
|
|
60
|
+
'user_id': value['user_id'],
|
|
61
|
+
};
|
|
62
|
+
}
|
|
@@ -0,0 +1,58 @@
|
|
|
1
|
+
/**
|
|
2
|
+
* incident.io
|
|
3
|
+
* No description provided (generated by Openapi Generator https://github.com/openapitools/openapi-generator)
|
|
4
|
+
*
|
|
5
|
+
* The version of the OpenAPI document: 1.0.0
|
|
6
|
+
*
|
|
7
|
+
*
|
|
8
|
+
* NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
|
|
9
|
+
* https://openapi-generator.tech
|
|
10
|
+
* Do not edit the class manually.
|
|
11
|
+
*/
|
|
12
|
+
import type { AuditLogActorV2 } from './AuditLogActorV2.js';
|
|
13
|
+
import type { AuditLogEntryContextV2 } from './AuditLogEntryContextV2.js';
|
|
14
|
+
import type { AuditLogCodeRepositoryAccessedMetadataV2 } from './AuditLogCodeRepositoryAccessedMetadataV2.js';
|
|
15
|
+
import type { AuditLogTargetV2 } from './AuditLogTargetV2.js';
|
|
16
|
+
/**
|
|
17
|
+
*
|
|
18
|
+
* @export
|
|
19
|
+
* @interface AuditLogsCodeRepositoryAccessedV1
|
|
20
|
+
*/
|
|
21
|
+
export interface AuditLogsCodeRepositoryAccessedV1 {
|
|
22
|
+
/**
|
|
23
|
+
* The type of log entry that this is
|
|
24
|
+
*/
|
|
25
|
+
action: string;
|
|
26
|
+
/**
|
|
27
|
+
*
|
|
28
|
+
*/
|
|
29
|
+
actor: AuditLogActorV2;
|
|
30
|
+
/**
|
|
31
|
+
*
|
|
32
|
+
*/
|
|
33
|
+
context: AuditLogEntryContextV2;
|
|
34
|
+
/**
|
|
35
|
+
*
|
|
36
|
+
*/
|
|
37
|
+
metadata: AuditLogCodeRepositoryAccessedMetadataV2;
|
|
38
|
+
/**
|
|
39
|
+
* When the entry occurred
|
|
40
|
+
*/
|
|
41
|
+
occurred_at: Date;
|
|
42
|
+
/**
|
|
43
|
+
* The custom field that was created
|
|
44
|
+
*/
|
|
45
|
+
targets: Array<AuditLogTargetV2>;
|
|
46
|
+
/**
|
|
47
|
+
* Which version the event is
|
|
48
|
+
*/
|
|
49
|
+
version: number;
|
|
50
|
+
}
|
|
51
|
+
/**
|
|
52
|
+
* Check if a given object implements the AuditLogsCodeRepositoryAccessedV1 interface.
|
|
53
|
+
*/
|
|
54
|
+
export declare function instanceOfAuditLogsCodeRepositoryAccessedV1(value: object): value is AuditLogsCodeRepositoryAccessedV1;
|
|
55
|
+
export declare function AuditLogsCodeRepositoryAccessedV1FromJSON(json: any): AuditLogsCodeRepositoryAccessedV1;
|
|
56
|
+
export declare function AuditLogsCodeRepositoryAccessedV1FromJSONTyped(json: any, ignoreDiscriminator: boolean): AuditLogsCodeRepositoryAccessedV1;
|
|
57
|
+
export declare function AuditLogsCodeRepositoryAccessedV1ToJSON(json: any): AuditLogsCodeRepositoryAccessedV1;
|
|
58
|
+
export declare function AuditLogsCodeRepositoryAccessedV1ToJSONTyped(value?: AuditLogsCodeRepositoryAccessedV1 | null, ignoreDiscriminator?: boolean): any;
|
|
@@ -0,0 +1,79 @@
|
|
|
1
|
+
"use strict";
|
|
2
|
+
/* tslint:disable */
|
|
3
|
+
/* eslint-disable */
|
|
4
|
+
/**
|
|
5
|
+
* incident.io
|
|
6
|
+
* No description provided (generated by Openapi Generator https://github.com/openapitools/openapi-generator)
|
|
7
|
+
*
|
|
8
|
+
* The version of the OpenAPI document: 1.0.0
|
|
9
|
+
*
|
|
10
|
+
*
|
|
11
|
+
* NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
|
|
12
|
+
* https://openapi-generator.tech
|
|
13
|
+
* Do not edit the class manually.
|
|
14
|
+
*/
|
|
15
|
+
Object.defineProperty(exports, "__esModule", { value: true });
|
|
16
|
+
exports.instanceOfAuditLogsCodeRepositoryAccessedV1 = instanceOfAuditLogsCodeRepositoryAccessedV1;
|
|
17
|
+
exports.AuditLogsCodeRepositoryAccessedV1FromJSON = AuditLogsCodeRepositoryAccessedV1FromJSON;
|
|
18
|
+
exports.AuditLogsCodeRepositoryAccessedV1FromJSONTyped = AuditLogsCodeRepositoryAccessedV1FromJSONTyped;
|
|
19
|
+
exports.AuditLogsCodeRepositoryAccessedV1ToJSON = AuditLogsCodeRepositoryAccessedV1ToJSON;
|
|
20
|
+
exports.AuditLogsCodeRepositoryAccessedV1ToJSONTyped = AuditLogsCodeRepositoryAccessedV1ToJSONTyped;
|
|
21
|
+
const runtime_js_1 = require("../runtime.js");
|
|
22
|
+
const AuditLogActorV2_js_1 = require("./AuditLogActorV2.js");
|
|
23
|
+
const AuditLogEntryContextV2_js_1 = require("./AuditLogEntryContextV2.js");
|
|
24
|
+
const AuditLogCodeRepositoryAccessedMetadataV2_js_1 = require("./AuditLogCodeRepositoryAccessedMetadataV2.js");
|
|
25
|
+
const AuditLogTargetV2_js_1 = require("./AuditLogTargetV2.js");
|
|
26
|
+
/**
|
|
27
|
+
* Check if a given object implements the AuditLogsCodeRepositoryAccessedV1 interface.
|
|
28
|
+
*/
|
|
29
|
+
function instanceOfAuditLogsCodeRepositoryAccessedV1(value) {
|
|
30
|
+
if (!('action' in value) || value['action'] === undefined)
|
|
31
|
+
return false;
|
|
32
|
+
if (!('actor' in value) || value['actor'] === undefined)
|
|
33
|
+
return false;
|
|
34
|
+
if (!('context' in value) || value['context'] === undefined)
|
|
35
|
+
return false;
|
|
36
|
+
if (!('metadata' in value) || value['metadata'] === undefined)
|
|
37
|
+
return false;
|
|
38
|
+
if (!('occurred_at' in value) || value['occurred_at'] === undefined)
|
|
39
|
+
return false;
|
|
40
|
+
if (!('targets' in value) || value['targets'] === undefined)
|
|
41
|
+
return false;
|
|
42
|
+
if (!('version' in value) || value['version'] === undefined)
|
|
43
|
+
return false;
|
|
44
|
+
return true;
|
|
45
|
+
}
|
|
46
|
+
function AuditLogsCodeRepositoryAccessedV1FromJSON(json) {
|
|
47
|
+
return AuditLogsCodeRepositoryAccessedV1FromJSONTyped(json, false);
|
|
48
|
+
}
|
|
49
|
+
function AuditLogsCodeRepositoryAccessedV1FromJSONTyped(json, ignoreDiscriminator) {
|
|
50
|
+
if (json == null) {
|
|
51
|
+
return json;
|
|
52
|
+
}
|
|
53
|
+
return {
|
|
54
|
+
'action': json['action'],
|
|
55
|
+
'actor': (0, AuditLogActorV2_js_1.AuditLogActorV2FromJSON)(json['actor']),
|
|
56
|
+
'context': (0, AuditLogEntryContextV2_js_1.AuditLogEntryContextV2FromJSON)(json['context']),
|
|
57
|
+
'metadata': (0, AuditLogCodeRepositoryAccessedMetadataV2_js_1.AuditLogCodeRepositoryAccessedMetadataV2FromJSON)(json['metadata']),
|
|
58
|
+
'occurred_at': (json['occurred_at'] == null ? json['occurred_at'] : (0, runtime_js_1.parseDateTime)(json['occurred_at'])),
|
|
59
|
+
'targets': (json['targets'].map(AuditLogTargetV2_js_1.AuditLogTargetV2FromJSON)),
|
|
60
|
+
'version': json['version'],
|
|
61
|
+
};
|
|
62
|
+
}
|
|
63
|
+
function AuditLogsCodeRepositoryAccessedV1ToJSON(json) {
|
|
64
|
+
return AuditLogsCodeRepositoryAccessedV1ToJSONTyped(json, false);
|
|
65
|
+
}
|
|
66
|
+
function AuditLogsCodeRepositoryAccessedV1ToJSONTyped(value, ignoreDiscriminator = false) {
|
|
67
|
+
if (value == null) {
|
|
68
|
+
return value;
|
|
69
|
+
}
|
|
70
|
+
return {
|
|
71
|
+
'action': value['action'],
|
|
72
|
+
'actor': (0, AuditLogActorV2_js_1.AuditLogActorV2ToJSON)(value['actor']),
|
|
73
|
+
'context': (0, AuditLogEntryContextV2_js_1.AuditLogEntryContextV2ToJSON)(value['context']),
|
|
74
|
+
'metadata': (0, AuditLogCodeRepositoryAccessedMetadataV2_js_1.AuditLogCodeRepositoryAccessedMetadataV2ToJSON)(value['metadata']),
|
|
75
|
+
'occurred_at': value['occurred_at'] == null ? value['occurred_at'] : (0, runtime_js_1.serializeDateTime)(value['occurred_at']),
|
|
76
|
+
'targets': (value['targets'].map(AuditLogTargetV2_js_1.AuditLogTargetV2ToJSON)),
|
|
77
|
+
'version': value['version'],
|
|
78
|
+
};
|
|
79
|
+
}
|
|
@@ -203,6 +203,7 @@ export * from './AuditLogAnnouncementPostTemplateOwningTeamsMetadataV2.js';
|
|
|
203
203
|
export * from './AuditLogAnnouncementRuleMetadataV2.js';
|
|
204
204
|
export * from './AuditLogCatalogAttributeUpdatedMetadataV2.js';
|
|
205
205
|
export * from './AuditLogCatalogAttributeUpdatedMetadataV2V2.js';
|
|
206
|
+
export * from './AuditLogCodeRepositoryAccessedMetadataV2.js';
|
|
206
207
|
export * from './AuditLogEmailOtpLoginSettingUpdatedMetadataV2.js';
|
|
207
208
|
export * from './AuditLogEntryContextV2.js';
|
|
208
209
|
export * from './AuditLogExtensionConnectorCalledMetadataV2.js';
|
|
@@ -319,6 +320,7 @@ export * from './AuditLogsCatalogTypeDeletedV1.js';
|
|
|
319
320
|
export * from './AuditLogsCatalogTypeDeletedV2.js';
|
|
320
321
|
export * from './AuditLogsCatalogTypeUpdatedV1.js';
|
|
321
322
|
export * from './AuditLogsCatalogTypeUpdatedV2.js';
|
|
323
|
+
export * from './AuditLogsCodeRepositoryAccessedV1.js';
|
|
322
324
|
export * from './AuditLogsConnectorConfigCreatedV1.js';
|
|
323
325
|
export * from './AuditLogsConnectorConfigCreatedV2.js';
|
|
324
326
|
export * from './AuditLogsConnectorConfigTokenGeneratedV1.js';
|
package/dist/cjs/models/index.js
CHANGED
|
@@ -221,6 +221,7 @@ __exportStar(require("./AuditLogAnnouncementPostTemplateOwningTeamsMetadataV2.js
|
|
|
221
221
|
__exportStar(require("./AuditLogAnnouncementRuleMetadataV2.js"), exports);
|
|
222
222
|
__exportStar(require("./AuditLogCatalogAttributeUpdatedMetadataV2.js"), exports);
|
|
223
223
|
__exportStar(require("./AuditLogCatalogAttributeUpdatedMetadataV2V2.js"), exports);
|
|
224
|
+
__exportStar(require("./AuditLogCodeRepositoryAccessedMetadataV2.js"), exports);
|
|
224
225
|
__exportStar(require("./AuditLogEmailOtpLoginSettingUpdatedMetadataV2.js"), exports);
|
|
225
226
|
__exportStar(require("./AuditLogEntryContextV2.js"), exports);
|
|
226
227
|
__exportStar(require("./AuditLogExtensionConnectorCalledMetadataV2.js"), exports);
|
|
@@ -337,6 +338,7 @@ __exportStar(require("./AuditLogsCatalogTypeDeletedV1.js"), exports);
|
|
|
337
338
|
__exportStar(require("./AuditLogsCatalogTypeDeletedV2.js"), exports);
|
|
338
339
|
__exportStar(require("./AuditLogsCatalogTypeUpdatedV1.js"), exports);
|
|
339
340
|
__exportStar(require("./AuditLogsCatalogTypeUpdatedV2.js"), exports);
|
|
341
|
+
__exportStar(require("./AuditLogsCodeRepositoryAccessedV1.js"), exports);
|
|
340
342
|
__exportStar(require("./AuditLogsConnectorConfigCreatedV1.js"), exports);
|
|
341
343
|
__exportStar(require("./AuditLogsConnectorConfigCreatedV2.js"), exports);
|
|
342
344
|
__exportStar(require("./AuditLogsConnectorConfigTokenGeneratedV1.js"), exports);
|
package/dist/cjs/version.d.ts
CHANGED
|
@@ -1 +1 @@
|
|
|
1
|
-
export declare const VERSION = "2.
|
|
1
|
+
export declare const VERSION = "2.35.0";
|
package/dist/cjs/version.js
CHANGED
|
@@ -270,12 +270,12 @@ export declare class EscalationsV2Api extends runtime.BaseAPI {
|
|
|
270
270
|
*/
|
|
271
271
|
escalationsV2ReassignEscalationRequestOpts(requestParameters: EscalationsV2ReassignEscalationRequest): Promise<runtime.RequestOpts>;
|
|
272
272
|
/**
|
|
273
|
-
* Reassign an escalation to a different escalation path or set of users. Use this when a page reached the wrong people. Reassigning creates a new escalation aimed at the targets you give, linked back to the original, and carries over the original\'s title, description, priority, incident and alert so the page stays attached to the same alert and acknowledgements keep grouping under it. You must provide either an escalation_path_id OR user_ids, but not both. Both name incident.io escalation paths and users, so an escalation cannot be reassigned to an external escalator such as PagerDuty or Opsgenie. By default the original escalation is resolved, so the first targets stop being paged. Pass resolve_original=false to leave it running alongside the new one. Resolving the original additionally needs the \"escalations.respond\" permission, since it stops a page someone else may be responding to. An escalation can only be reassigned once: calling this again for the same escalation is rejected. Retrying a request whose response you never saw is safe in the sense that matters — a reassignment that already happened is never repeated, so nobody is paged twice — but the retry is rejected rather than returning the escalation the first call created, so keep the ID from the original response. To use this API, you will need an API key with the \"Create and manage escalations\" permission. The reassignment is attributed to the key; to attribute it to one of your users instead, set the X-Incident-User header, which needs the \"api_keys.act_on_behalf_of_users\" scope. If your API key\'s permissions are scoped to teams, the escalation you\'re reassigning must be owned by one of those teams, and you can only reassign via an escalation path one of them owns. Reassigning directly to user_ids needs the permission at the account level, because an escalation aimed at a person has no owning team.
|
|
273
|
+
* Reassign an escalation to a different escalation path or set of users. Use this when a page reached the wrong people. Reassigning creates a new escalation aimed at the targets you give, linked back to the original, and carries over the original\'s title, description, priority, incident and alert so the page stays attached to the same alert and acknowledgements keep grouping under it. You must provide either an escalation_path_id OR user_ids, but not both. Both name incident.io escalation paths and users, so an escalation cannot be reassigned to an external escalator such as PagerDuty or Opsgenie. By default the original escalation is resolved, so the first targets stop being paged. Pass resolve_original=false to leave it running alongside the new one. Resolving the original additionally needs the \"escalations.respond\" permission, since it stops a page someone else may be responding to. An escalation can only be reassigned once: calling this again for the same escalation is rejected. Retrying a request whose response you never saw is safe in the sense that matters — a reassignment that already happened is never repeated, so nobody is paged twice — but the retry is rejected rather than returning the escalation the first call created, so keep the ID from the original response. To use this API, you will need an API key with the \"Create and manage escalations\" permission. The reassignment is attributed to the key; to attribute it to one of your users instead, set the X-Incident-User header, which needs the \"api_keys.act_on_behalf_of_users\" scope and no team permissions on the key. If your API key\'s permissions are scoped to teams, the escalation you\'re reassigning must be owned by one of those teams, and you can only reassign via an escalation path one of them owns. Reassigning directly to user_ids needs the permission at the account level, because an escalation aimed at a person has no owning team.
|
|
274
274
|
* ReassignEscalation Escalations V2
|
|
275
275
|
*/
|
|
276
276
|
escalationsV2ReassignEscalationRaw(requestParameters: EscalationsV2ReassignEscalationRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<EscalationsReassignEscalationResultV2>>;
|
|
277
277
|
/**
|
|
278
|
-
* Reassign an escalation to a different escalation path or set of users. Use this when a page reached the wrong people. Reassigning creates a new escalation aimed at the targets you give, linked back to the original, and carries over the original\'s title, description, priority, incident and alert so the page stays attached to the same alert and acknowledgements keep grouping under it. You must provide either an escalation_path_id OR user_ids, but not both. Both name incident.io escalation paths and users, so an escalation cannot be reassigned to an external escalator such as PagerDuty or Opsgenie. By default the original escalation is resolved, so the first targets stop being paged. Pass resolve_original=false to leave it running alongside the new one. Resolving the original additionally needs the \"escalations.respond\" permission, since it stops a page someone else may be responding to. An escalation can only be reassigned once: calling this again for the same escalation is rejected. Retrying a request whose response you never saw is safe in the sense that matters — a reassignment that already happened is never repeated, so nobody is paged twice — but the retry is rejected rather than returning the escalation the first call created, so keep the ID from the original response. To use this API, you will need an API key with the \"Create and manage escalations\" permission. The reassignment is attributed to the key; to attribute it to one of your users instead, set the X-Incident-User header, which needs the \"api_keys.act_on_behalf_of_users\" scope. If your API key\'s permissions are scoped to teams, the escalation you\'re reassigning must be owned by one of those teams, and you can only reassign via an escalation path one of them owns. Reassigning directly to user_ids needs the permission at the account level, because an escalation aimed at a person has no owning team.
|
|
278
|
+
* Reassign an escalation to a different escalation path or set of users. Use this when a page reached the wrong people. Reassigning creates a new escalation aimed at the targets you give, linked back to the original, and carries over the original\'s title, description, priority, incident and alert so the page stays attached to the same alert and acknowledgements keep grouping under it. You must provide either an escalation_path_id OR user_ids, but not both. Both name incident.io escalation paths and users, so an escalation cannot be reassigned to an external escalator such as PagerDuty or Opsgenie. By default the original escalation is resolved, so the first targets stop being paged. Pass resolve_original=false to leave it running alongside the new one. Resolving the original additionally needs the \"escalations.respond\" permission, since it stops a page someone else may be responding to. An escalation can only be reassigned once: calling this again for the same escalation is rejected. Retrying a request whose response you never saw is safe in the sense that matters — a reassignment that already happened is never repeated, so nobody is paged twice — but the retry is rejected rather than returning the escalation the first call created, so keep the ID from the original response. To use this API, you will need an API key with the \"Create and manage escalations\" permission. The reassignment is attributed to the key; to attribute it to one of your users instead, set the X-Incident-User header, which needs the \"api_keys.act_on_behalf_of_users\" scope and no team permissions on the key. If your API key\'s permissions are scoped to teams, the escalation you\'re reassigning must be owned by one of those teams, and you can only reassign via an escalation path one of them owns. Reassigning directly to user_ids needs the permission at the account level, because an escalation aimed at a person has no owning team.
|
|
279
279
|
* ReassignEscalation Escalations V2
|
|
280
280
|
*/
|
|
281
281
|
escalationsV2ReassignEscalation(requestParameters: EscalationsV2ReassignEscalationRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<EscalationsReassignEscalationResultV2>;
|
|
@@ -386,7 +386,7 @@ export class EscalationsV2Api extends runtime.BaseAPI {
|
|
|
386
386
|
};
|
|
387
387
|
}
|
|
388
388
|
/**
|
|
389
|
-
* Reassign an escalation to a different escalation path or set of users. Use this when a page reached the wrong people. Reassigning creates a new escalation aimed at the targets you give, linked back to the original, and carries over the original\'s title, description, priority, incident and alert so the page stays attached to the same alert and acknowledgements keep grouping under it. You must provide either an escalation_path_id OR user_ids, but not both. Both name incident.io escalation paths and users, so an escalation cannot be reassigned to an external escalator such as PagerDuty or Opsgenie. By default the original escalation is resolved, so the first targets stop being paged. Pass resolve_original=false to leave it running alongside the new one. Resolving the original additionally needs the \"escalations.respond\" permission, since it stops a page someone else may be responding to. An escalation can only be reassigned once: calling this again for the same escalation is rejected. Retrying a request whose response you never saw is safe in the sense that matters — a reassignment that already happened is never repeated, so nobody is paged twice — but the retry is rejected rather than returning the escalation the first call created, so keep the ID from the original response. To use this API, you will need an API key with the \"Create and manage escalations\" permission. The reassignment is attributed to the key; to attribute it to one of your users instead, set the X-Incident-User header, which needs the \"api_keys.act_on_behalf_of_users\" scope. If your API key\'s permissions are scoped to teams, the escalation you\'re reassigning must be owned by one of those teams, and you can only reassign via an escalation path one of them owns. Reassigning directly to user_ids needs the permission at the account level, because an escalation aimed at a person has no owning team.
|
|
389
|
+
* Reassign an escalation to a different escalation path or set of users. Use this when a page reached the wrong people. Reassigning creates a new escalation aimed at the targets you give, linked back to the original, and carries over the original\'s title, description, priority, incident and alert so the page stays attached to the same alert and acknowledgements keep grouping under it. You must provide either an escalation_path_id OR user_ids, but not both. Both name incident.io escalation paths and users, so an escalation cannot be reassigned to an external escalator such as PagerDuty or Opsgenie. By default the original escalation is resolved, so the first targets stop being paged. Pass resolve_original=false to leave it running alongside the new one. Resolving the original additionally needs the \"escalations.respond\" permission, since it stops a page someone else may be responding to. An escalation can only be reassigned once: calling this again for the same escalation is rejected. Retrying a request whose response you never saw is safe in the sense that matters — a reassignment that already happened is never repeated, so nobody is paged twice — but the retry is rejected rather than returning the escalation the first call created, so keep the ID from the original response. To use this API, you will need an API key with the \"Create and manage escalations\" permission. The reassignment is attributed to the key; to attribute it to one of your users instead, set the X-Incident-User header, which needs the \"api_keys.act_on_behalf_of_users\" scope and no team permissions on the key. If your API key\'s permissions are scoped to teams, the escalation you\'re reassigning must be owned by one of those teams, and you can only reassign via an escalation path one of them owns. Reassigning directly to user_ids needs the permission at the account level, because an escalation aimed at a person has no owning team.
|
|
390
390
|
* ReassignEscalation Escalations V2
|
|
391
391
|
*/
|
|
392
392
|
async escalationsV2ReassignEscalationRaw(requestParameters, initOverrides) {
|
|
@@ -395,7 +395,7 @@ export class EscalationsV2Api extends runtime.BaseAPI {
|
|
|
395
395
|
return new runtime.JSONApiResponse(response, (jsonValue) => EscalationsReassignEscalationResultV2FromJSON(jsonValue));
|
|
396
396
|
}
|
|
397
397
|
/**
|
|
398
|
-
* Reassign an escalation to a different escalation path or set of users. Use this when a page reached the wrong people. Reassigning creates a new escalation aimed at the targets you give, linked back to the original, and carries over the original\'s title, description, priority, incident and alert so the page stays attached to the same alert and acknowledgements keep grouping under it. You must provide either an escalation_path_id OR user_ids, but not both. Both name incident.io escalation paths and users, so an escalation cannot be reassigned to an external escalator such as PagerDuty or Opsgenie. By default the original escalation is resolved, so the first targets stop being paged. Pass resolve_original=false to leave it running alongside the new one. Resolving the original additionally needs the \"escalations.respond\" permission, since it stops a page someone else may be responding to. An escalation can only be reassigned once: calling this again for the same escalation is rejected. Retrying a request whose response you never saw is safe in the sense that matters — a reassignment that already happened is never repeated, so nobody is paged twice — but the retry is rejected rather than returning the escalation the first call created, so keep the ID from the original response. To use this API, you will need an API key with the \"Create and manage escalations\" permission. The reassignment is attributed to the key; to attribute it to one of your users instead, set the X-Incident-User header, which needs the \"api_keys.act_on_behalf_of_users\" scope. If your API key\'s permissions are scoped to teams, the escalation you\'re reassigning must be owned by one of those teams, and you can only reassign via an escalation path one of them owns. Reassigning directly to user_ids needs the permission at the account level, because an escalation aimed at a person has no owning team.
|
|
398
|
+
* Reassign an escalation to a different escalation path or set of users. Use this when a page reached the wrong people. Reassigning creates a new escalation aimed at the targets you give, linked back to the original, and carries over the original\'s title, description, priority, incident and alert so the page stays attached to the same alert and acknowledgements keep grouping under it. You must provide either an escalation_path_id OR user_ids, but not both. Both name incident.io escalation paths and users, so an escalation cannot be reassigned to an external escalator such as PagerDuty or Opsgenie. By default the original escalation is resolved, so the first targets stop being paged. Pass resolve_original=false to leave it running alongside the new one. Resolving the original additionally needs the \"escalations.respond\" permission, since it stops a page someone else may be responding to. An escalation can only be reassigned once: calling this again for the same escalation is rejected. Retrying a request whose response you never saw is safe in the sense that matters — a reassignment that already happened is never repeated, so nobody is paged twice — but the retry is rejected rather than returning the escalation the first call created, so keep the ID from the original response. To use this API, you will need an API key with the \"Create and manage escalations\" permission. The reassignment is attributed to the key; to attribute it to one of your users instead, set the X-Incident-User header, which needs the \"api_keys.act_on_behalf_of_users\" scope and no team permissions on the key. If your API key\'s permissions are scoped to teams, the escalation you\'re reassigning must be owned by one of those teams, and you can only reassign via an escalation path one of them owns. Reassigning directly to user_ids needs the permission at the account level, because an escalation aimed at a person has no owning team.
|
|
399
399
|
* ReassignEscalation Escalations V2
|
|
400
400
|
*/
|
|
401
401
|
async escalationsV2ReassignEscalation(requestParameters, initOverrides) {
|
|
@@ -0,0 +1,50 @@
|
|
|
1
|
+
/**
|
|
2
|
+
* incident.io
|
|
3
|
+
* No description provided (generated by Openapi Generator https://github.com/openapitools/openapi-generator)
|
|
4
|
+
*
|
|
5
|
+
* The version of the OpenAPI document: 1.0.0
|
|
6
|
+
*
|
|
7
|
+
*
|
|
8
|
+
* NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
|
|
9
|
+
* https://openapi-generator.tech
|
|
10
|
+
* Do not edit the class manually.
|
|
11
|
+
*/
|
|
12
|
+
/**
|
|
13
|
+
*
|
|
14
|
+
* @export
|
|
15
|
+
* @interface AuditLogCodeRepositoryAccessedMetadataV2
|
|
16
|
+
*/
|
|
17
|
+
export interface AuditLogCodeRepositoryAccessedMetadataV2 {
|
|
18
|
+
/**
|
|
19
|
+
* ID of the alert the run was for, when known
|
|
20
|
+
*/
|
|
21
|
+
alert_id?: string;
|
|
22
|
+
/**
|
|
23
|
+
* ID of the incident the run was for, when known
|
|
24
|
+
*/
|
|
25
|
+
incident_id?: string;
|
|
26
|
+
/**
|
|
27
|
+
* ID of the investigation, when an investigation read the repository
|
|
28
|
+
*/
|
|
29
|
+
investigation_id?: string;
|
|
30
|
+
/**
|
|
31
|
+
* The commit the run checked out
|
|
32
|
+
*/
|
|
33
|
+
revision_sha: string;
|
|
34
|
+
/**
|
|
35
|
+
* The kind of agent run that read the repository (investigation, chat, code_agent)
|
|
36
|
+
*/
|
|
37
|
+
run_type: string;
|
|
38
|
+
/**
|
|
39
|
+
* ID of the user who asked, when a chat read the repository
|
|
40
|
+
*/
|
|
41
|
+
user_id?: string;
|
|
42
|
+
}
|
|
43
|
+
/**
|
|
44
|
+
* Check if a given object implements the AuditLogCodeRepositoryAccessedMetadataV2 interface.
|
|
45
|
+
*/
|
|
46
|
+
export declare function instanceOfAuditLogCodeRepositoryAccessedMetadataV2(value: object): value is AuditLogCodeRepositoryAccessedMetadataV2;
|
|
47
|
+
export declare function AuditLogCodeRepositoryAccessedMetadataV2FromJSON(json: any): AuditLogCodeRepositoryAccessedMetadataV2;
|
|
48
|
+
export declare function AuditLogCodeRepositoryAccessedMetadataV2FromJSONTyped(json: any, ignoreDiscriminator: boolean): AuditLogCodeRepositoryAccessedMetadataV2;
|
|
49
|
+
export declare function AuditLogCodeRepositoryAccessedMetadataV2ToJSON(json: any): AuditLogCodeRepositoryAccessedMetadataV2;
|
|
50
|
+
export declare function AuditLogCodeRepositoryAccessedMetadataV2ToJSONTyped(value?: AuditLogCodeRepositoryAccessedMetadataV2 | null, ignoreDiscriminator?: boolean): any;
|
|
@@ -0,0 +1,55 @@
|
|
|
1
|
+
/* tslint:disable */
|
|
2
|
+
/* eslint-disable */
|
|
3
|
+
/**
|
|
4
|
+
* incident.io
|
|
5
|
+
* No description provided (generated by Openapi Generator https://github.com/openapitools/openapi-generator)
|
|
6
|
+
*
|
|
7
|
+
* The version of the OpenAPI document: 1.0.0
|
|
8
|
+
*
|
|
9
|
+
*
|
|
10
|
+
* NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
|
|
11
|
+
* https://openapi-generator.tech
|
|
12
|
+
* Do not edit the class manually.
|
|
13
|
+
*/
|
|
14
|
+
/**
|
|
15
|
+
* Check if a given object implements the AuditLogCodeRepositoryAccessedMetadataV2 interface.
|
|
16
|
+
*/
|
|
17
|
+
export function instanceOfAuditLogCodeRepositoryAccessedMetadataV2(value) {
|
|
18
|
+
if (!('revision_sha' in value) || value['revision_sha'] === undefined)
|
|
19
|
+
return false;
|
|
20
|
+
if (!('run_type' in value) || value['run_type'] === undefined)
|
|
21
|
+
return false;
|
|
22
|
+
return true;
|
|
23
|
+
}
|
|
24
|
+
export function AuditLogCodeRepositoryAccessedMetadataV2FromJSON(json) {
|
|
25
|
+
return AuditLogCodeRepositoryAccessedMetadataV2FromJSONTyped(json, false);
|
|
26
|
+
}
|
|
27
|
+
export function AuditLogCodeRepositoryAccessedMetadataV2FromJSONTyped(json, ignoreDiscriminator) {
|
|
28
|
+
if (json == null) {
|
|
29
|
+
return json;
|
|
30
|
+
}
|
|
31
|
+
return {
|
|
32
|
+
'alert_id': json['alert_id'] == null ? undefined : json['alert_id'],
|
|
33
|
+
'incident_id': json['incident_id'] == null ? undefined : json['incident_id'],
|
|
34
|
+
'investigation_id': json['investigation_id'] == null ? undefined : json['investigation_id'],
|
|
35
|
+
'revision_sha': json['revision_sha'],
|
|
36
|
+
'run_type': json['run_type'],
|
|
37
|
+
'user_id': json['user_id'] == null ? undefined : json['user_id'],
|
|
38
|
+
};
|
|
39
|
+
}
|
|
40
|
+
export function AuditLogCodeRepositoryAccessedMetadataV2ToJSON(json) {
|
|
41
|
+
return AuditLogCodeRepositoryAccessedMetadataV2ToJSONTyped(json, false);
|
|
42
|
+
}
|
|
43
|
+
export function AuditLogCodeRepositoryAccessedMetadataV2ToJSONTyped(value, ignoreDiscriminator = false) {
|
|
44
|
+
if (value == null) {
|
|
45
|
+
return value;
|
|
46
|
+
}
|
|
47
|
+
return {
|
|
48
|
+
'alert_id': value['alert_id'],
|
|
49
|
+
'incident_id': value['incident_id'],
|
|
50
|
+
'investigation_id': value['investigation_id'],
|
|
51
|
+
'revision_sha': value['revision_sha'],
|
|
52
|
+
'run_type': value['run_type'],
|
|
53
|
+
'user_id': value['user_id'],
|
|
54
|
+
};
|
|
55
|
+
}
|
|
@@ -0,0 +1,58 @@
|
|
|
1
|
+
/**
|
|
2
|
+
* incident.io
|
|
3
|
+
* No description provided (generated by Openapi Generator https://github.com/openapitools/openapi-generator)
|
|
4
|
+
*
|
|
5
|
+
* The version of the OpenAPI document: 1.0.0
|
|
6
|
+
*
|
|
7
|
+
*
|
|
8
|
+
* NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
|
|
9
|
+
* https://openapi-generator.tech
|
|
10
|
+
* Do not edit the class manually.
|
|
11
|
+
*/
|
|
12
|
+
import type { AuditLogActorV2 } from './AuditLogActorV2.js';
|
|
13
|
+
import type { AuditLogEntryContextV2 } from './AuditLogEntryContextV2.js';
|
|
14
|
+
import type { AuditLogCodeRepositoryAccessedMetadataV2 } from './AuditLogCodeRepositoryAccessedMetadataV2.js';
|
|
15
|
+
import type { AuditLogTargetV2 } from './AuditLogTargetV2.js';
|
|
16
|
+
/**
|
|
17
|
+
*
|
|
18
|
+
* @export
|
|
19
|
+
* @interface AuditLogsCodeRepositoryAccessedV1
|
|
20
|
+
*/
|
|
21
|
+
export interface AuditLogsCodeRepositoryAccessedV1 {
|
|
22
|
+
/**
|
|
23
|
+
* The type of log entry that this is
|
|
24
|
+
*/
|
|
25
|
+
action: string;
|
|
26
|
+
/**
|
|
27
|
+
*
|
|
28
|
+
*/
|
|
29
|
+
actor: AuditLogActorV2;
|
|
30
|
+
/**
|
|
31
|
+
*
|
|
32
|
+
*/
|
|
33
|
+
context: AuditLogEntryContextV2;
|
|
34
|
+
/**
|
|
35
|
+
*
|
|
36
|
+
*/
|
|
37
|
+
metadata: AuditLogCodeRepositoryAccessedMetadataV2;
|
|
38
|
+
/**
|
|
39
|
+
* When the entry occurred
|
|
40
|
+
*/
|
|
41
|
+
occurred_at: Date;
|
|
42
|
+
/**
|
|
43
|
+
* The custom field that was created
|
|
44
|
+
*/
|
|
45
|
+
targets: Array<AuditLogTargetV2>;
|
|
46
|
+
/**
|
|
47
|
+
* Which version the event is
|
|
48
|
+
*/
|
|
49
|
+
version: number;
|
|
50
|
+
}
|
|
51
|
+
/**
|
|
52
|
+
* Check if a given object implements the AuditLogsCodeRepositoryAccessedV1 interface.
|
|
53
|
+
*/
|
|
54
|
+
export declare function instanceOfAuditLogsCodeRepositoryAccessedV1(value: object): value is AuditLogsCodeRepositoryAccessedV1;
|
|
55
|
+
export declare function AuditLogsCodeRepositoryAccessedV1FromJSON(json: any): AuditLogsCodeRepositoryAccessedV1;
|
|
56
|
+
export declare function AuditLogsCodeRepositoryAccessedV1FromJSONTyped(json: any, ignoreDiscriminator: boolean): AuditLogsCodeRepositoryAccessedV1;
|
|
57
|
+
export declare function AuditLogsCodeRepositoryAccessedV1ToJSON(json: any): AuditLogsCodeRepositoryAccessedV1;
|
|
58
|
+
export declare function AuditLogsCodeRepositoryAccessedV1ToJSONTyped(value?: AuditLogsCodeRepositoryAccessedV1 | null, ignoreDiscriminator?: boolean): any;
|
|
@@ -0,0 +1,72 @@
|
|
|
1
|
+
/* tslint:disable */
|
|
2
|
+
/* eslint-disable */
|
|
3
|
+
/**
|
|
4
|
+
* incident.io
|
|
5
|
+
* No description provided (generated by Openapi Generator https://github.com/openapitools/openapi-generator)
|
|
6
|
+
*
|
|
7
|
+
* The version of the OpenAPI document: 1.0.0
|
|
8
|
+
*
|
|
9
|
+
*
|
|
10
|
+
* NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
|
|
11
|
+
* https://openapi-generator.tech
|
|
12
|
+
* Do not edit the class manually.
|
|
13
|
+
*/
|
|
14
|
+
import { parseDateTime, serializeDateTime } from '../runtime.js';
|
|
15
|
+
import { AuditLogActorV2FromJSON, AuditLogActorV2ToJSON, } from './AuditLogActorV2.js';
|
|
16
|
+
import { AuditLogEntryContextV2FromJSON, AuditLogEntryContextV2ToJSON, } from './AuditLogEntryContextV2.js';
|
|
17
|
+
import { AuditLogCodeRepositoryAccessedMetadataV2FromJSON, AuditLogCodeRepositoryAccessedMetadataV2ToJSON, } from './AuditLogCodeRepositoryAccessedMetadataV2.js';
|
|
18
|
+
import { AuditLogTargetV2FromJSON, AuditLogTargetV2ToJSON, } from './AuditLogTargetV2.js';
|
|
19
|
+
/**
|
|
20
|
+
* Check if a given object implements the AuditLogsCodeRepositoryAccessedV1 interface.
|
|
21
|
+
*/
|
|
22
|
+
export function instanceOfAuditLogsCodeRepositoryAccessedV1(value) {
|
|
23
|
+
if (!('action' in value) || value['action'] === undefined)
|
|
24
|
+
return false;
|
|
25
|
+
if (!('actor' in value) || value['actor'] === undefined)
|
|
26
|
+
return false;
|
|
27
|
+
if (!('context' in value) || value['context'] === undefined)
|
|
28
|
+
return false;
|
|
29
|
+
if (!('metadata' in value) || value['metadata'] === undefined)
|
|
30
|
+
return false;
|
|
31
|
+
if (!('occurred_at' in value) || value['occurred_at'] === undefined)
|
|
32
|
+
return false;
|
|
33
|
+
if (!('targets' in value) || value['targets'] === undefined)
|
|
34
|
+
return false;
|
|
35
|
+
if (!('version' in value) || value['version'] === undefined)
|
|
36
|
+
return false;
|
|
37
|
+
return true;
|
|
38
|
+
}
|
|
39
|
+
export function AuditLogsCodeRepositoryAccessedV1FromJSON(json) {
|
|
40
|
+
return AuditLogsCodeRepositoryAccessedV1FromJSONTyped(json, false);
|
|
41
|
+
}
|
|
42
|
+
export function AuditLogsCodeRepositoryAccessedV1FromJSONTyped(json, ignoreDiscriminator) {
|
|
43
|
+
if (json == null) {
|
|
44
|
+
return json;
|
|
45
|
+
}
|
|
46
|
+
return {
|
|
47
|
+
'action': json['action'],
|
|
48
|
+
'actor': AuditLogActorV2FromJSON(json['actor']),
|
|
49
|
+
'context': AuditLogEntryContextV2FromJSON(json['context']),
|
|
50
|
+
'metadata': AuditLogCodeRepositoryAccessedMetadataV2FromJSON(json['metadata']),
|
|
51
|
+
'occurred_at': (json['occurred_at'] == null ? json['occurred_at'] : parseDateTime(json['occurred_at'])),
|
|
52
|
+
'targets': (json['targets'].map(AuditLogTargetV2FromJSON)),
|
|
53
|
+
'version': json['version'],
|
|
54
|
+
};
|
|
55
|
+
}
|
|
56
|
+
export function AuditLogsCodeRepositoryAccessedV1ToJSON(json) {
|
|
57
|
+
return AuditLogsCodeRepositoryAccessedV1ToJSONTyped(json, false);
|
|
58
|
+
}
|
|
59
|
+
export function AuditLogsCodeRepositoryAccessedV1ToJSONTyped(value, ignoreDiscriminator = false) {
|
|
60
|
+
if (value == null) {
|
|
61
|
+
return value;
|
|
62
|
+
}
|
|
63
|
+
return {
|
|
64
|
+
'action': value['action'],
|
|
65
|
+
'actor': AuditLogActorV2ToJSON(value['actor']),
|
|
66
|
+
'context': AuditLogEntryContextV2ToJSON(value['context']),
|
|
67
|
+
'metadata': AuditLogCodeRepositoryAccessedMetadataV2ToJSON(value['metadata']),
|
|
68
|
+
'occurred_at': value['occurred_at'] == null ? value['occurred_at'] : serializeDateTime(value['occurred_at']),
|
|
69
|
+
'targets': (value['targets'].map(AuditLogTargetV2ToJSON)),
|
|
70
|
+
'version': value['version'],
|
|
71
|
+
};
|
|
72
|
+
}
|
|
@@ -203,6 +203,7 @@ export * from './AuditLogAnnouncementPostTemplateOwningTeamsMetadataV2.js';
|
|
|
203
203
|
export * from './AuditLogAnnouncementRuleMetadataV2.js';
|
|
204
204
|
export * from './AuditLogCatalogAttributeUpdatedMetadataV2.js';
|
|
205
205
|
export * from './AuditLogCatalogAttributeUpdatedMetadataV2V2.js';
|
|
206
|
+
export * from './AuditLogCodeRepositoryAccessedMetadataV2.js';
|
|
206
207
|
export * from './AuditLogEmailOtpLoginSettingUpdatedMetadataV2.js';
|
|
207
208
|
export * from './AuditLogEntryContextV2.js';
|
|
208
209
|
export * from './AuditLogExtensionConnectorCalledMetadataV2.js';
|
|
@@ -319,6 +320,7 @@ export * from './AuditLogsCatalogTypeDeletedV1.js';
|
|
|
319
320
|
export * from './AuditLogsCatalogTypeDeletedV2.js';
|
|
320
321
|
export * from './AuditLogsCatalogTypeUpdatedV1.js';
|
|
321
322
|
export * from './AuditLogsCatalogTypeUpdatedV2.js';
|
|
323
|
+
export * from './AuditLogsCodeRepositoryAccessedV1.js';
|
|
322
324
|
export * from './AuditLogsConnectorConfigCreatedV1.js';
|
|
323
325
|
export * from './AuditLogsConnectorConfigCreatedV2.js';
|
|
324
326
|
export * from './AuditLogsConnectorConfigTokenGeneratedV1.js';
|
package/dist/esm/models/index.js
CHANGED
|
@@ -205,6 +205,7 @@ export * from './AuditLogAnnouncementPostTemplateOwningTeamsMetadataV2.js';
|
|
|
205
205
|
export * from './AuditLogAnnouncementRuleMetadataV2.js';
|
|
206
206
|
export * from './AuditLogCatalogAttributeUpdatedMetadataV2.js';
|
|
207
207
|
export * from './AuditLogCatalogAttributeUpdatedMetadataV2V2.js';
|
|
208
|
+
export * from './AuditLogCodeRepositoryAccessedMetadataV2.js';
|
|
208
209
|
export * from './AuditLogEmailOtpLoginSettingUpdatedMetadataV2.js';
|
|
209
210
|
export * from './AuditLogEntryContextV2.js';
|
|
210
211
|
export * from './AuditLogExtensionConnectorCalledMetadataV2.js';
|
|
@@ -321,6 +322,7 @@ export * from './AuditLogsCatalogTypeDeletedV1.js';
|
|
|
321
322
|
export * from './AuditLogsCatalogTypeDeletedV2.js';
|
|
322
323
|
export * from './AuditLogsCatalogTypeUpdatedV1.js';
|
|
323
324
|
export * from './AuditLogsCatalogTypeUpdatedV2.js';
|
|
325
|
+
export * from './AuditLogsCodeRepositoryAccessedV1.js';
|
|
324
326
|
export * from './AuditLogsConnectorConfigCreatedV1.js';
|
|
325
327
|
export * from './AuditLogsConnectorConfigCreatedV2.js';
|
|
326
328
|
export * from './AuditLogsConnectorConfigTokenGeneratedV1.js';
|
package/dist/esm/version.d.ts
CHANGED
|
@@ -1 +1 @@
|
|
|
1
|
-
export declare const VERSION = "2.
|
|
1
|
+
export declare const VERSION = "2.35.0";
|
package/dist/esm/version.js
CHANGED
|
@@ -1,2 +1,2 @@
|
|
|
1
1
|
// Written by `make build` from package.json. Do not edit.
|
|
2
|
-
export const VERSION = "2.
|
|
2
|
+
export const VERSION = "2.35.0";
|