dual_burner 0.2.0 → 0.3.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: b1d8c2c25e1bcce734886cfcda729cafd83e81d0
-  data.tar.gz: 6ec0cf8e2238eb616a706542cef5e7042246a77a
+  metadata.gz: b49df89d634d3ca0c8fe45b12f43309b757e1fdf
+  data.tar.gz: 0c552354fbfb4dda6474d75a0fd3f2361cb651b1
 SHA512:
-  metadata.gz: bbe353d8e66511ae3e5556b2fa362f662f0bc4c7a7a6f96a6ea559048670fcfb03c2ebf41c82b78f2eb5a95c9711bef36d3486ac34da4b67b59194bb3c8993d0
-  data.tar.gz: db3c3384cd97b8204674d0f3372962737237cb74ef19ab08c4187e550154dbd7b21d74783ad84bf1334d4197acc64f2547253304f65121d6729d9b791f2aed73
+  metadata.gz: e78945c728157e374466a0488c9e361c1e9cedfceab4674ccd3a63cf368521ce5aab6b9121bba739e46e2d5cd30e1e7a559fd06c5ac5753e8551c8af6eb07375
+  data.tar.gz: ff4b58dff18a06b39dac2096bc8f3d29cf97930beef3f9c75bcdcb36247d6f87f46409a664f5de1a8d23f7b6327f6cf4addae5d1c48602be3466cbeb144a3274

data/.rubocop.yml

@@ -18,6 +18,9 @@ Metrics/MethodLength:
 Metrics/ParameterLists:
   Max: 6
 
+Style/ClassLength:
+  Max: 110
+
 Style/Documentation:
   Enabled: false
 

data/README.md

@@ -63,7 +63,9 @@ These are the possible configurations for your application.
 | color           | no            | The presentation color for display. |
 | heroku_app_name | no            | The heroku app name. Needed only for Heroku related commands i.e. `dual_burner config_set`. |
 
-## Deploying
+## Git Commands
+
+### Deploying
 
 Use the `dual_burner deploy` executable to deploy your projects.
 
@@ -85,19 +87,23 @@ You can pass in file locations of your deploy configuration if it is not under `
 
 `dual_burner deploy -c config/dual_burner.yml -e staging -g master`
 
-## Latest Release
+### Latest Release
 
 You can verify that all versions are consistent with the following command.
 
 `dual_burner last_release -e wms_testing`
 
-## Joining Heroku Apps
+## Heroku Commands
+
+Please note, due to how the Heroku Toolbelt operations under a [locked version](https://github.com/heroku/toolbelt/issues/53#issuecomment-47022750) of ruby, do not use `bundle exec` or [install](https://github.com/heroku/toolbelt/issues/53#issuecomment-47022750) Heroku Toolbelt via `brew`.
+
+### Joining Heroku Apps
 
 You can join all Heroku apps in a cluster.
 
 `dual_burner join -e wms_testing`
 
-## Heroku Config Management
+### Heroku Config Management
 
 You can set, unset, and verify consistency of Heroku configurations.
 

data/lib/dual_burner/base_command.rb

@@ -18,6 +18,25 @@ module DualBurner
       @apps ||= apps_for_environment
     end
 
+    def execute_command_with_threads(print_lines: true)
+      results = []
+      threads = []
+
+      apps.each do |app|
+        threads << Thread.new do
+          results << execute_command(
+            yield(app),
+            app: app,
+            print_lines: print_lines
+          )
+        end
+      end
+
+      threads.map(&:join)
+
+      results
+    end
+
     def apps_for_environment
       raise ArgumentError, 'ENV IS NOT PRESENT!' if env.nil?
       raise DualBurner::ConfigurationError, 'CONFIG IS NOT PRESENT!' unless File.exist?(configuration.deploy_file)

data/lib/dual_burner/commands/deployer.rb

@@ -7,24 +7,21 @@ module DualBurner
           git_reference = 'master'
         end
 
-        challenge_user!(git_reference: git_reference) if configuration.interactive?
-
-        threads = []
-        results = []
+        results = execute_command_with_threads do |app|
+          "git ls-remote #{app.remote_url}"
+        end
 
-        apps.each do |app|
-          # Execute each command in a separate thread.
-          # Deploys can take a long time....
-          threads << Thread.new do
-            results << execute_command(
-              build_deploy_command(app: app, git_reference: git_reference),
-              app: app
-            )
-          end
+        # Ensure that the deployer has access to all git remotes.
+        unless verify_results_exit_0(results, context: 'deploy permissions')
+          return false
         end
 
-        # Wait for all commands to complete.
-        threads.map(&:join)
+        challenge_user!(git_reference: git_reference) if configuration.interactive?
+
+        # Deploys can take a long time....
+        results = execute_command_with_threads do |app|
+          build_deploy_command(app: app, git_reference: git_reference)
+        end
 
         verify_results_exit_0(results, context: 'deploys')
       end

data/lib/dual_burner/runner.rb

@@ -21,10 +21,7 @@ module DualBurner
     method_option :env, aliases: '-e', type: :string, required: true, desc: ENV_DESC
     method_option :config, aliases: '-c', type: :string, optional: true, desc: CONFIG_DESC
     method_option :git_reference, aliases: '-g', default: 'master', type: :string, optional: true, desc: GIT_DESC
-    method_option :join, aliases: '-j', default: true, optional: true, desc: 'Join all applications before deploy.'
     def deploy
-      invoke(:join, [], env: options['env']) if options['join'] == true
-
       ::DualBurner::Commands::Deployer.new(
         env: options.fetch('env'),
         configuration: get_configuration_instance(deploy_file: options['config'])

data/lib/dual_burner/version.rb

@@ -1,3 +1,3 @@
 module DualBurner
-  VERSION = '0.2.0'.freeze
+  VERSION = '0.3.0'.freeze
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: dual_burner
 version: !ruby/object:Gem::Version
-  version: 0.2.0
+  version: 0.3.0
 platform: ruby
 authors:
 - Blue Apron Engineering