incident_io_api 2.12.0 → 2.13.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.
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA256:
3
- metadata.gz: 734b247fd9014ca6c42cee2f96dadc1368f37a05e193f29fb500bfa59cfda311
4
- data.tar.gz: f60a7c8e119d1007706601af9130d0053ea6ca0e04fad50e043dd968df7c7b0a
3
+ metadata.gz: 40238192040d7218ab8e65726b51b40e9aa2067f6d267dcfcc2c26d2db76764d
4
+ data.tar.gz: 942be54d4a7a19cd0f0b7fb55f96a928ac7edc183e8a6ec36dfaa6cac5e4881b
5
5
  SHA512:
6
- metadata.gz: 8435e217215c77fcbc3194a6e3c9437181f98d5a6bcf0a22c07ead0e37dde4fb5dc6982750c390e3f42cc4bb30edc7f4aebd868d7ae7b76725f4716b32b562e9
7
- data.tar.gz: b7b209be6af601e9297596e822eb25a084e30162d38f9cf7c10e1e417ff8e67e4f387ffd5e3e37210fc5e033356bd83d9923918dfb12aca4d72f6123f410bfbf
6
+ metadata.gz: 1c78e753cb96dcab72289b2d8f7be46b7173a9b089f3840163920bbba14812ebd5df61a41f280e4f1b72dc0b904256891a84bb33797296c400e57e4ff8f3da06
7
+ data.tar.gz: a5380ec4fbfaf09045a0d31c90176940caf30f29d069dc8aaecc068e64676beaf607924983900c45f573c9fe5aedf5b1e00ead0b5743233bd4078d747dbd27b6
@@ -21,7 +21,7 @@ module IncidentIo
21
21
  # URL of the resource
22
22
  attr_accessor :permalink
23
23
 
24
- # E.g. PagerDuty: the external system that holds the resource Known values: `pager_duty_incident`, `opsgenie_alert`, `datadog_monitor_alert`, `github_pull_request`, `gitlab_merge_request`, `sentry_issue`, `jira_issue`, `jsm_alert`, `atlassian_statuspage_incident`, `zendesk_ticket`, `google_calendar_event`, `outlook_calendar_event`, `slack_file`, `salesforce_case`, `arbitrary_url`, `scrubbed`, `statuspage_incident`
24
+ # E.g. PagerDuty: the external system that holds the resource Known values: `pager_duty_incident`, `opsgenie_alert`, `datadog_monitor_alert`, `github_pull_request`, `gitlab_merge_request`, `sentry_issue`, `jira_issue`, `jsm_alert`, `atlassian_statuspage_incident`, `zendesk_ticket`, `google_calendar_event`, `outlook_calendar_event`, `slack_file`, `salesforce_case`, `pylon_issue`, `arbitrary_url`, `scrubbed`, `statuspage_incident`
25
25
  attr_accessor :resource_type
26
26
 
27
27
  # Title of resource
@@ -21,7 +21,7 @@ module IncidentIo
21
21
  # ID of the resource in the external system
22
22
  attr_accessor :external_id
23
23
 
24
- # E.g. PagerDuty: the external system that holds the resource Known values: `pager_duty_incident`, `opsgenie_alert`, `datadog_monitor_alert`, `github_pull_request`, `gitlab_merge_request`, `sentry_issue`, `jira_issue`, `jsm_alert`, `atlassian_statuspage_incident`, `zendesk_ticket`, `google_calendar_event`, `outlook_calendar_event`, `slack_file`, `salesforce_case`, `arbitrary_url`, `scrubbed`, `statuspage_incident`
24
+ # E.g. PagerDuty: the external system that holds the resource Known values: `pager_duty_incident`, `opsgenie_alert`, `datadog_monitor_alert`, `github_pull_request`, `gitlab_merge_request`, `sentry_issue`, `jira_issue`, `jsm_alert`, `atlassian_statuspage_incident`, `zendesk_ticket`, `google_calendar_event`, `outlook_calendar_event`, `slack_file`, `salesforce_case`, `pylon_issue`, `arbitrary_url`, `scrubbed`, `statuspage_incident`
25
25
  attr_accessor :resource_type
26
26
 
27
27
  # Human readable title for the link. Only supported for the arbitrary_url resource type.
@@ -4,5 +4,5 @@ module IncidentIo
4
4
  # The release workflow sets this before building, so it tracks whatever we
5
5
  # last published. Listed in .openapi-generator-ignore so regeneration can't
6
6
  # reset it.
7
- VERSION = "2.12.0"
7
+ VERSION = "2.13.0"
8
8
  end
metadata CHANGED
@@ -1,7 +1,7 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: incident_io_api
3
3
  version: !ruby/object:Gem::Version
4
- version: 2.12.0
4
+ version: 2.13.0
5
5
  platform: ruby
6
6
  authors:
7
7
  - incident.io