elastic-beanstalk 1.0.0 → 1.0.1

checksums.yaml

@@ -1,15 +1,15 @@
 ---
 !binary "U0hBMQ==":
   metadata.gz: !binary |-
-    OTE1OWJkODc3MDJjOGZjNGQ3ZmQ3NTA4NmNhODMwMjE1YmM5YWVhZA==
+    NjU1YWI4M2E0MDRhNGVkNTE5OGZlYTZmOWU0YTE1NmNlZGFlODRlYg==
   data.tar.gz: !binary |-
-    ZTZkYWFhOGU1ZGI0MGJiOWJjMDQ4M2NmZTE1OGM1NmNjYjRmMWRlNg==
+    NWFhYzg0MjE3MjI0OGU3MzVmODRjMDEyMGJhYTBmNjExM2YwN2VkYQ==
 SHA512:
   metadata.gz: !binary |-
-    MTVkYjhkN2ViNmQ3NmJhZGVlYzBhZDM2YmUzZjQ3ZDE5NGIwOTIwNTQ2MGFm
-    OGM1MGI3MjgwMDc0MGE2YWE4NTFkYWQxMTg5NjhkNmY3NWRiODA3ZWVhY2Mz
-    MWRiYmZmNmUwZWJlODlhMjNkNDE5ZWRkNTNjNjM5ZWNlMzhjNTY=
+    MTY0YTU4Yjc0NjY2MDEyNzhiMmZhMDg0YmM0ODQ3YzhlZDY2ZmMzNGU1MGIx
+    M2YxN2UyNzIxYmU4OGIxZGRmOTE5ZDJkOWU4YWNiMGVjYTRiMTk2YjQ4NGVj
+    ZjZiM2JkZTZhZTMzNTBlYTYxYTY3NDI3MzA1YzllOTExNDBiYjU=
   data.tar.gz: !binary |-
-    ZTU1NDI4YjVkMGI2YWNhZDc3ZmFmZmEyOWFjMGFkNTZjODIzODJmMzFjNTBm
-    NDhlMjhiZjc5NGFjNDU3MDM1NjNmZmM3ZWFjYWVlNmQxYWVkNDZiZjkzZDgy
-    ZDExY2E0NWI1N2YzMTkyN2IzNDdiZDRiM2FlOTYyYmMwNzg2NjE=
+    NGI2ZWQ0Y2U0MDhiMjI3MzJiNzY0MDA3YmZmN2U3NjMxYzZhOWVmZTIxNzMw
+    NDIyMWYwYjY3Y2M0N2QyZWMyZTc4ZGMwYjUyNjVlZDFmMDE3ODdjMmNiNDIx
+    Nzc5MTY5NzAxZDY0YzkzMDU5M2FmYzA1MmZlZGQwNTBiZjk4YWU=

data/LICENSE.txt

@@ -1,4 +1,4 @@
-Copyright (c) 2013 AlienFast, LLC
+Copyright (c) 2014 AlienFast, LLC
 
 MIT License
 

data/README.md

@@ -37,8 +37,8 @@ Since [eb_deployer](https://github.com/ThoughtWorksStudios/eb_deployer) is doing
 
 Given an application named 'acme':
 
-### Step 1: Add a ~/.aws/acme.yml
-This should contain the access and secret keys generated from the selected IAM user.  This is the only file that will need to reside outside the repository.
+### Step 1: Add ~/.aws/acme.yml
+This should contain the access and secret keys generated from the selected IAM user.  This is the only file that will need to reside outside the repository.  Note that this location is configurable in the `config/eb.yml` file.
 
     access_key_id: XXXXXX
     secret_access_key: XXXXXX
@@ -234,3 +234,7 @@ Please contribute! While this is working great, a greater scope of functionality
 3. Commit your changes (`git commit -am 'Add some feature'`)
 4. Push to the branch (`git push origin my-new-feature`)
 5. Create new Pull Request
+
+## Copyright
+
+Copyright (c) 2014 AlienFast. See LICENSE.txt for further details.

data/elastic-beanstalk.gemspec

@@ -31,7 +31,7 @@ Gem::Specification.new do |spec|
 
   # runtime
   spec.add_runtime_dependency 'railties', '>= 3.2'
-  spec.add_runtime_dependency 'eb_deployer'
+  spec.add_runtime_dependency 'eb_deployer', '>= 0.4.4'
   spec.add_runtime_dependency 'awesome_print'
   spec.add_runtime_dependency 'time_diff'
   spec.add_runtime_dependency 'rubyzip'

data/lib/elastic/beanstalk/version.rb

@@ -1,5 +1,5 @@
 module Elastic
   module Beanstalk
-    VERSION = '1.0.0'
+    VERSION = '1.0.1'
   end
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: elastic-beanstalk
 version: !ruby/object:Gem::Version
-  version: 1.0.0
+  version: 1.0.1
 platform: ruby
 authors:
 - Kevin Ross
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2014-01-27 00:00:00.000000000 Z
+date: 2014-05-14 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: bundler
@@ -72,14 +72,14 @@ dependencies:
     requirements:
     - - ! '>='
       - !ruby/object:Gem::Version
-        version: '0'
+        version: 0.4.4
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
     - - ! '>='
       - !ruby/object:Gem::Version
-        version: '0'
+        version: 0.4.4
 - !ruby/object:Gem::Dependency
   name: awesome_print
   requirement: !ruby/object:Gem::Requirement