nat-monitor 1.0.10 → 1.0.11

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 53d21e0dcaa4528797557bd7513a94aaeb6a1fd6
-  data.tar.gz: 4616081b6d79caecadd87c23cca881882e06c6b1
+  metadata.gz: 0ef71c5eb1a6f5fb396b13cecc77c20a55dd0b32
+  data.tar.gz: a4f7ec5adea7a6b00a5f4a96fe32161a3998c004
 SHA512:
-  metadata.gz: 40f201d0d17c80394211ffdb6796c9262e485b57a6fe63e7e2fdbd5038ae52cd71b8a530f0d86c27ff845b69c20c671176f1d501de8579d1d3e009a5a4535f5f
-  data.tar.gz: d0aebc0ee07fae6d3862012d591394a4dee9d33326d72ee9cd0494a02c6c3be08bc5592293ecfe20ae8fd5ee5eeb1497ffca17d2f66d27f1897f283fd03252eb
+  metadata.gz: 8ac9f3ec2081be7ff3d6ae382ac0694d605b6ed59ea56ff5b81522840d697d5f4245a2e041389571bc4a9ece8b312b10e57409a364f3bb8a392a2a5abeacd9ce
+  data.tar.gz: 012f78d85801e864f838e3a3139664910273d2bdc23db3c9e7516729a49b9da99ec43dcd22948c61630ed6d02a5ac28a2d7cdfc6889a41090af679a9ce8fa100

data/README.md

@@ -2,6 +2,10 @@
 
 Monitors a quorum of NAT servers for an outage and reassigns the specified EC2 route table to point to a working server.
 
+## Requirements
+
+The basic AWS setup required to make this work is actually pretty complex. I recommend reading my [how-to blog post](http://evertrue.github.io/blog/2015/07/06/the-right-way-to-set-up-nat-in-ec2/). Feedback is highly appreciated.
+
 ## Installation
 
 Add this line to your application's Gemfile:
@@ -39,16 +43,25 @@ nodes:
   i-00000003: 10.0.2.1
 ```
 
-Optional properties include:
+Optional properties include (Values shown are the defaults):
 ```yaml
 pings: 3
 ping_timeout: 1
 heartbeat_interval: 10
 ```
 
+Optional AWS configuration include:
+```yaml
+aws_access_key_id: YOUR ACCESS KEY
+aws_secret_access_key: YOUR SECRET KEY
+region: us-east-1
+```
+Note that:
+  - If you don't specify the aws credentials it will use the IAM role of the instance
+
 ## Contributing
 
-1. Fork it ( https://github.com/[my-github-username]/nat-monitor/fork )
+1. Fork it ( https://github.com/evertrue/nat-monitor/fork )
 2. Create your feature branch (`git checkout -b my-new-feature`)
 3. Commit your changes (`git commit -am 'Add some feature'`)
 4. Push to the branch (`git push origin my-new-feature`)

data/lib/nat-monitor/version.rb

@@ -1,5 +1,5 @@
 module EtTools
   class NatMonitor
-    VERSION = '1.0.10'
+    VERSION = '1.0.11'
   end
 end

data/lib/nat-monitor.rb

@@ -114,7 +114,9 @@ module EtTools
           options = { use_iam_profile: true }
         end
 
+        options[:region] = @conf['region'] if @conf['region']
         options[:endpoint] = @conf['aws_url'] if @conf['aws_url']
+
         Fog::Compute::AWS.new(options)
       end
     end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: nat-monitor
 version: !ruby/object:Gem::Version
-  version: 1.0.10
+  version: 1.0.11
 platform: ruby
 authors:
 - Eric Herot
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2015-08-11 00:00:00.000000000 Z
+date: 2015-09-03 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: rspec
@@ -160,3 +160,4 @@ summary: A service for providing an HA NAT in EC2
 test_files:
 - spec/lib/nat-monitor_spec.rb
 - spec/spec_helper.rb
+has_rdoc: