pagerduty-sdk 1.0.3 → 1.0.4

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: fb62479652d262b0920666828da1fcf7742dde8a
-  data.tar.gz: 4d3ce2efa6fcb9ac163af176f9d406fb1aa431b5
+  metadata.gz: 8fd8e2d77075c877e57f0f9f31c00cbe2be4d093
+  data.tar.gz: c670ba7104f17fbcdbb3b3922fab5ab939766ada
 SHA512:
-  metadata.gz: fc7611edc60bb045e1cc14599fc519565b45a05331ae6a0008b5bfdd20ecf197608e53283adc8cc2fae2a0ce7b6e2afc248496d2da2d6a6af46da26c70df2809
-  data.tar.gz: c44e5ff4d83db5e29cd8aedcb3462b05b90e122bd0b3fad820ca76715bf7c32d25f56c9b305a326d86f19e0f009a51c0225baeeae21b938f7c106f2d75b35d44
+  metadata.gz: 8a924e251cb1d4fcc3982dc0bdce9170b0e7dc649d160d6fd8868d9a9d0e443577a281ea3f06c588aaa62f00a532d90614ca60b0fb59e18eaa35d124739b9285
+  data.tar.gz: 66a3965d498497c8647c735e1fb36c943fac8725b559cb65667dfbc22613ca67bc6f4c4597db674a212616d13df0ed08372e2cb73d8b9b922aad77d250ac091a

data/README.md

@@ -26,4 +26,4 @@ pagerduty = Pagerduty.new(token: "#{token}", subdomain: "#{subdomain}")
 #<Pagerduty:0x007f9a340fc410>
 ```
 
-See [YARD documentation](http://rubydoc.info/gems/pagerduty-sdk/1.0.2/frames) for specific function usage.
+See [YARD documentation](http://rubydoc.info/github/kryptek/pagerduty-sdk/master/frames) for specific function usage.

data/lib/pagerduty.rb

@@ -34,7 +34,9 @@ require 'pagerduty/models/notes'
 require 'pagerduty/models/incident'
 require 'pagerduty/models/incidents'
 require 'pagerduty/models/services'
+require 'pagerduty/models/integration'
 
 # Requests
 require 'pagerduty/requests/incident'
+require 'pagerduty/requests/integration'
 #require 'pagerduty/requests/alerts'

data/lib/pagerduty/models/integration.rb

@@ -0,0 +1,9 @@
+class Pagerduty
+  class Integration
+    include Virtus.model
+
+    attribute :status
+    attribute :message
+    attribute :incident_key
+  end
+end

data/lib/pagerduty/requests/integration.rb

@@ -0,0 +1,74 @@
+class Pagerduty
+
+  # Your monitoring tools should send PagerDuty a trigger event to report a new or ongoing problem. When PagerDuty receives a trigger event, it will either open a new incident, or add a new trigger log entry to an existing incident, depending on the provided incident_key
+  #
+  # ==== Parameters
+  # * options<~Hash>:
+  #   * 'service_key'<~String> - The GUID of one of your "Generic API" services. This is the "service key" listed on a Generic API's service detail page
+  #   * 'description'<~String> - A short description of the problem that led to this trigger. This field (or a truncated version) will be used when generating phone calls, SMS messages and alert emails. It will also appear on the incidents tables in the PagerDuty UI. The maximum length is 1024 characters
+  #   * 'incident_key'<~String> - Identifies the incident to which this trigger event should be applied. If there's no open (i.e. unresolved) incident with this key, a new one will be created. If there's already an open incident with a matching key, this event will be appended to that incident's log. The event key provides an easy way to "de-dup" problem reports. If this field isn't provided, PagerDuty will automatically open a new incident with a unique key
+  #   * 'details'<~Hash> - Any data you'd like included in the incident log
+  #
+  # ==== Returns
+  # * <~Pagerduty::Integration>
+  #   * 'status'<~String>
+  #   * 'incident_key'<~String>
+  #   * 'message'<~String>
+  #
+  # {Pagerduty API Reference}[http://developer.pagerduty.com/documentation/integration/events/trigger]
+  def trigger(options={})
+    Pagerduty::Integration.new(curl({
+      uri: 'https://events.pagerduty.com/generic/2010-04-15/create_event.json',
+      data: options.merge({event_type: 'trigger'}),
+      method: 'POST'
+    }))
+  end
+
+  # Acknowledge events cause the referenced incident to enter the acknowledged state
+  #
+  # ==== Parameters
+  # * options<~Hash>:
+  #   * 'service_key'<~String> - The GUID of one of your "Generic API" services. This is the "service key" listed on a Generic API's service detail page
+  #   * 'description'<~String> - Text that will appear in the incident's log associated with this event.
+  #   * 'incident_key'<~String> - Identifies the incident to acknowledge. This should be the incident_key you received back when the incident was first opened by a trigger event. Acknowledge events referencing resolved or nonexistent incidents will be discarded
+  #   * 'details'<~Hash> - Any data you'd like included in the incident log
+  #
+  # ==== Returns
+  # * <~Pagerduty::Integration>
+  #   * 'status'<~String>
+  #   * 'incident_key'<~String>
+  #   * 'message'<~String>
+  #
+  # {Pagerduty API Reference}[http://developer.pagerduty.com/documentation/integration/events/trigger]
+  def acknowledge(options={})
+    Pagerduty::Integration.new(curl({
+      uri: 'https://events.pagerduty.com/generic/2010-04-15/create_event.json',
+      data: options.merge({event_type: 'acknowledge'}),
+      method: 'POST'
+    }))
+  end
+
+  # Resolve events cause the referenced incident to enter the resolved state
+  #
+  # ==== Parameters
+  # * options<~Hash>:
+  #   * 'service_key'<~String> - The GUID of one of your "Generic API" services. This is the "service key" listed on a Generic API's service detail page
+  #   * 'description'<~String> - Text that will appear in the incident's log associated with this event.
+  #   * 'incident_key'<~String> - Identifies the incident to acknowledge. This should be the incident_key you received back when the incident was first opened by a trigger event. Acknowledge events referencing resolved or nonexistent incidents will be discarded
+  #   * 'details'<~Hash> - Any data you'd like included in the incident log
+  #
+  # ==== Returns
+  # * <~Pagerduty::Integration>
+  #   * 'status'<~String>
+  #   * 'incident_key'<~String>
+  #   * 'message'<~String>
+  #
+  # {Pagerduty API Reference}[http://developer.pagerduty.com/documentation/integration/events/trigger]
+  def resolve(options={})
+    Pagerduty::Integration.new(curl({
+      uri: 'https://events.pagerduty.com/generic/2010-04-15/create_event.json',
+      data: options.merge({event_type: 'resolve'}),
+      method: 'POST'
+    }))
+  end
+end

data/pagerduty-sdk.gemspec

@@ -6,7 +6,7 @@ require 'pagerduty/pagerduty'
 
 Gem::Specification.new do |gem|
   gem.name          = "pagerduty-sdk"
-  gem.version       = '1.0.3'
+  gem.version       = '1.0.4'
   gem.authors       = ["Alfred Moreno"]
   gem.email         = ["kryptek@gmail.com"]
   gem.description   = %q{An SDK for Pagerduty's API}

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: pagerduty-sdk
 version: !ruby/object:Gem::Version
-  version: 1.0.3
+  version: 1.0.4
 platform: ruby
 authors:
 - Alfred Moreno
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2013-11-02 00:00:00.000000000 Z
+date: 2013-11-03 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: active_support
@@ -72,6 +72,7 @@ files:
 - lib/pagerduty/models/escalationpolicies.rb
 - lib/pagerduty/models/incident.rb
 - lib/pagerduty/models/incidents.rb
+- lib/pagerduty/models/integration.rb
 - lib/pagerduty/models/laststatuschangeby.rb
 - lib/pagerduty/models/log_entry.rb
 - lib/pagerduty/models/maintenance_window.rb
@@ -88,6 +89,7 @@ files:
 - lib/pagerduty/pagerduty.rb
 - lib/pagerduty/requests/alerts.rb
 - lib/pagerduty/requests/incident.rb
+- lib/pagerduty/requests/integration.rb
 - pagerduty-sdk.gemspec
 homepage: https://github.com/kryptek/pagerduty-sdk
 licenses: