vagrant-commands 0.2.0 → 0.2.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 1ff12e9edc886c0bbf5f9b00de66e72cf7148d6b8da86bb8e080c024052850f8
-  data.tar.gz: 4761720d59916ea65d932364f2b8d980d9b92f80c34c16977ac566ef8a6ac9f7
+  metadata.gz: 99bffecdcfbe1d9286bee3981c1454fdbb557b86bbbc7dce372d9b8e52c4b321
+  data.tar.gz: eee026b56f8e3b102a89e23bf72df4c0ab2a0db3427bea4afdc893c7d550aee6
 SHA512:
-  metadata.gz: c61ab325ae426ed219d143ad1e44d1de9fac0e1c437cb68d3fbec89c999332ce620c48a6ad7fc9b1eabd5866de63786b657e3879d5dacb34db52049eea04616a
-  data.tar.gz: e668353505885a2abd22fe024aabe5219935ac9281a342b6c4bd80225b3eb0267f133d61ab8e7222a6be1343f31ec81ff71170aa188becda6880c4dfd5011de8
+  metadata.gz: ef42b0aa2d38b8fa13a1816f6061d1750d22229769bf225c426d9453f73a9f41d056fc8cd8e632c84ceda50052ef1324185dfdaa7c55b8ea5c942fddd771d755
+  data.tar.gz: ee72cd9f39ace1e486608c12214c21465c2032bcf8084d69c2662b5dd3a5a7650a5652c0019f33c3a99ac56bf30f550d2e12fcace9a81567ca0e66dc8df0a425

data/Gemfile.lock

@@ -28,21 +28,22 @@ GIT
 PATH
   remote: .
   specs:
-    vagrant-commands (0.1.0)
+    vagrant-commands (0.2.1)
 
 GEM
   remote: https://rubygems.org/
   specs:
     bcrypt_pbkdf (1.0.1-x64-mingw32)
-    builder (3.2.3)
+    builder (3.2.4)
     childprocess (0.6.3)
       ffi (~> 1.0, >= 1.0.11)
-    concurrent-ruby (1.1.5)
+    concurrent-ruby (1.1.6)
     domain_name (0.5.20190701)
       unf (>= 0.0.5, < 1.0.0)
     ed25519 (1.2.4)
+    erubi (1.9.0)
     erubis (2.7.0)
-    ffi (1.11.1-x64-mingw32)
+    ffi (1.12.2-x64-mingw32)
     gssapi (1.3.0)
       ffi (>= 1.0.1)
     gyoku (1.3.1)
@@ -62,10 +63,10 @@ GEM
     logging (2.2.2)
       little-plugger (~> 1.1)
       multi_json (~> 1.10)
-    mime-types (3.2.2)
+    mime-types (3.3.1)
       mime-types-data (~> 3.2015)
-    mime-types-data (3.2019.0331)
-    multi_json (1.13.1)
+    mime-types-data (3.2019.1009)
+    multi_json (1.14.1)
     net-scp (1.2.1)
       net-ssh (>= 2.6.5)
     net-sftp (2.1.2)
@@ -75,7 +76,7 @@ GEM
     nori (2.6.0)
     rake (10.5.0)
     rb-fsevent (0.10.3)
-    rb-inotify (0.10.0)
+    rb-inotify (0.10.1)
       ffi (~> 1.0)
     rb-kqueue (0.2.5)
       ffi (>= 0.5.0)
@@ -86,27 +87,28 @@ GEM
       netrc (~> 0.8)
     ruby_dep (1.3.1)
     rubyntlm (0.6.2)
-    rubyzip (1.2.3)
+    rubyzip (1.2.4)
     unf (0.1.4)
       unf_ext
-    unf_ext (0.0.7.6)
-    vagrant_cloud (2.0.2)
+    unf_ext (0.0.7.7-x64-mingw32)
+    vagrant_cloud (2.0.3)
       rest-client (~> 2.0.2)
     wdm (0.1.1)
-    winrm (2.3.2)
+    winrm (2.3.4)
       builder (>= 2.1.2)
-      erubis (~> 2.7)
+      erubi (~> 1.8)
       gssapi (~> 1.2)
       gyoku (~> 1.0)
       httpclient (~> 2.2, >= 2.2.0.2)
       logging (>= 1.6.1, < 3.0)
       nori (~> 2.0)
       rubyntlm (~> 0.6.0, >= 0.6.1)
-    winrm-elevated (1.1.1)
+    winrm-elevated (1.2.1)
+      erubi (~> 1.8)
       winrm (~> 2.0)
       winrm-fs (~> 1.0)
-    winrm-fs (1.3.2)
-      erubis (~> 2.7)
+    winrm-fs (1.3.3)
+      erubi (~> 1.8)
       logging (>= 1.6.1, < 3.0)
       rubyzip (~> 1.1)
       winrm (~> 2.0)

data/README.md

@@ -2,6 +2,37 @@
 Vagrant plugin for custom console commands
 
 ## Overview
-Vagrant Commands allows you to define arbitrary subcommands for your
-Vagrant development environments, allowing you to execute scripts on
-your Vagrant guests using custom interfaces defined in YAML.
+Vagrant Commands allows you to define arbitrary subcommands for your Vagrant development environments, allowing you to execute scripts on your Vagrant guests using custom interfaces defined in YAML.
+
+## Installation
+To install, run `vagrant plugin install vagrant-commands`
+
+## Usage
+The plugin looks for a **vagrant-commands.yml** file in the same directory as your vagrantfile. An example **vagrant-commands.yml** file might be:
+
+    commands:
+      - name: hello
+        synopsis: say "Hello, World!"
+        machine: default
+        exec:
+          command: echo "Hello, World!"
+          
+      - name: restart
+        synopsis: restart Apache service
+        machine: default
+        exec:
+          command: systemctl restart httpd.service
+
+Commands defined in **vagrant-commands.yml** will be shown in the Vagrant help screen like all other commands.
+
+## Limitations
+This plugin has only been confirmed working with environments that use a single virtual machine. Basic support for multi-machine environments has been implemented but has not been confirmed working.
+
+Because this plugin currently relies on SSH to execute commands, it is not compatible with Windows guests.
+
+## Going Forward
+I'd like to make additions and improvements to this plugin in the future. Some things I'd like to implement sometime soon, in no particular order:
+* Test and improve functionality for environments with multiple machines
+* Improve compatibility with Windows guests by using WinRM instead of SSH
+* Allow commands to be defined in **vagrant-commands.yml** that are executed locally instead of in the guest
+* Allow configuration file path (e.g. **vagrant-commands.yml**) to be changed in vagrantfile

data/lib/vagrant-commands/version.rb

@@ -1,3 +1,3 @@
 module VagrantCommands
-  VERSION = "0.2.0"
+  VERSION = "0.2.1"
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: vagrant-commands
 version: !ruby/object:Gem::Version
-  version: 0.2.0
+  version: 0.2.1
 platform: ruby
 authors:
 - Joe D'Amore
 autorequire: 
 bindir: exe
 cert_chain: []
-date: 2019-08-28 00:00:00.000000000 Z
+date: 2020-04-04 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: bundler