git.iko.soy/typeable/pagerduty
on develop help sign in
Allow triggering events with details
commit6600c166744326f9664965f11686a356a0d1310a authorBjørn Nordbø <bjorn@wearezeta.com> dateWed 4 Feb 2015, 10:51 (12 years ago) parenta49442b
1 file changed+6−5
src/Network/PagerDuty/Integration.hs+6−5
src/Network/PagerDuty/Integration.hs+6−5
@@ -231,18 +231,19 @@ instance ToJSON Event where
231231-- or ongoing problem. When PagerDuty receives a trigger event, it will either open
232232-- a new incident, or add a new trigger log entry to an existing incident,
233233-- depending on the provided incident_key.
234−trigger :: ServiceKey -- ^ 'serviceKey'
235− -> IncidentKey -- ^ 'incidentKey'
236− -> Text -- ^ 'description'
234+trigger :: ServiceKey -- ^ 'serviceKey'
235+ -> IncidentKey -- ^ 'incidentKey'
236+ -> Text -- ^ 'description'
237+ -> Maybe Object -- ^ 'details'
237238 -> Event
238−trigger k i d =
239+trigger k i d t =
239240 Trigger Trigger'
240241 { _tServiceKey' = k
241242 , _tDescription' = d
242243 , _tIncidentKey' = i
243244 , _tClient' = Nothing
244245 , _tClientUrl' = Nothing
245− , _tDetails' = Nothing
246+ , _tDetails' = t
246247 }
247248
248249-- | Acknowledge events cause the referenced incident to enter the acknowledged