github · kdaigle · Dec 12, 2013 · Dec 4, 2013 · Dec 10, 2013 · Jul 22, 2013
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
@@ -36,7 +36,7 @@ active contributor to the hook file itself.
 You can annotate this directly in the hook like so:
 
 ```ruby
-class Service::MyService < Service
+class Service::MyService < Service::HttpPost
   string :project, :api_token
 
   # only include 'project' in the debug logs, skip the api token.
@@ -81,7 +81,7 @@ You can test your service in a ruby irb console:
       # Hash of payload.
       {'blah' => 'payload!'})
 
-    svc.receive_push
+    svc.receive_event
     ```
 
 3. The third argument is optional if you just want to use the sample
@@ -92,7 +92,7 @@ You can test your service in a ruby irb console:
       # Hash of configuration information.
       {'token' => 'abc'})
 
-    svc.receive_push
+    svc.receive_event
     ```
 
 Other hook types

diff --git a/Gemfile.lock b/Gemfile.lock
@@ -1,19 +1,17 @@
 PATH
   remote: .
   specs:
-    github-services (1.0.0.edf0e37)
+    github-services (1.0.0.8a56c1e)
       activeresource (~> 3.0.0)
       addressable (~> 2.2.7)
-      aws-sdk (~> 1.8.0)
+      aws-sdk (~> 1.27)
       faraday (= 0.8.7)
       httparty (= 0.7.4)
       mail (~> 2.3)
       mash (~> 0.1.1)
       mime-types (~> 1.15)
       mqtt (= 0.0.8)
       oauth (= 0.4.4)
-      right_aws (= 3.0.3)
-      right_http_connection (= 1.3.0)
       ruby-hmac (= 0.4.0)
       softlayer_messaging (~> 1.0.2)
       tinder (= 1.8.0.github)
@@ -34,7 +32,7 @@ GEM
       activesupport (= 3.0.20)
     activesupport (3.0.20)
     addressable (2.2.8)
-    aws-sdk (1.8.5)
+    aws-sdk (1.28.1)
       json (~> 1.4)
       nokogiri (>= 1.4.4)
       uuidtools (~> 2.1)
@@ -43,38 +41,34 @@ GEM
     eventmachine (0.12.10)
     faraday (0.8.7)
       multipart-post (~> 1.1)
-    faraday_middleware (0.8.7)
+    faraday_middleware (0.9.0)
       faraday (>= 0.7.4, < 0.9)
     hashie (1.2.0)
     http_parser.rb (0.5.3)
     httparty (0.7.4)
       crack (= 0.1.8)
     i18n (0.5.0)
-    json (1.8.0)
-    jwt (0.1.6)
-      multi_json (>= 1.0)
-    mail (2.3.0)
-      i18n (>= 0.4.0)
+    json (1.8.1)
+    jwt (0.1.8)
+      multi_json (>= 1.5)
+    mail (2.5.4)
       mime-types (~> 1.16)
       treetop (~> 1.4.8)
     mash (0.1.1)
-    mime-types (1.18)
-    mini_portile (0.5.1)
+    mime-types (1.25.1)
+    mini_portile (0.5.2)
     mqtt (0.0.8)
-    multi_json (1.3.2)
-    multipart-post (1.1.5)
+    multi_json (1.8.2)
+    multipart-post (1.2.0)
     nokogiri (1.6.0)
       mini_portile (~> 0.5.0)
     oauth (0.4.4)
     polyglot (0.3.3)
     rake (10.0.3)
     rest-client (1.6.7)
       mime-types (>= 1.16)
-    right_aws (3.0.3)
-      right_http_connection (>= 1.2.5)
-    right_http_connection (1.3.0)
     ruby-hmac (0.4.0)
-    simple_oauth (0.1.5)
+    simple_oauth (0.1.9)
     softlayer_messaging (1.0.2)
       rest-client
     tinder (1.8.0.github)
@@ -88,20 +82,20 @@ GEM
       multi_json (~> 1.0)
       multipart-post (~> 1.1)
       twitter-stream (~> 0.1)
-    treetop (1.4.10)
+    treetop (1.4.15)
       polyglot
       polyglot (>= 0.3.1)
     twilio-ruby (3.9.0)
       builder (>= 2.1.2)
       jwt (>= 0.1.2)
       multi_json (>= 1.3.0)
-    twitter-stream (0.1.15)
+    twitter-stream (0.1.16)
       eventmachine (>= 0.12.8)
       http_parser.rb (~> 0.5.1)
       simple_oauth (~> 0.1.4)
     uuidtools (2.1.4)
     xml-simple (1.0.11)
-    xmpp4r (0.5)
+    xmpp4r (0.5.5)
     xmpp4r-simple-19 (1.0.0)
       xmpp4r (>= 0.3.2)
     yajl-ruby (1.1.0)

diff --git a/docs/amazonsns b/docs/amazonsns
@@ -1,13 +1,37 @@
 Amazon Simple Notification Service
 ==================================
 
-This service lets you publish event messages to Amazon's Simple Notification Service.  Optionally, you can set up an Amazon SQS subscriber if 'sqs_queue' is specified.
+This service lets you publish event messages to Amazon's Simple Notification Service. Please note that SNS Topics are region specific.
 
-Install Notes
--------------
+The AWS Key and Secret you proide can either be from your master account (not recommended) or from an IAM Resource. 
 
-1. 'aws_key' (REQUIRED) is the Amazon Access Key ID of an account with permission to publish SNS notifications.
-2. 'aws_secret' (REQUIRED) is the Amazon Secret Access Key associated with the aws_key
-3. 'sns_topic' (REQUIRED) is either the name of the Amazon SNS topic or the topic's ARN.  If no topic exists by this name, one will be created.  This service will not attempt to create the topic if the ARN is specified, thus allowing the minimum level of permissions (namely: 'sns:Publish') to be used.
-4. 'sqs_queue' (OPTIONAL) is the name of an Amazon SQS Queue to be subscribed to the sns_topic.  If no queue exists by this name, one will be created.
+If using IAM, be sure to check that the user has the correct policies for publishing to the specified SNS Topic. A policy similar to the one below will provide your IAM Resource with the correct permission level.
+
+```
+{
+  "Version": "2012-10-17",
+  "Statement": [
+    {
+      "Action": [
+        "sns:Publish"
+      ],
+      "Sid": "Stmt0000000000000",
+      "Resource": [
+        "arn:aws:sns:us-east-1:718656560584:app-deploy"
+      ],
+      "Effect": "Allow"
+    }
+  ]
+}
+``` 
+
+This service will attempt to provide you with meaningful errors if your configuration is incorrect.
+
+1. 'aws_key' (Required) The access key to an Amazon Account or IAM User.
+
+2. 'aws_secret' (Required) The Amazon secret access key associated with the AWS Key.
+
+3. 'sns_topic' (Required) Full ARN path to the SNS Topic, ie. `arn:aws:sns:eu-west-1:718656560584:sns_topic_name`
+
+4. 'sns_region' (Optional) the identifier for the AWS Region that the SNS Topic is located in. This defaults to `us-east-1`.
 
diff --git a/docs/awsopsworks b/docs/awsopsworks
@@ -0,0 +1,27 @@
+AWS OpsWorks
+============
+
+This service lets you deploy apps in AWS OpsWorks after pushing to the configured branch.
+
+You need to provide an AWS access key id and the corresponding secret access key having at least the permission for the `opsworks:CreateDeployment` action. That's the minimal required policy file:
+
+```
+{
+  "Statement": [
+    {
+      "Effect": "Allow",
+      "Action": "opsworks:CreateDeployment",
+      "Resource": "*"
+    }
+  ]
+}
+```
+
+Install Notes
+-------------
+
+1. **Stack Id** (required) - "OpsWorks ID" on the **stack setting page** in the AWS OpsWorks Console or see `StackId` at http://docs.aws.amazon.com/opsworks/latest/APIReference/API_Stack.html
+2. **App Id** (required) - "OpsWorks ID" on the **app setting page** in the AWS OpsWorks Console or see `AppId` at http://docs.aws.amazon.com/opsworks/latest/APIReference/API_App.html
+3. **Branch Name** (required) - "Branch/Revision" configured for that app in the AWS OpsWorks Console or see `Revision` at http://docs.aws.amazon.com/opsworks/latest/APIReference/API_Source.html
+4. **Aws Access Key Id** (required) - Access key id of an AWS IAM user having the permission for the `opsworks:CreateDeployment` action.
+5. **Aws Secret Access Key** (required) - Corresponding secret access key of the AWS IAM user.
diff --git a/docs/flowdock b/docs/flowdock
@@ -1,10 +1,16 @@
 Broadcast this project's commits, pull requests, issues, and their
 respective comments to Flowdock.
 
-
 Install Notes
 -------------
 
   API Token is a flow-specific token. You can find it either in the flow, or in Flowdock's Integrations help page at https://www.flowdock.com/help/integrations.
 
   Multiple flows may be specified with multiple comma-separated tokens.
+
+  To include certain tags with every message, you can add tags to the tokens. Use + to separate tags. For example, "65f80e994031fcd80f57d1a9e294c1d1d+frontend+web,af8629b07978d1223c9d48d05ff1356+fyi" would add `frontend` and `web` tags to the messages posted to the first flow, and `fyi` to the messages posted to the second flow.
+
+Configure From Flowdock
+-----------------------
+
+  You can also configure hooks from within Flowdock. Those hooks will appear in the `Web Hooks` category of the service hooks. This can be done from the flow’s inbox settings.
diff --git a/docs/gitter b/docs/gitter
@@ -0,0 +1,26 @@
+Gitter
+======
+
+Chat rooms for your public and private repos with awesome GitHub integration.
+
+https://gitter.im
+
+If you want to see detailed repo activity in your room, follow this steps:
+
+  - Click the **Settings Cog** on the top right
+  - Click on **Integrations**
+  - Select **GitHub**
+  - Click on **configure manually** option
+  - Copy and paste the provided token here
+
+Install Notes
+-------------
+
+1. **Token** - Gitter token for this repo
+
+Options
+
+2. **Mute Fork** - Mute fork notifications.
+3. **Mute Watch** - Mute watch notifications.
+4. **Mute Comments** - Mute issue and pull request comments.
+5. **Mute Wiki** - Mute wiki changes.
diff --git a/docs/notifo b/docs/notifo
diff --git a/docs/obs b/docs/obs
@@ -15,7 +15,7 @@ Install Notes
     # osc token --create
 
     You may already specify the package here
-    # osc token --create <PROJECT> <PACKAGE>
+    # osc token --create _PROJECT_ _PACKAGE_
 
     That means the token can only be used for this package. It also means you do not have
     to specify it in github.com. Just using the token is enough.

diff --git a/docs/piwikplugins b/docs/piwikplugins
@@ -0,0 +1,4 @@
+Piwik Plugins
+==============
+
+Piwik is an open analytics platform which can be extended with Plugins and Themes. This service notifies the [Piwik Marketplace](http://plugins.piwik.org) of any new releases to your Piwik plugin. See [http://developer.piwik.org/guides/marketplace](the Publisher Guide) for more information.
diff --git a/docs/sqsqueue b/docs/sqsqueue
@@ -9,3 +9,7 @@ SqsQueue allows GitHub to send a notification to a queue inside your Amazon AWS
 1. Configure your Amazon AWS account with an appropriately set up access-key/secret-key (Either parent account or IAM)
    that has permissions to perform 'SendMessage' operations. (https://console.aws.amazon.com/sqs/)
 
+2. Aws SQS ARN is the unique code SQS references your queue with. It can be copied from the console
+   or fetched through the API. It takes the form of arn:aws:sqs:us-(region)-(dc):(id):(name). Copy and
+   paste the entire string. This hook parses the necessary details from the arn.
+   You may also specify a SQS Queue URL instead of an ARN if you want to use IAM or a Queue that was created using a different account.
diff --git a/docs/versioneye b/docs/versioneye
@@ -0,0 +1,12 @@
+VersionEye is a notification system for software libraries. It notifies you about outdated dependencies in your repository and works currently for Ruby (Bundler), Python (Pypi), Node.JS (NPM), Java (Maven, Gradle), PHP (Composer) and Clojure (Lein). The integration for CocoaPods and Bower is on the way.
+
+This service hook will inform VersionEye every time you push to GitHub. On every push VersionEye will reparse your project file.
+
+Install Notes
+-------------
+
+1.  Sign up for free at http://www.VersionEye.com with your GitHub Account.
+2.  Go to https://www.versioneye.com/user/projects/github_repositories.
+3.  Select a repository that you want VersionEye to monitor for you.
+4.  Go to the project page and copy the project_id from the URL.
+5.  Here you will find your API Key https://www.versioneye.com/settings/api
diff --git a/github-services.gemspec b/github-services.gemspec
@@ -48,18 +48,14 @@ Gem::Specification.new do |spec|
   # Twilio
   spec.add_dependency "twilio-ruby",            "~> 3.9.0"
 
-  # Amazon SQS
-  spec.add_dependency "right_aws",              "3.0.3"
-  spec.add_dependency "right_http_connection",  "1.3.0"
-
   # MQTT
   spec.add_dependency "mqtt", "0.0.8"
 
   # Softlayer Messaging
   spec.add_dependency "softlayer_messaging", "~> 1.0.2"
 
-  # Amazon SNS
-  spec.add_dependency "aws-sdk", "~> 1.8.0"
+  # Amazon SNS, Amazon SQS, AWS OpsWorks
+  spec.add_dependency "aws-sdk", "~> 1.27"
   spec.add_dependency "httparty", "0.7.4"
 
   spec.files = %w(Gemfile LICENSE README.mkdn CONTRIBUTING.md Rakefile)

diff --git a/lib/github-services.rb b/lib/github-services.rb
@@ -26,8 +26,6 @@
 require 'oauth'
 require 'yammer4r'
 require 'twilio-ruby'
-require 'right_aws'
-require 'right_http_connection'
 
 # vendor
 require 'basecamp'