simple_deploy
simple_deploy copied to clipboard
intuit
Maintenance Mode - Simple Deploy is an opinionated CLI tool for managing AWS Cloud Formation Stacks.
Cloud Formation has a very sensitive rate limit for their API. We should not fail a build, but sleep and exponentially backoff when these errors are hit: 2013-02-18 08:39:34 -0800...
Clone threw an error which we believe is related to writing to a temp file during clone. This should be done in memory. Tommy Bishop: 2013-09-11 14:42:11 -0700 INFO :...
``` simple_deploy clone -e lc_preprod -s lc-pod-2-dev-1-solr-master-eip-1 -n lc-pod-2-dev-1-solr-master-eip-5 2013-08-07 23:47:20 -0700 INFO : Creating Cloud Formation stack lc-pod-2-dev-1-solr-master-eip-5. /home/kyoung/.rvm/rubies/ruby-1.9.3-p392/lib/ruby/1.9.1/json/common.rb:148:in `initialize': A JSON text must at least contain two octets!...
Here's what I found when trying to update (note: the response hash was me debugging it): ``` shell 2013-07-14 23:12:34 -0700 INFO : Updating Cloud Formation stack lc-pod-2-prod-1-elb-1. {"xmlns"=>"http://cloudformation.amazonaws.com/doc/2010-05-15/", "Error"=>[{"Type"=>["Receiver"],...
@bradly receieved a transient error than did not appear to be handled correctly. We should verify that our error handling logic is sound. 2013-05-21 19:22:21 -0700 INFO : Updating Cloud...
Catch internal errors and log error message: Excon::Errors::InternalServerError /Users/bweaver/.rvm/gems/ruby-1.9.3-p385@simple_deploy_example/gems/excon-0.20.0/lib/excon/middlewares/expects.rb:10:in `response_call': Expected(200) Actual(500 InternalServerError) (Excon::Errors::InternalServerError) request => {:chunk_size=>1048576, :connect_timeout=>60, :headers=>{"Content-Type"=>"application/x-www-form-urlencoded; charset=utf-8", "Host"=>"sdb.u s-west-1.amazonaws.com:443", "Content-Length"=>215}, :idempotent=>true, :instrumentor_name=>"excon", :middlewares=>[Excon::Middleware::Expects, Excon:: Middleware::Idempotent, Excon::Middleware::Instrumentor, Excon::Middleware::Mock],...
Currently notification exceptions will be raised and cause the deployment to fail. These should be caught and log as a warning, then continue to keep from disrupting deployments. 2013-02-14 23:15:02...
``` shell # simple_deploy deploy -e preprod -n foo -a chef_repo=my_sha 2012-12-27 22:20:48 -0800 INFO : Read chef_repo=my_sha 2012-12-27 22:20:52 -0800 INFO : Updating foo. 2012-12-27 22:20:53 -0800 INFO :...
it would be nice to have summary output similar to heirloom, where we can see a summary of some basic attributes of a particular stack, such as date created, template...
