elastic-beanstalk 1.1.6 → 1.1.7

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 8ac39f21da7ab6b45f1575dbb743c27df32ed6d4
-  data.tar.gz: 1111780e7f1fadbc700824f30e5e304d6ae6d520
+  metadata.gz: db486b8d00fc9b4c31c75b6b9c879e204d5017f3
+  data.tar.gz: 0c4b527fca49fe0456492b364b02f7414db5e2a3
 SHA512:
-  metadata.gz: 96caf4b9dc9c72c38e6c18389dcd5e76299ae99e50266d647784485c4467039665d7986634806d0016bbdcbf6704b10a77ca697051a3575a9e300bf274cf053d
-  data.tar.gz: 1642bb10dcd9c7ee06c8f0f338b18988823e0f5c74bbf273d02eb752ce5227088575b23ed063d98ea2a677b6dd3cf51f58ff8099d81a54d75ed9ff323572dcf7
+  metadata.gz: 833300ff20288c4b09aaf1750ec1b87a085feccbc02dbfb7cff2feea4918277eb6194943923b505858e7dfee19e65157ed613da348a182c14c49e0769e2b629f
+  data.tar.gz: a7bad06e982e9a6f5273aff034bc9712bcc45c91377df7e1e597bb195384ef3799b9a97b81a4dd84ae5b4598d4c2267a0fa60e9218cee07c023bdd0d97c62321

data/LICENSE.txt

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

data/README.md

@@ -29,9 +29,9 @@ Or install it yourself as:
 
 ### Plus
 Since [eb_deployer](https://github.com/ThoughtWorksStudios/eb_deployer) is doing the heavy lifting, by proxy you get access to great continuous delivery features such as:
-* Blue Green deployment strategy
-* In Place deployment strategy
-* Smoke Testing upon deployment before Blue Green DNS switching
+* `blue-green` deployment strategy
+* `inplace-update` deployment strategy
+* Smoke Testing upon deployment before `blue-green` CNAME switching
 
 ## Usage
 
@@ -49,16 +49,15 @@ Something like this should get you started
 ```ruby
 app: acme
 region: us-east-1
-# http://docs.aws.amazon.com/elasticbeanstalk/latest/dg/concepts.platforms.html
-solution_stack_name: 64bit Amazon Linux 2013.09 running Ruby 1.9.3
-
+solution_stack_name: 64bit Amazon Linux 2015.03 v2.0.0 running Ruby 2.2 (Passenger Standalone)
+strategy: inplace-update 
 development:
-  strategy: inplace_update
   options:
     aws:autoscaling:launchconfiguration:
       InstanceType: t1.micro
 
 production:
+  strategy: blue-green 
   options:
     aws:autoscaling:launchconfiguration:
       InstanceType: t1.small
@@ -70,18 +69,20 @@ The default is the 'development' environment, change this via command line argum
     $ rake eb:package eb:deploy
 
 ### Step 4. Get some coffee
-This will take a while.  We intend to provide an example in the wiki and/or samples dir that implements a [caching strategy detailed here](http://horewi.cz/faster-rails-3-deployments-to-aws-elastic-beanstalk.html) to speed up deployment.
+This will take a while.   TODO: investigate methods to speed up deployment i.e. cache bundle.  Feel free to post yours in the wiki.
+
+## Rake Tasks
 
-## EB Rake Tasks
+### EB
 
-    rake eb:clobber                 # Remove any generated package
-    rake eb:config                  # Setup AWS.config and merge/override environments into one resolved configuration
-    rake eb:deploy[version]         # Deploy to Elastic Beanstalk
-    rake eb:destroy[force]          # ** Warning: Destroy Elastic Beanstalk application and *all* environments
-    rake eb:package                 # Package zip source bundle for Elastic Beanstalk
-    rake eb:show_config[version]    # Show resolved configuration without doing anything
+    rake eb:clobber                             # Remove any generated package
+    rake eb:config[environment,version]         # Setup AWS.config and merge/override environments into one resolved configuration
+    rake eb:deploy[environment,version]         # Deploy to Elastic Beanstalk
+    rake eb:destroy[force]                      # ** Warning: Destroy Elastic Beanstalk application and *all* environments
+    rake eb:package[environment,version]        # Package zip source bundle for Elastic Beanstalk
+    rake eb:show_config[environment,version]    # Show resolved configuration without doing anything
 
-## EB:RDS Rake Tasks
+### EB:RDS Rake Tasks
 
 The EB:RDS tasks are intended to make use of RDS tasks simple given existing configuration in the eb.yml.
 i.e. create a snapshot before or after an `eb:deploy`.  The following rake tasks exist:
@@ -94,9 +95,7 @@ For example, this would create a snapshot prior to the deployment (and migration
 
     rake eb:rds:create_snapshot[acme, pre-1.1.0] eb:deploy[1.1.0]
 
-## Command line
-
-### RAILS_ENV vs :environment:  
+### Using RAILS_ENV vs :environment:  
 Some people prefer to use `RAILS_ENV`, others prefer to use the `:environment` argument.  Both are accepted. Depending on the use case, each one can be DRYer than the other. 
 Where the task specifies `[:environment, :version]`, consider the `:environment` optional if you want to use the default of `development` or utilize the `RAILS_ENV` instead.  
 
@@ -137,73 +136,54 @@ config/eb.yml
 # This is a sample that has not been executed so it may not be exactly 100%, but is intended to show
 #   that access to full options_settings and .ebextensions is intended.
 #---
+# http://docs.aws.amazon.com/elasticbeanstalk/latest/dg/command-options.html#command-options-ruby
+#
+# This is a sample that has not been executed so it may not be exactly 100%, but is intended to show
+#   that access to full options_settings and .ebextensions is intended.
+#---
 app: acme
 region: us-east-1
-solution_stack_name: 64bit Amazon Linux running Ruby 1.9.3
+# Choose a platform from http://docs.aws.amazon.com/elasticbeanstalk/latest/dg/concepts.platforms.html
+solution_stack_name: 64bit Amazon Linux 2015.03 v2.0.0 running Ruby 2.2 (Passenger Standalone)
+strategy: inplace-update # default to inplace-update to avoid starting new environments
 package:
   verbose: true
-  exclude_dirs: [solr, features] # additional dirs that merge with default excludes
-  exclude_files: [rspec.xml, README*, db/*.sqlite3]
+  exclude_dirs: [features, spec, target, coverage, vcr, flows]  # additional dirs that merge with default excludes
+  exclude_files: [.ruby-*,  rspec.xml, README*, db/*.sqlite3, bower.json]
 smoke_test: |
     lambda { |host|
-      EbSmokeTester.test_url("http://#{host}/ping", 600, 5, 'All good! Everything is up and checks out.')
+      EbSmokeTester.test_url("http://#{host}/health", 600, 5, 'All good! Everything is up and checks out.')
     }
 #--
 ebextensions:
-  01settings.config:
-    # Run rake tasks before an application deployment
-    container_commands:
-      01seed:
-        command: rake db:seed
-        leader_only: true
-  # run any necessary commands
-  02commands.config:
-    container_commands:
+  # General settings for the server environment
+  01-environment.config:
+    commands:
       01timezone:
         command: "ln -sf /usr/share/zoneinfo/America/Chicago /etc/localtime"
 
-  # These are things that make sense for any Ruby application see:
-  #     https://github.com/gkop/elastic-beanstalk-ruby/blob/master/.ebextensions/ruby.config
-  03-ruby.config:
-
+  # These are things that make sense for any Ruby application
+  02-ruby.config:
     # Install git in order to be able to bundle gems from git
     packages:
       yum:
         git: []
-    commands:
-      # Run rake with bundle exec to be sure you get the right version
-      add_bundle_exec:
-        test: test ! -f /opt/elasticbeanstalk/support/.post-provisioning-complete
-        cwd: /opt/elasticbeanstalk/hooks/appdeploy/pre
-        command: perl -pi -e 's/(rake)/bundle exec $1/' 11_asset_compilation.sh 12_db_migration.sh
-      # Bundle with --deployment as recommended by bundler docs
-      #   cf. http://gembundler.com/v1.2/rationale.html under Deploying Your Application
-      add_deployment_flag:
-        test: test ! -f /opt/elasticbeanstalk/support/.post-provisioning-complete
-        cwd: /opt/elasticbeanstalk/hooks/appdeploy/pre
-        command: perl -pi -e 's/(bundle install)/$1 --deployment/' 10_bundle_install.sh
-      # Vendor gems to a persistent directory for speedy subsequent bundling
-      make_vendor_bundle_dir:
-        test: test ! -f /opt/elasticbeanstalk/support/.post-provisioning-complete
-        command: mkdir /var/app/support/vendor_bundle
-      # Store the location of vendored gems in a handy env var
-      set_vendor_bundle_var:
-        test: test ! -f /opt/elasticbeanstalk/support/.post-provisioning-complete
-        cwd: /opt/elasticbeanstalk/support
-        command: sed -i '12iexport EB_CONFIG_APP_VENDOR_BUNDLE=$EB_CONFIG_APP_SUPPORT/vendor_bundle' envvars
-      # The --deployment flag tells bundler to install gems to vendor/bundle/, so
-      # symlink that to the persistent directory
-      symlink_vendor_bundle:
-        test: test ! -f /opt/elasticbeanstalk/support/.post-provisioning-complete
-        cwd: /opt/elasticbeanstalk/hooks/appdeploy/pre
-        command: sed -i '6iln -s $EB_CONFIG_APP_VENDOR_BUNDLE ./vendor/bundle' 10_bundle_install.sh
-      # Don't run the above commands again on this instance
-      #   cf. http://stackoverflow.com/a/16846429/283398
-      z_write_post_provisioning_complete_file:
-        cwd: /opt/elasticbeanstalk/support
-        command: touch .post-provisioning-complete
+        patch: []
+
+  # Run rake tasks before an application deployment
+  03-rake.config:
+    container_commands:
+      01seed:
+        command: rake db:seed
+        leader_only: true
+
 #---
 options:
+
+  # Any environment variables - will be available in ENV
+  aws:elasticbeanstalk:application:environment:
+    FOO: 'bar'
+
   aws:autoscaling:launchconfiguration:
     EC2KeyName: eb-ssh
     SecurityGroups: 'acme-production-control'
@@ -223,10 +203,9 @@ options:
     Notification Endpoint: 'alerts@acme.com'
 
   aws:elasticbeanstalk:application:
-    Application Healthcheck URL: '/'
+    Application Healthcheck URL: '/health'
 #---
 development:
-  strategy: inplace_update
   options:
     aws:autoscaling:launchconfiguration:
       InstanceType: t1.micro
@@ -234,6 +213,7 @@ development:
       RAILS_SKIP_ASSET_COMPILATION: true
 #---
 production:
+  strategy: blue-green # always fire up a new environment and healthcheck before transitioning cname
   options:
     aws:autoscaling:launchconfiguration:
       InstanceType: t1.small
@@ -260,8 +240,7 @@ tier:
 ```
 
 ## Still to come
-1. Caching sample config?
-2. More thorough access to the Elastic Beanstalk api as-needed.
+1. Speedier deployments - investigate caching of bundle and asset pre-compilation to see if there is a common setting to be found
 
 ## Contributing
 
@@ -273,6 +252,7 @@ Please contribute! While this is working great, a greater scope of functionality
 4. Push to the branch (`git push origin my-new-feature`)
 5. Create new Pull Request
 
-## Copyright
 
-Copyright (c) 2014 AlienFast, LLC. See LICENSE.txt for further details.
+## Copyright and License
+
+Copyright (c) 2014-2015 AlienFast, LLC. MIT License, see LICENSE.txt for further details.

data/lib/elastic/beanstalk/tasks/eb.rake

@@ -384,7 +384,7 @@ namespace :eb do
 
   def destroy
     Rake::Task['eb:config'].invoke
-    EbDeployer.destroy(application: EbConfig.app)
+    EbDeployer.destroy(application: EbConfig.app, environment: EbConfig.environment)
     puts "Destroy issued to AWS."
   end
 

data/lib/elastic/beanstalk/version.rb

@@ -1,5 +1,5 @@
 module Elastic
   module Beanstalk
-    VERSION = '1.1.6'
+    VERSION = '1.1.7'
   end
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: elastic-beanstalk
 version: !ruby/object:Gem::Version
-  version: 1.1.6
+  version: 1.1.7
 platform: ruby
 authors:
 - Kevin Ross
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2015-08-18 00:00:00.000000000 Z
+date: 2015-09-01 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: bundler