@incident-io/sdk 2.34.0 → 2.36.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.
@@ -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) {
@@ -61,12 +61,12 @@ export declare class StatusPageComponentsV2Api extends runtime.BaseAPI {
61
61
  */
62
62
  statusPageComponentsV2CreateRequestOpts(requestParameters: StatusPageComponentsV2CreateRequest): Promise<runtime.RequestOpts>;
63
63
  /**
64
- * Create a status page component. Placement on a page is controlled separately via status page structures.
64
+ * Create a status page component. Placement on a page is controlled separately via status page structures. This endpoint requires an API key with the \"Manage organization settings (e.g. custom fields)\" scope.
65
65
  * Create Status Page Components V2
66
66
  */
67
67
  statusPageComponentsV2CreateRaw(requestParameters: StatusPageComponentsV2CreateRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<StatusPageComponentsCreateResultV2>>;
68
68
  /**
69
- * Create a status page component. Placement on a page is controlled separately via status page structures.
69
+ * Create a status page component. Placement on a page is controlled separately via status page structures. This endpoint requires an API key with the \"Manage organization settings (e.g. custom fields)\" scope.
70
70
  * Create Status Page Components V2
71
71
  */
72
72
  statusPageComponentsV2Create(requestParameters: StatusPageComponentsV2CreateRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<StatusPageComponentsCreateResultV2>;
@@ -75,12 +75,12 @@ export declare class StatusPageComponentsV2Api extends runtime.BaseAPI {
75
75
  */
76
76
  statusPageComponentsV2DestroyRequestOpts(requestParameters: StatusPageComponentsV2DestroyRequest): Promise<runtime.RequestOpts>;
77
77
  /**
78
- * Archive a status page component.
78
+ * Archive a status page component. This endpoint requires an API key with the \"Manage organization settings (e.g. custom fields)\" scope.
79
79
  * Destroy Status Page Components V2
80
80
  */
81
81
  statusPageComponentsV2DestroyRaw(requestParameters: StatusPageComponentsV2DestroyRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<void>>;
82
82
  /**
83
- * Archive a status page component.
83
+ * Archive a status page component. This endpoint requires an API key with the \"Manage organization settings (e.g. custom fields)\" scope.
84
84
  * Destroy Status Page Components V2
85
85
  */
86
86
  statusPageComponentsV2Destroy(requestParameters: StatusPageComponentsV2DestroyRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<void>;
@@ -117,12 +117,12 @@ export declare class StatusPageComponentsV2Api extends runtime.BaseAPI {
117
117
  */
118
118
  statusPageComponentsV2UpdateRequestOpts(requestParameters: StatusPageComponentsV2UpdateRequest): Promise<runtime.RequestOpts>;
119
119
  /**
120
- * Update a status page component\'s name and description.
120
+ * Update a status page component\'s name and description. This endpoint requires an API key with the \"Manage organization settings (e.g. custom fields)\" scope.
121
121
  * Update Status Page Components V2
122
122
  */
123
123
  statusPageComponentsV2UpdateRaw(requestParameters: StatusPageComponentsV2UpdateRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<StatusPageComponentsUpdateResultV2>>;
124
124
  /**
125
- * Update a status page component\'s name and description.
125
+ * Update a status page component\'s name and description. This endpoint requires an API key with the \"Manage organization settings (e.g. custom fields)\" scope.
126
126
  * Update Status Page Components V2
127
127
  */
128
128
  statusPageComponentsV2Update(requestParameters: StatusPageComponentsV2UpdateRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<StatusPageComponentsUpdateResultV2>;
@@ -85,7 +85,7 @@ class StatusPageComponentsV2Api extends runtime.BaseAPI {
85
85
  };
86
86
  }
87
87
  /**
88
- * Create a status page component. Placement on a page is controlled separately via status page structures.
88
+ * Create a status page component. Placement on a page is controlled separately via status page structures. This endpoint requires an API key with the \"Manage organization settings (e.g. custom fields)\" scope.
89
89
  * Create Status Page Components V2
90
90
  */
91
91
  async statusPageComponentsV2CreateRaw(requestParameters, initOverrides) {
@@ -94,7 +94,7 @@ class StatusPageComponentsV2Api extends runtime.BaseAPI {
94
94
  return new runtime.JSONApiResponse(response, (jsonValue) => (0, StatusPageComponentsCreateResultV2_js_1.StatusPageComponentsCreateResultV2FromJSON)(jsonValue));
95
95
  }
96
96
  /**
97
- * Create a status page component. Placement on a page is controlled separately via status page structures.
97
+ * Create a status page component. Placement on a page is controlled separately via status page structures. This endpoint requires an API key with the \"Manage organization settings (e.g. custom fields)\" scope.
98
98
  * Create Status Page Components V2
99
99
  */
100
100
  async statusPageComponentsV2Create(requestParameters, initOverrides) {
@@ -127,7 +127,7 @@ class StatusPageComponentsV2Api extends runtime.BaseAPI {
127
127
  };
128
128
  }
129
129
  /**
130
- * Archive a status page component.
130
+ * Archive a status page component. This endpoint requires an API key with the \"Manage organization settings (e.g. custom fields)\" scope.
131
131
  * Destroy Status Page Components V2
132
132
  */
133
133
  async statusPageComponentsV2DestroyRaw(requestParameters, initOverrides) {
@@ -136,7 +136,7 @@ class StatusPageComponentsV2Api extends runtime.BaseAPI {
136
136
  return new runtime.VoidApiResponse(response);
137
137
  }
138
138
  /**
139
- * Archive a status page component.
139
+ * Archive a status page component. This endpoint requires an API key with the \"Manage organization settings (e.g. custom fields)\" scope.
140
140
  * Destroy Status Page Components V2
141
141
  */
142
142
  async statusPageComponentsV2Destroy(requestParameters, initOverrides) {
@@ -253,7 +253,7 @@ class StatusPageComponentsV2Api extends runtime.BaseAPI {
253
253
  };
254
254
  }
255
255
  /**
256
- * Update a status page component\'s name and description.
256
+ * Update a status page component\'s name and description. This endpoint requires an API key with the \"Manage organization settings (e.g. custom fields)\" scope.
257
257
  * Update Status Page Components V2
258
258
  */
259
259
  async statusPageComponentsV2UpdateRaw(requestParameters, initOverrides) {
@@ -262,7 +262,7 @@ class StatusPageComponentsV2Api extends runtime.BaseAPI {
262
262
  return new runtime.JSONApiResponse(response, (jsonValue) => (0, StatusPageComponentsUpdateResultV2_js_1.StatusPageComponentsUpdateResultV2FromJSON)(jsonValue));
263
263
  }
264
264
  /**
265
- * Update a status page component\'s name and description.
265
+ * Update a status page component\'s name and description. This endpoint requires an API key with the \"Manage organization settings (e.g. custom fields)\" scope.
266
266
  * Update Status Page Components V2
267
267
  */
268
268
  async statusPageComponentsV2Update(requestParameters, initOverrides) {
@@ -0,0 +1,53 @@
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 { AuditLogTargetV2 } from './AuditLogTargetV2.js';
15
+ /**
16
+ *
17
+ * @export
18
+ * @interface AuditLogsConnectorConfigArchivedV1
19
+ */
20
+ export interface AuditLogsConnectorConfigArchivedV1 {
21
+ /**
22
+ * The type of log entry that this is
23
+ */
24
+ action: string;
25
+ /**
26
+ *
27
+ */
28
+ actor: AuditLogActorV2;
29
+ /**
30
+ *
31
+ */
32
+ context: AuditLogEntryContextV2;
33
+ /**
34
+ * When the entry occurred
35
+ */
36
+ occurred_at: Date;
37
+ /**
38
+ * The custom field that was created
39
+ */
40
+ targets: Array<AuditLogTargetV2>;
41
+ /**
42
+ * Which version the event is
43
+ */
44
+ version: number;
45
+ }
46
+ /**
47
+ * Check if a given object implements the AuditLogsConnectorConfigArchivedV1 interface.
48
+ */
49
+ export declare function instanceOfAuditLogsConnectorConfigArchivedV1(value: object): value is AuditLogsConnectorConfigArchivedV1;
50
+ export declare function AuditLogsConnectorConfigArchivedV1FromJSON(json: any): AuditLogsConnectorConfigArchivedV1;
51
+ export declare function AuditLogsConnectorConfigArchivedV1FromJSONTyped(json: any, ignoreDiscriminator: boolean): AuditLogsConnectorConfigArchivedV1;
52
+ export declare function AuditLogsConnectorConfigArchivedV1ToJSON(json: any): AuditLogsConnectorConfigArchivedV1;
53
+ export declare function AuditLogsConnectorConfigArchivedV1ToJSONTyped(value?: AuditLogsConnectorConfigArchivedV1 | null, ignoreDiscriminator?: boolean): any;
@@ -0,0 +1,74 @@
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.instanceOfAuditLogsConnectorConfigArchivedV1 = instanceOfAuditLogsConnectorConfigArchivedV1;
17
+ exports.AuditLogsConnectorConfigArchivedV1FromJSON = AuditLogsConnectorConfigArchivedV1FromJSON;
18
+ exports.AuditLogsConnectorConfigArchivedV1FromJSONTyped = AuditLogsConnectorConfigArchivedV1FromJSONTyped;
19
+ exports.AuditLogsConnectorConfigArchivedV1ToJSON = AuditLogsConnectorConfigArchivedV1ToJSON;
20
+ exports.AuditLogsConnectorConfigArchivedV1ToJSONTyped = AuditLogsConnectorConfigArchivedV1ToJSONTyped;
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 AuditLogTargetV2_js_1 = require("./AuditLogTargetV2.js");
25
+ /**
26
+ * Check if a given object implements the AuditLogsConnectorConfigArchivedV1 interface.
27
+ */
28
+ function instanceOfAuditLogsConnectorConfigArchivedV1(value) {
29
+ if (!('action' in value) || value['action'] === undefined)
30
+ return false;
31
+ if (!('actor' in value) || value['actor'] === undefined)
32
+ return false;
33
+ if (!('context' in value) || value['context'] === undefined)
34
+ return false;
35
+ if (!('occurred_at' in value) || value['occurred_at'] === undefined)
36
+ return false;
37
+ if (!('targets' in value) || value['targets'] === undefined)
38
+ return false;
39
+ if (!('version' in value) || value['version'] === undefined)
40
+ return false;
41
+ return true;
42
+ }
43
+ function AuditLogsConnectorConfigArchivedV1FromJSON(json) {
44
+ return AuditLogsConnectorConfigArchivedV1FromJSONTyped(json, false);
45
+ }
46
+ function AuditLogsConnectorConfigArchivedV1FromJSONTyped(json, ignoreDiscriminator) {
47
+ if (json == null) {
48
+ return json;
49
+ }
50
+ return {
51
+ 'action': json['action'],
52
+ 'actor': (0, AuditLogActorV2_js_1.AuditLogActorV2FromJSON)(json['actor']),
53
+ 'context': (0, AuditLogEntryContextV2_js_1.AuditLogEntryContextV2FromJSON)(json['context']),
54
+ 'occurred_at': (json['occurred_at'] == null ? json['occurred_at'] : (0, runtime_js_1.parseDateTime)(json['occurred_at'])),
55
+ 'targets': (json['targets'].map(AuditLogTargetV2_js_1.AuditLogTargetV2FromJSON)),
56
+ 'version': json['version'],
57
+ };
58
+ }
59
+ function AuditLogsConnectorConfigArchivedV1ToJSON(json) {
60
+ return AuditLogsConnectorConfigArchivedV1ToJSONTyped(json, false);
61
+ }
62
+ function AuditLogsConnectorConfigArchivedV1ToJSONTyped(value, ignoreDiscriminator = false) {
63
+ if (value == null) {
64
+ return value;
65
+ }
66
+ return {
67
+ 'action': value['action'],
68
+ 'actor': (0, AuditLogActorV2_js_1.AuditLogActorV2ToJSON)(value['actor']),
69
+ 'context': (0, AuditLogEntryContextV2_js_1.AuditLogEntryContextV2ToJSON)(value['context']),
70
+ 'occurred_at': value['occurred_at'] == null ? value['occurred_at'] : (0, runtime_js_1.serializeDateTime)(value['occurred_at']),
71
+ 'targets': (value['targets'].map(AuditLogTargetV2_js_1.AuditLogTargetV2ToJSON)),
72
+ 'version': value['version'],
73
+ };
74
+ }
@@ -321,6 +321,7 @@ export * from './AuditLogsCatalogTypeDeletedV2.js';
321
321
  export * from './AuditLogsCatalogTypeUpdatedV1.js';
322
322
  export * from './AuditLogsCatalogTypeUpdatedV2.js';
323
323
  export * from './AuditLogsCodeRepositoryAccessedV1.js';
324
+ export * from './AuditLogsConnectorConfigArchivedV1.js';
324
325
  export * from './AuditLogsConnectorConfigCreatedV1.js';
325
326
  export * from './AuditLogsConnectorConfigCreatedV2.js';
326
327
  export * from './AuditLogsConnectorConfigTokenGeneratedV1.js';
@@ -339,6 +339,7 @@ __exportStar(require("./AuditLogsCatalogTypeDeletedV2.js"), exports);
339
339
  __exportStar(require("./AuditLogsCatalogTypeUpdatedV1.js"), exports);
340
340
  __exportStar(require("./AuditLogsCatalogTypeUpdatedV2.js"), exports);
341
341
  __exportStar(require("./AuditLogsCodeRepositoryAccessedV1.js"), exports);
342
+ __exportStar(require("./AuditLogsConnectorConfigArchivedV1.js"), exports);
342
343
  __exportStar(require("./AuditLogsConnectorConfigCreatedV1.js"), exports);
343
344
  __exportStar(require("./AuditLogsConnectorConfigCreatedV2.js"), exports);
344
345
  __exportStar(require("./AuditLogsConnectorConfigTokenGeneratedV1.js"), exports);
@@ -1 +1 @@
1
- export declare const VERSION = "2.34.0";
1
+ export declare const VERSION = "2.36.0";
@@ -2,4 +2,4 @@
2
2
  Object.defineProperty(exports, "__esModule", { value: true });
3
3
  exports.VERSION = void 0;
4
4
  // Written by `make build` from package.json. Do not edit.
5
- exports.VERSION = "2.34.0";
5
+ exports.VERSION = "2.36.0";
@@ -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) {
@@ -61,12 +61,12 @@ export declare class StatusPageComponentsV2Api extends runtime.BaseAPI {
61
61
  */
62
62
  statusPageComponentsV2CreateRequestOpts(requestParameters: StatusPageComponentsV2CreateRequest): Promise<runtime.RequestOpts>;
63
63
  /**
64
- * Create a status page component. Placement on a page is controlled separately via status page structures.
64
+ * Create a status page component. Placement on a page is controlled separately via status page structures. This endpoint requires an API key with the \"Manage organization settings (e.g. custom fields)\" scope.
65
65
  * Create Status Page Components V2
66
66
  */
67
67
  statusPageComponentsV2CreateRaw(requestParameters: StatusPageComponentsV2CreateRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<StatusPageComponentsCreateResultV2>>;
68
68
  /**
69
- * Create a status page component. Placement on a page is controlled separately via status page structures.
69
+ * Create a status page component. Placement on a page is controlled separately via status page structures. This endpoint requires an API key with the \"Manage organization settings (e.g. custom fields)\" scope.
70
70
  * Create Status Page Components V2
71
71
  */
72
72
  statusPageComponentsV2Create(requestParameters: StatusPageComponentsV2CreateRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<StatusPageComponentsCreateResultV2>;
@@ -75,12 +75,12 @@ export declare class StatusPageComponentsV2Api extends runtime.BaseAPI {
75
75
  */
76
76
  statusPageComponentsV2DestroyRequestOpts(requestParameters: StatusPageComponentsV2DestroyRequest): Promise<runtime.RequestOpts>;
77
77
  /**
78
- * Archive a status page component.
78
+ * Archive a status page component. This endpoint requires an API key with the \"Manage organization settings (e.g. custom fields)\" scope.
79
79
  * Destroy Status Page Components V2
80
80
  */
81
81
  statusPageComponentsV2DestroyRaw(requestParameters: StatusPageComponentsV2DestroyRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<void>>;
82
82
  /**
83
- * Archive a status page component.
83
+ * Archive a status page component. This endpoint requires an API key with the \"Manage organization settings (e.g. custom fields)\" scope.
84
84
  * Destroy Status Page Components V2
85
85
  */
86
86
  statusPageComponentsV2Destroy(requestParameters: StatusPageComponentsV2DestroyRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<void>;
@@ -117,12 +117,12 @@ export declare class StatusPageComponentsV2Api extends runtime.BaseAPI {
117
117
  */
118
118
  statusPageComponentsV2UpdateRequestOpts(requestParameters: StatusPageComponentsV2UpdateRequest): Promise<runtime.RequestOpts>;
119
119
  /**
120
- * Update a status page component\'s name and description.
120
+ * Update a status page component\'s name and description. This endpoint requires an API key with the \"Manage organization settings (e.g. custom fields)\" scope.
121
121
  * Update Status Page Components V2
122
122
  */
123
123
  statusPageComponentsV2UpdateRaw(requestParameters: StatusPageComponentsV2UpdateRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<StatusPageComponentsUpdateResultV2>>;
124
124
  /**
125
- * Update a status page component\'s name and description.
125
+ * Update a status page component\'s name and description. This endpoint requires an API key with the \"Manage organization settings (e.g. custom fields)\" scope.
126
126
  * Update Status Page Components V2
127
127
  */
128
128
  statusPageComponentsV2Update(requestParameters: StatusPageComponentsV2UpdateRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<StatusPageComponentsUpdateResultV2>;
@@ -49,7 +49,7 @@ export class StatusPageComponentsV2Api extends runtime.BaseAPI {
49
49
  };
50
50
  }
51
51
  /**
52
- * Create a status page component. Placement on a page is controlled separately via status page structures.
52
+ * Create a status page component. Placement on a page is controlled separately via status page structures. This endpoint requires an API key with the \"Manage organization settings (e.g. custom fields)\" scope.
53
53
  * Create Status Page Components V2
54
54
  */
55
55
  async statusPageComponentsV2CreateRaw(requestParameters, initOverrides) {
@@ -58,7 +58,7 @@ export class StatusPageComponentsV2Api extends runtime.BaseAPI {
58
58
  return new runtime.JSONApiResponse(response, (jsonValue) => StatusPageComponentsCreateResultV2FromJSON(jsonValue));
59
59
  }
60
60
  /**
61
- * Create a status page component. Placement on a page is controlled separately via status page structures.
61
+ * Create a status page component. Placement on a page is controlled separately via status page structures. This endpoint requires an API key with the \"Manage organization settings (e.g. custom fields)\" scope.
62
62
  * Create Status Page Components V2
63
63
  */
64
64
  async statusPageComponentsV2Create(requestParameters, initOverrides) {
@@ -91,7 +91,7 @@ export class StatusPageComponentsV2Api extends runtime.BaseAPI {
91
91
  };
92
92
  }
93
93
  /**
94
- * Archive a status page component.
94
+ * Archive a status page component. This endpoint requires an API key with the \"Manage organization settings (e.g. custom fields)\" scope.
95
95
  * Destroy Status Page Components V2
96
96
  */
97
97
  async statusPageComponentsV2DestroyRaw(requestParameters, initOverrides) {
@@ -100,7 +100,7 @@ export class StatusPageComponentsV2Api extends runtime.BaseAPI {
100
100
  return new runtime.VoidApiResponse(response);
101
101
  }
102
102
  /**
103
- * Archive a status page component.
103
+ * Archive a status page component. This endpoint requires an API key with the \"Manage organization settings (e.g. custom fields)\" scope.
104
104
  * Destroy Status Page Components V2
105
105
  */
106
106
  async statusPageComponentsV2Destroy(requestParameters, initOverrides) {
@@ -217,7 +217,7 @@ export class StatusPageComponentsV2Api extends runtime.BaseAPI {
217
217
  };
218
218
  }
219
219
  /**
220
- * Update a status page component\'s name and description.
220
+ * Update a status page component\'s name and description. This endpoint requires an API key with the \"Manage organization settings (e.g. custom fields)\" scope.
221
221
  * Update Status Page Components V2
222
222
  */
223
223
  async statusPageComponentsV2UpdateRaw(requestParameters, initOverrides) {
@@ -226,7 +226,7 @@ export class StatusPageComponentsV2Api extends runtime.BaseAPI {
226
226
  return new runtime.JSONApiResponse(response, (jsonValue) => StatusPageComponentsUpdateResultV2FromJSON(jsonValue));
227
227
  }
228
228
  /**
229
- * Update a status page component\'s name and description.
229
+ * Update a status page component\'s name and description. This endpoint requires an API key with the \"Manage organization settings (e.g. custom fields)\" scope.
230
230
  * Update Status Page Components V2
231
231
  */
232
232
  async statusPageComponentsV2Update(requestParameters, initOverrides) {
@@ -0,0 +1,53 @@
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 { AuditLogTargetV2 } from './AuditLogTargetV2.js';
15
+ /**
16
+ *
17
+ * @export
18
+ * @interface AuditLogsConnectorConfigArchivedV1
19
+ */
20
+ export interface AuditLogsConnectorConfigArchivedV1 {
21
+ /**
22
+ * The type of log entry that this is
23
+ */
24
+ action: string;
25
+ /**
26
+ *
27
+ */
28
+ actor: AuditLogActorV2;
29
+ /**
30
+ *
31
+ */
32
+ context: AuditLogEntryContextV2;
33
+ /**
34
+ * When the entry occurred
35
+ */
36
+ occurred_at: Date;
37
+ /**
38
+ * The custom field that was created
39
+ */
40
+ targets: Array<AuditLogTargetV2>;
41
+ /**
42
+ * Which version the event is
43
+ */
44
+ version: number;
45
+ }
46
+ /**
47
+ * Check if a given object implements the AuditLogsConnectorConfigArchivedV1 interface.
48
+ */
49
+ export declare function instanceOfAuditLogsConnectorConfigArchivedV1(value: object): value is AuditLogsConnectorConfigArchivedV1;
50
+ export declare function AuditLogsConnectorConfigArchivedV1FromJSON(json: any): AuditLogsConnectorConfigArchivedV1;
51
+ export declare function AuditLogsConnectorConfigArchivedV1FromJSONTyped(json: any, ignoreDiscriminator: boolean): AuditLogsConnectorConfigArchivedV1;
52
+ export declare function AuditLogsConnectorConfigArchivedV1ToJSON(json: any): AuditLogsConnectorConfigArchivedV1;
53
+ export declare function AuditLogsConnectorConfigArchivedV1ToJSONTyped(value?: AuditLogsConnectorConfigArchivedV1 | null, ignoreDiscriminator?: boolean): any;
@@ -0,0 +1,67 @@
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 { AuditLogTargetV2FromJSON, AuditLogTargetV2ToJSON, } from './AuditLogTargetV2.js';
18
+ /**
19
+ * Check if a given object implements the AuditLogsConnectorConfigArchivedV1 interface.
20
+ */
21
+ export function instanceOfAuditLogsConnectorConfigArchivedV1(value) {
22
+ if (!('action' in value) || value['action'] === undefined)
23
+ return false;
24
+ if (!('actor' in value) || value['actor'] === undefined)
25
+ return false;
26
+ if (!('context' in value) || value['context'] === undefined)
27
+ return false;
28
+ if (!('occurred_at' in value) || value['occurred_at'] === undefined)
29
+ return false;
30
+ if (!('targets' in value) || value['targets'] === undefined)
31
+ return false;
32
+ if (!('version' in value) || value['version'] === undefined)
33
+ return false;
34
+ return true;
35
+ }
36
+ export function AuditLogsConnectorConfigArchivedV1FromJSON(json) {
37
+ return AuditLogsConnectorConfigArchivedV1FromJSONTyped(json, false);
38
+ }
39
+ export function AuditLogsConnectorConfigArchivedV1FromJSONTyped(json, ignoreDiscriminator) {
40
+ if (json == null) {
41
+ return json;
42
+ }
43
+ return {
44
+ 'action': json['action'],
45
+ 'actor': AuditLogActorV2FromJSON(json['actor']),
46
+ 'context': AuditLogEntryContextV2FromJSON(json['context']),
47
+ 'occurred_at': (json['occurred_at'] == null ? json['occurred_at'] : parseDateTime(json['occurred_at'])),
48
+ 'targets': (json['targets'].map(AuditLogTargetV2FromJSON)),
49
+ 'version': json['version'],
50
+ };
51
+ }
52
+ export function AuditLogsConnectorConfigArchivedV1ToJSON(json) {
53
+ return AuditLogsConnectorConfigArchivedV1ToJSONTyped(json, false);
54
+ }
55
+ export function AuditLogsConnectorConfigArchivedV1ToJSONTyped(value, ignoreDiscriminator = false) {
56
+ if (value == null) {
57
+ return value;
58
+ }
59
+ return {
60
+ 'action': value['action'],
61
+ 'actor': AuditLogActorV2ToJSON(value['actor']),
62
+ 'context': AuditLogEntryContextV2ToJSON(value['context']),
63
+ 'occurred_at': value['occurred_at'] == null ? value['occurred_at'] : serializeDateTime(value['occurred_at']),
64
+ 'targets': (value['targets'].map(AuditLogTargetV2ToJSON)),
65
+ 'version': value['version'],
66
+ };
67
+ }
@@ -321,6 +321,7 @@ export * from './AuditLogsCatalogTypeDeletedV2.js';
321
321
  export * from './AuditLogsCatalogTypeUpdatedV1.js';
322
322
  export * from './AuditLogsCatalogTypeUpdatedV2.js';
323
323
  export * from './AuditLogsCodeRepositoryAccessedV1.js';
324
+ export * from './AuditLogsConnectorConfigArchivedV1.js';
324
325
  export * from './AuditLogsConnectorConfigCreatedV1.js';
325
326
  export * from './AuditLogsConnectorConfigCreatedV2.js';
326
327
  export * from './AuditLogsConnectorConfigTokenGeneratedV1.js';
@@ -323,6 +323,7 @@ export * from './AuditLogsCatalogTypeDeletedV2.js';
323
323
  export * from './AuditLogsCatalogTypeUpdatedV1.js';
324
324
  export * from './AuditLogsCatalogTypeUpdatedV2.js';
325
325
  export * from './AuditLogsCodeRepositoryAccessedV1.js';
326
+ export * from './AuditLogsConnectorConfigArchivedV1.js';
326
327
  export * from './AuditLogsConnectorConfigCreatedV1.js';
327
328
  export * from './AuditLogsConnectorConfigCreatedV2.js';
328
329
  export * from './AuditLogsConnectorConfigTokenGeneratedV1.js';
@@ -1 +1 @@
1
- export declare const VERSION = "2.34.0";
1
+ export declare const VERSION = "2.36.0";
@@ -1,2 +1,2 @@
1
1
  // Written by `make build` from package.json. Do not edit.
2
- export const VERSION = "2.34.0";
2
+ export const VERSION = "2.36.0";
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@incident-io/sdk",
3
- "version": "2.34.0",
3
+ "version": "2.36.0",
4
4
  "description": "TypeScript SDK for the incident.io API",
5
5
  "license": "MIT",
6
6
  "author": "incident.io <support@incident.io>",