vagrant-orchestrate 0.1.0 → 0.1.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: ae428a0690c14047e05845e7f3a24da592882c9d
-  data.tar.gz: 6f3269c537f110f8c9b66c03e3b8cd2cf689d462
+  metadata.gz: f4f003fe2e9ff1f79c05fdb94187ca3f9957950a
+  data.tar.gz: dd89457152b3cb5240932e40f5163fc182e22887
 SHA512:
-  metadata.gz: bd77d6176cf9fc391905c6f913a84719b0a6fecc1ead0a75e25d6d8ff390b97a45422db484b8a0a831de7090b9e4cfd36d7ecb1de044c855673584de51be3fdd
-  data.tar.gz: 5502b1cef7a68f9c8f5438d1958f9ec51ffb9ed5f50967029cc989a42b2fb75d386a89e1b05b691ac94dd35cf299af61ec9282e53818baef49d7c752192ce26e
+  metadata.gz: cee9ce03f28e452395afbe716422ccfb87994655a38c333f62ae277a5edf08f6a1b54466c6daac37a0ebc00d2194cc29b04fe68d723d0927796b01c1617ff7d0
+  data.tar.gz: 4f669963f2a2b23a58fd4a2cc9bdd3df5094c0ba3d843d20fbb387ab82609316e0b525c110cc652e5324c9613b80959f1d6b47791c22744940050b24022f962f

data/README.md

@@ -53,13 +53,21 @@ required_plugins.each do |plugin|
   system "vagrant plugin install #{plugin}" unless Vagrant.has_plugin? plugin
 end
 Vagrant.configure("2") do |config|
+  # This disables up, provision, reload, and destroy for managed servers. Use
+  # `vagrant orchestrate push` to communicate with managed servers.
+  config.orchestrate.filter_managed_commands = true
+
   config.vm.provision "shell", path: "{{YOUR_SCRIPT_PATH}}"
   config.ssh.username = "{{YOUR_SSH_USERNAME}}"
   config.ssh.private_key_path = "{{YOUR_SSH_PRIVATE_KEY_PATH}}"
 
+  config.vm.define "local", primary: true do |local|
+    local.vm.box = "ubuntu/trusty64"
+  end
+
   managed_servers.each do |instance|
-    config.vm.define "managed-#{instance}" do |box|
-      box.vm.box = "tknerr/managed-server-dummy"
+    config.vm.define instance, autostart: false do |box|
+      box.vm.box = "managed-server-dummy"
       box.vm.box_url = "./dummy.box"
       box.vm.provider :managed do |provider|
         provider.server = instance
@@ -141,6 +149,13 @@ You can run vagrant with increased verbosity if you run into problems
 
     $ vagrant orchestrate push --debug
 
+## Filtering managed commands
+It can be easy to make mistakes such as rebooting production if you have managed long-lived servers as well as local VMs defined in your Vagrantfile. We add some protection with the `orchestrate.filter_managed_commands` configuration setting, which will cause up, provision, reload, and destroy commands to be ignored for servers with the managed provider. 
+
+```ruby
+  config.orchestrate.filter_managed_commands = true
+```
+
 ## Branching strategy
 
 If you have several environments (e.g. dev, test, prod), it is recommended to create

data/lib/vagrant-orchestrate/command/push.rb

@@ -27,11 +27,11 @@ module VagrantPlugins
               @env.ui.info("Skipping machine #{machine.name}")
               next
             end
-            push(options)
+            push(machine, options)
           end
         end
 
-        def push(options)
+        def push(machine, options)
           ENV["VAGRANT_ORCHESTRATE_COMMAND"] = "PUSH"
           begin
             machine.action(:up, options)

data/lib/vagrant-orchestrate/version.rb

@@ -1,5 +1,5 @@
 module VagrantPlugins
   module Orchestrate
-    VERSION = "0.1.0"
+    VERSION = "0.1.1"
   end
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: vagrant-orchestrate
 version: !ruby/object:Gem::Version
-  version: 0.1.0
+  version: 0.1.1
 platform: ruby
 authors:
 - Christopher Baldauf