broadside 3.0.5 → 3.0.6

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: a3e0d92c4b8e8a5079c5a3008c16c2986fe00862
-  data.tar.gz: 70c9df295003bc04c67ac64ed9acd1809aee14cd
+  metadata.gz: 4d47c9c89f13bf617c34dce01f63f4ce4c6f880c
+  data.tar.gz: 958f75c93c3c14d4ee31b4f1d2414e2f152df360
 SHA512:
-  metadata.gz: 46d9466884ee07ffd715ff753e04aefb1361bf807dbd0d31a1f6aa7ae96d8deb1cc65066c6f1394ee1384b4fa456cf4ca8f18965564505d5f75626292f9f0507
-  data.tar.gz: 5414a05c469f5c7014f834406658fe3ff7a53400cf9d0b01d2b3f14af43513c732769f95adce490cf37095069cf1d9ca7adc321e329774f440435986ec42ee5a
+  metadata.gz: 35c4297593f18933c788b1052c02bf7dbd111adc713fc76ca76aef8a095a034d7f1c391661de157737abe0ee9ffa7c3d962d4e550bb8064b9c1c89d439dff3f7
+  data.tar.gz: 534205c168aa0281a9d68224474d1b258bc7d68f5149d6b9e6d6b3d2d618ebce3d7bcd92096f73f6a90cc02ff3d9d11bc35859439570f4c9fcd90dbfcead95aa

data/CHANGELOG.md

@@ -1,3 +1,12 @@
+# 3.0.6
+- `--tag` option is optional while bootstrapping if you already have a configured `task_definition`
+
+# 3.0.5
+- Make `update_service` work correctly for services configured with load balancers
+
+# 3.0.4
+- `--tag` option required during bootstrapping
+
 # 3.0.3
 - update of GLI specifications, adding on to 3.0.2
 

data/README.md

@@ -5,17 +5,18 @@ A [GLI](https://github.com/davetron5000/gli) based command-line tool for deployi
 ### [The wiki](https://github.com/lumoslabs/broadside/wiki) has all kinds of useful information on it so don't just rely on this README.
 
 ## Overview
-Amazon ECS presents a low barrier to entry for production-level docker applications. Combined with ECS's built-in blue-green deployment, Elastic Load Balancers, Autoscale Groups, and CloudWatch, one can theoretically set up a robust cluster that can scale to serve any number of applications in a short amount of time. The ECS GUI, CLI, overall architecture are not the easiest to work with, however, so Broadside seeks to leverage the [ECS ruby API](http://docs.aws.amazon.com/sdkforruby/api/Aws/ECS.html) to dramatically simplify and improve the configuration and deployment process for developers, offering a simple command line interface and configuration format that should meet most needs.
+Amazon ECS presents a low barrier to entry for production-level docker applications. Combined with ECS's built-in blue-green deployment, Elastic Load Balancers, Autoscale Groups, and CloudWatch, one can theoretically set up a robust cluster that can scale to serve any number of applications in a short amount of time. The ECS GUI, CLI, and overall architecture are not the easiest to work with, however, so Broadside seeks to leverage the [ECS ruby API](http://docs.aws.amazon.com/sdkforruby/api/Aws/ECS.html) to dramatically simplify and improve the configuration and deployment process for developers, offering a simple command line interface and configuration format that should meet most needs.
 
 Broadside does _not_ attempt to handle operational tasks like infrastructure setup and configuration, which are better suited to tools like [terraform](https://www.terraform.io/).
 
 ### Capabilities
 
 - **Trigger** ECS deployments
-- **Launch** a bash shell directly onto a running container in the cluster
+- **Inject** environment variables into ECS containers from local configuration files
+- **Launch a bash shell** on container in the cluster
 - **SSH** directly onto a host running a container
-- **Launch** an ECS task running an arbitrary command
-- **Tail** logs of a running container
+- **Execute** an arbitrary shell command on a container
+- **Tail logs** of a running container
 - **Scale** an existing deployment on the fly
 
 ### Example Config for Quickstarters

data/broadside.gemspec

@@ -24,6 +24,6 @@ Gem::Specification.new do |spec|
   spec.add_dependency 'gli', '~> 2.13'
   spec.add_dependency 'tty', '~> 0.5'
 
-  spec.add_development_dependency 'rspec', '~> 3.4.0'
+  spec.add_development_dependency 'rspec', '~> 3.4'
   spec.add_development_dependency 'bundler', '~> 1.9'
 end

data/lib/broadside/ecs/ecs_deploy.rb

@@ -28,6 +28,7 @@ module Broadside
         info "Task definition for #{family} already exists."
       else
         raise ConfigurationError, "No :task_definition_config for #{family}" unless @target.task_definition_config
+        raise ConfigurationError, 'Bootstrapping a task_definition requires a --tag option' unless @target.tag
         info "Creating an initial task definition for '#{family}' from the config..."
 
         EcsManager.ecs.register_task_definition(

data/lib/broadside/gli/commands.rb

@@ -24,7 +24,10 @@ end
 
 desc 'Bootstrap your service and task definition from the configured definition.'
 command :bootstrap do |bootstrap|
-  add_tag_flag(bootstrap)
+  bootstrap.desc 'Optionally configured tag - without it you cannot bootstrap a task_definition'
+  bootstrap.arg_name 'TAG'
+  bootstrap.flag 'tag', :optional
+
   add_target_flag(bootstrap)
 
   bootstrap.action do |_, options, _|

data/lib/broadside/version.rb

@@ -1,3 +1,3 @@
 module Broadside
-  VERSION = '3.0.5'.freeze
+  VERSION = '3.0.6'.freeze
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: broadside
 version: !ruby/object:Gem::Version
-  version: 3.0.5
+  version: 3.0.6
 platform: ruby
 authors:
 - Matthew Leung
@@ -9,7 +9,7 @@ authors:
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2017-03-01 00:00:00.000000000 Z
+date: 2017-03-07 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: activesupport
@@ -119,14 +119,14 @@ dependencies:
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: 3.4.0
+        version: '3.4'
   type: :development
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: 3.4.0
+        version: '3.4'
 - !ruby/object:Gem::Dependency
   name: bundler
   requirement: !ruby/object:Gem::Requirement