vagrant-environments 0.1.0

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA1:
+  metadata.gz: b1cfdb945660ce9eae0ce0ce88bfe3f6d565291b
+  data.tar.gz: 0680f875bb88da4e318457b67b210a82a223cfd2
+SHA512:
+  metadata.gz: 5d04eae8f840bbe4276953b0364101545c5241d185fb65d2bff031f51b9a006786b63d0d0bac6382bfe34ff3b6681a13e2efb720b70440c9e91e4562fa4430db
+  data.tar.gz: 92500203c2972e1fa9b34835761a14adc33b21534c0f0856738fd106e6ef563e85a5725c9cde4970a7b7ff09286579bee55ffb375477a8d2938586568f2db420

data/.gitignore

@@ -0,0 +1,6 @@
+/pkg/
+/tmp/
+/.bundle/
+/vendor/bundle/
+Gemfile.lock
+results.html

data/.ruby-version

@@ -0,0 +1 @@
+2.0.0-dev

data/CHANGELOG.md

@@ -0,0 +1,3 @@
+## 0.1.0
+
+* Initial release

data/Gemfile

@@ -0,0 +1,13 @@
+source 'http://rubygems.org'
+
+group :development do
+  # We depend on Vagrant for development, but we don't add it as a
+  # gem dependency because we expect to be installed within the
+  # Vagrant environment itself using `vagrant plugin`.
+  gem 'vagrant', git: 'git://github.com/mitchellh/vagrant.git'
+  gem 'pry'
+end
+
+group :plugins do
+  gemspec
+end

data/LICENSE.md

@@ -0,0 +1,20 @@
+Copyright (c) 2013-2104 Igor Rodionov
+
+Permission is hereby granted, free of charge, to any person obtaining
+a copy of this software and associated documentation files (the
+"Software"), to deal in the Software without restriction, including
+without limitation the rights to use, copy, modify, merge, publish,
+distribute, sublicense, and/or sell copies of the Software, and to
+permit persons to whom the Software is furnished to do so, subject to
+the following conditions:
+
+The above copyright notice and this permission notice shall be
+included in all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
+EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
+MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
+NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE
+LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION
+OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
+WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

data/README.md

@@ -0,0 +1,186 @@
+vagrant-exec [![Gem Version](https://badge.fury.io/rb/vagrant-exec.png)](http://badge.fury.io/rb/vagrant-exec)
+===============
+
+Vagrant plugin to execute commands within the context of VM synced directory.
+
+Description
+-----------
+
+You will probably use the plugin if you don't want to SSH into the box to execute commands simply because your machine environment is already configured (e.g. I use ZSH and TextMate bundles to run specs/features).
+
+Installation
+------------
+
+```bash
+➜ vagrant plugin install vagrant-exec
+```
+
+Example
+-------
+
+```bash
+➜ vagrant exec pwd
+/vagrant
+```
+
+Configuration
+-------------
+
+vagrant-exec has only one configuration option for Vagrantfile, which allows you to alter the behavior of all or specific commands.
+
+```ruby
+Vagrant.configure('2') do |config|
+  config.vm.box = 'precise32'
+  config.exec.commands '*', directory: '/tmp'
+end
+```
+
+Commands can either be:
+
+  * `"*"` (wildcard) - apply options to all the commands
+  * `"command"` (string) - apply options for specific commands
+  * `%w(command1 command2)` (array) - apply options to all commands in array
+
+Configuration options are merged, so if you specify single command in several places, all the option will be applied. The only exception is `:directory`, which is applied only once and in reverse order (i.e. the last set is used).
+
+### Directory
+
+```ruby
+Vagrant.configure('2') do |config|
+  config.vm.box = 'precise32'
+
+  # Make /tmp working directory for all the commands:
+  #   ➜ vagrant exec pwd
+  #   # is the same as
+  #   ➜ vagrant ssh -c "cd /tmp && pwd"
+  config.exec.commands '*', directory: '/tmp'
+
+  # Make /etc working directory for env command:
+  #   ➜ vagrant exec env
+  #   # is the same as
+  #   ➜ vagrant ssh -c "cd /etc && env"
+  config.exec.commands 'env', directory: '/etc'
+end
+```
+
+### Prepend
+
+```ruby
+Vagrant.configure('2') do |config|
+  config.vm.box = 'precise32'
+
+  # Automatically prepend apt-get command with sudo:
+  #   ➜ vagrant exec apt-get install htop
+  #   # is the same as
+  #   ➜ vagrant ssh -c "cd /vagrant && sudo apt-get install htop"
+  config.exec.commands 'apt-get', prepend: 'sudo'
+
+  # Automatically prepend rails and rspec commands with bundle exec:
+  #   ➜ vagrant exec rails c
+  #   # is the same as
+  #   ➜ vagrant ssh -c "cd /vagrant && bundle exec rails c"
+  #
+  #   ➜ vagrant exec rspec spec/
+  #   # is the same as
+  #   ➜ vagrant ssh -c "cd /vagrant && bundle exec rspec spec/"
+  config.exec.commands %w(rails rspec), prepend: 'bundle exec'
+end
+```
+
+### Environment variables
+
+```ruby
+Vagrant.configure('2') do |config|
+  config.vm.box = 'precise32'
+
+  # Automatically export environment variables for ruby command:
+  #   ➜ vagrant exec ruby -e 'puts 1'
+  #   # is the same as
+  #   ➜ vagrant ssh -c "cd /vagrant && export RUBY_GC_MALLOC_LIMIT=100000000 && ruby -e 'puts 1'"
+  config.exec.commands 'ruby', env: { 'RUBY_GC_MALLOC_LIMIT' => 100000000 }
+end
+```
+
+Binstubs
+----------------
+
+It is possible can generate binstubs for all your configured commands. You might want to do this to avoid typing `vagrant exec` every time before command, or if you want integrate your flow in editor (e.g. running tests from editor).
+
+Assuming you have the following configuration:
+
+```ruby
+Vagrant.configure('2') do |config|
+  config.vm.box = 'precise32'
+  config.exec.commands 'bundle'
+  config.exec.commands %w(rails rake), prepend: 'bundle exec'
+  config.exec.commands %w(rspec cucumber), prepend: 'spring'
+end
+```
+
+You can generate binstubs for each command:
+
+```bash
+➜ vagrant exec --binstubs
+Generated binstub for bundle in bin/bundle.
+Generated binstub for cucumber in bin/cucumber.
+Generated binstub for rails in bin/rails.
+Generated binstub for rake in bin/rake.
+Generated binstub for rspec in bin/rspec.
+```
+
+Now you can use `bin/cucumber` instead of `vagrant exec cucumber` to execute commands in VM. All your configuration (directory, environment variables, prepend) will still be used.
+
+Since binstubs use plain SSH to connect to VM, it creates connection much faster because Vagrant is not invoked:
+
+```bash
+➜ time bin/echo 1
+        0.28 real
+➜ time vagrant exec echo 1
+        2.84 real
+```
+
+To make plain SSH work, it saves current SSH configuration of Vagrant to temporary file when you run `vagrant exec --binstubs`. This means that if your VM network configuration has changed (IP address, port), you will have to regenerate binstubs again. So far I had no problems with this, but it's not very convenient for sure.
+
+Moving forward, you can use projects like [direnv](https://github.com/zimbatm/direnv) to add `bin/` to `PATH` and completely forget that you have VM running.
+
+Testing
+----------------
+
+Before running features, you'll need to bootstrap box.
+
+```bash
+➜ bundle exec rake features:bootstrap
+```
+
+To run features, execute the following rake task.
+
+```bash
+➜ bundle exec rake features:run
+```
+
+After you're done, remove Vagrant box.
+
+```bash
+➜ bundle exec rake features:cleanup
+```
+
+To show stdout, add `@announce-stdout` tag to scenario/feature.
+
+Known issues
+-----------------------------
+
+`vagrant-exec` cannot properly handle `-v` in command args (it's caught somewhere before plugin), so executing `vagrant exec ruby -v` will return Vagrant version rather than Ruby. As a workaround, wrap it in quotes: `vagrant exec "ruby -v"`.
+
+Note on Patches/Pull Requests
+-----------------------------
+
+* Fork the project.
+* Make your feature addition or bug fix.
+* Add tests for it. This is important so I don't break it in a future version unintentionally.
+* Commit, do not mess with rakefile, version, or history. (if you want to have your own version, that is fine but bump version in a commit by itself I can ignore when I pull)
+* Send me a pull request. Bonus points for topic branches.
+
+Copyright
+---------
+
+Copyright (c) 2013-2014 Alex Rodionov. See LICENSE.md for details.

data/Rakefile

@@ -0,0 +1,20 @@
+require 'bundler'
+require 'cucumber/rake/task'
+Bundler::GemHelper.install_tasks
+
+namespace :features do
+  desc 'Downloads and adds vagrant box for testing.'
+  task(:bootstrap) do
+    system('bundle exec vagrant box add vagrant_exec http://cloud-images.ubuntu.com/vagrant/precise/current/precise-server-cloudimg-amd64-vagrant-disk1.box')
+  end
+
+  Cucumber::Rake::Task.new(:run) do |t|
+    t.cucumber_opts = %w(--format pretty)
+  end
+
+  desc 'Removes testing vagrant box.'
+  task(:cleanup) do
+    system('bundle exec vagrant destroy -f')
+    system('bundle exec vagrant box remove vagrant_exec virtualbox')
+  end
+end

data/cucumber.yml

@@ -0,0 +1 @@
+default: --require features --format html --out results.html --format pretty

data/features/step_definitions/steps.rb

@@ -0,0 +1,15 @@
+Then(/^SHH subprocess should execute command "(.+)"$/) do |command|
+  ssh  = %w(vagrant@127.0.0.1 -p 2200 -o Compression=yes)
+  ssh += %w(-o DSAAuthentication=yes -o LogLevel=FATAL)
+  ssh += %w(-o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null)
+  ssh += %W(-o IdentitiesOnly=yes -i #{Dir.home}/.vagrant.d/insecure_private_key)
+  ssh += ['-q', '-t', "bash -l -c '#{command.delete("''")}'"]
+  assert_partial_output("Executing SSH in subprocess: #{ssh}", all_output)
+end
+
+Then(/^the file "(.+)" should contain result of vagrant ssh-config$/) do |file|
+  # since "bundle exec" adds some output, we actually
+  # assert that file contents are included in stdout
+  step 'I run `bundle exec vagrant ssh-config`'
+  with_file_content(file) { |content| expect(all_stdout).to include(content) }
+end

data/features/support/env.rb

@@ -0,0 +1,17 @@
+unless `bundle exec vagrant box list`.include?('vagrant_exec')
+  raise 'Box is not added! Run "rake features:bootstrap".'
+end
+
+require 'aruba/cucumber'
+require 'pry-byebug'
+ENV['VAGRANT_LOG'] = 'info'
+
+Before do
+  # VM start takes a long time
+  @aruba_timeout_seconds = 60
+end
+
+After do
+  # halt VM
+  system 'cd tmp/aruba; bundle exec vagrant halt &> /dev/null'
+end

data/features/vagrant-exec.feature

@@ -0,0 +1,43 @@
+@no-clobber
+Feature: vagrant-exec
+  In order to execute commands in Vagrant box
+  Within context of synced folder
+  As a developer using vagrant-exec plugin
+  I want to use "vagrant exec" command
+
+  Background:
+    Given I write to "Vagrantfile" with:
+      """
+      Vagrant.configure('2') do |config|
+        config.vm.box = 'vagrant_exec'
+      end
+      """
+    And I run `bundle exec vagrant up`
+
+  Scenario Outline: shows help correctly
+    When I run `bundle exec vagrant exec <args>`
+    Then the output should contain:
+      """
+      Usage: vagrant exec [options] <command>
+
+          -h, --help                       Print this help
+              --binstubs                   Generate binstubs for configured commands
+      """
+    Examples:
+      | args          |
+      |               |
+      | -h            |
+      | --help        |
+      | -h pwd        |
+      | --help pwd -h |
+
+  Scenario Outline: passes command arguments correctly
+    When I run `bundle exec vagrant exec <command>`
+    Then SHH subprocess should execute command "cd /vagrant && <command>"
+    Examples:
+      | command               |
+      | pwd .                 |
+      | pwd ~                 |
+      | pwd -h                |
+      | pwd --blah            |
+      | 'pwd -h blah -v blah' |

data/features/vagrant-exec/binstubs.feature

@@ -0,0 +1,137 @@
+@no-clobber
+Feature: vagrant-exec binstubs
+  In order to easily integrate vagrant-exec into editors/IDEs
+  And significantly increase speed of executing commands in VM
+  As a user
+  I want to be able to generate binstubs for configured commands
+  Which use plan SSH
+
+  Scenario: generates binstubs for each configured command
+    Given I write to "Vagrantfile" with:
+      """
+      Vagrant.configure('2') do |config|
+        config.vm.box = 'vagrant_exec'
+        config.exec.commands 'echo', directory: '/tmp'
+        config.exec.commands %w(pwd echo), prepend: 'test -d . &&', env: { 'TEST' => 1 }
+      end
+      """
+    And I run `bundle exec vagrant up`
+    When I run `bundle exec vagrant exec --binstubs`
+    Then the exit status should be 0
+    And the output should contain "Generated binstub for echo in bin/echo."
+    And the output should contain "Generated binstub for pwd in bin/pwd."
+    And a file named "bin/echo" should exist
+    And a file named "bin/pwd" should exist
+    And the mode of filesystem object "bin/echo" should match "755"
+    And the mode of filesystem object "bin/pwd" should match "755"
+    And the file "bin/echo" should contain exactly:
+      """
+      #!/bin/bash
+      ssh -F .vagrant/ssh_config -q -t default "bash -l -c 'cd /tmp && export TEST=1 && test -d . && echo $@'"
+
+      """
+    And the file "bin/pwd" should contain exactly:
+      """
+      #!/bin/bash
+      ssh -F .vagrant/ssh_config -q -t default "bash -l -c 'cd /vagrant && export TEST=1 && test -d . && pwd $@'"
+
+      """
+    When I run `bin/echo test`
+    Then the exit status should be 0
+    And the output should contain "test"
+    When I run `bin/pwd`
+    Then the exit status should be 0
+    And the output should contain "/vagrant"
+
+  Scenario: dumps vagrant ssh-config to file
+    Given I write to "Vagrantfile" with:
+      """
+      Vagrant.configure('2') do |config|
+        config.vm.box = 'vagrant_exec'
+        config.exec.commands 'echo'
+      end
+      """
+    And I run `bundle exec vagrant up`
+    When I run `bundle exec vagrant exec --binstubs`
+    Then a file named ".vagrant/ssh_config" should exist
+    And the file ".vagrant/ssh_config" should contain result of vagrant ssh-config
+
+  Scenario: respects configured shell
+    Given I write to "Vagrantfile" with:
+      """
+      Vagrant.configure('2') do |config|
+        config.vm.box = 'vagrant_exec'
+        config.ssh.shell = 'zsh -l'
+        config.exec.commands 'echo'
+      end
+      """
+    And I run `bundle exec vagrant up`
+    When I run `bundle exec vagrant exec --binstubs`
+    Then the file "bin/echo" should contain exactly:
+      """
+      #!/bin/bash
+      ssh -F .vagrant/ssh_config -q -t default "zsh -l -c 'cd /vagrant && echo $@'"
+
+      """
+
+  Scenario: escapes double-quotes in command
+    Given I write to "Vagrantfile" with:
+      """
+      Vagrant.configure('2') do |config|
+        config.vm.box = 'vagrant_exec'
+        config.exec.commands 'echo', env: { 'TEST' => 'one two' }
+      end
+      """
+    And I run `bundle exec vagrant up`
+    When I run `bundle exec vagrant exec --binstubs`
+    Then the file "bin/echo" should contain exactly:
+      """
+      #!/bin/bash
+      ssh -F .vagrant/ssh_config -q -t default "bash -l -c 'cd /vagrant && export TEST=\"one two\" && echo $@'"
+
+      """
+
+  Scenario: skips if no commands are configured
+    Given I write to "Vagrantfile" with:
+      """
+      Vagrant.configure('2') do |config|
+        config.vm.box = 'vagrant_exec'
+      end
+      """
+    And I run `bundle exec vagrant up`
+    When I run `bundle exec vagrant exec --binstubs`
+    Then the exit status should be 0
+    And the output should contain "No commands to generate binstubs for."
+
+  Scenario: skips if only splat commands are configured
+    Given I write to "Vagrantfile" with:
+      """
+      Vagrant.configure('2') do |config|
+        config.vm.box = 'vagrant_exec'
+        config.exec.commands '*', env: { 'TEST' => 'one two' }
+      end
+      """
+    And I run `bundle exec vagrant up`
+    When I run `bundle exec vagrant exec --binstubs`
+    Then the exit status should be 0
+    And the output should contain "No commands to generate binstubs for."
+
+  Scenario: raises if vagrant is not upped
+    Given I write to "Vagrantfile" with:
+      """
+      Vagrant.configure('2') do |config|
+        config.vm.box = 'vagrant_exec'
+      end
+      """
+    When I run `bundle exec vagrant exec --binstubs`
+    Then the exit status should not be 0
+    And the stderr should contain:
+      """
+      The provider for this Vagrant-managed machine is reporting that it
+      is not yet ready for SSH. Depending on your provider this can carry
+      different meanings. Make sure your machine is created and running and
+      try again. Additionally, check the output of `vagrant status` to verify
+      that the machine is in the state that you expect. If you continue to
+      get this error message, please view the documentation for the provider
+      you're using.
+      """

data/features/vagrant-exec/directory.feature

@@ -0,0 +1,46 @@
+@no-clobber
+Feature: vagrant-exec directory
+  In order to change the working directory
+  For commands I execute using vagrant-exec
+  As a user
+  I should be able to specify it in Vagrantfile
+
+  Scenario: uses /vagrant as default directory
+    Given I write to "Vagrantfile" with:
+      """
+      Vagrant.configure('2') do |config|
+        config.vm.box = 'vagrant_exec'
+      end
+      """
+    And I run `bundle exec vagrant up`
+    When I run `bundle exec vagrant exec pwd`
+    Then the exit status should be 0
+    And SHH subprocess should execute command "cd /vagrant && pwd"
+
+  Scenario: uses custom directory for all commands
+    Given I write to "Vagrantfile" with:
+      """
+      Vagrant.configure('2') do |config|
+        config.vm.box = 'vagrant_exec'
+        config.exec.commands '*', directory: '/tmp'
+      end
+      """
+    And I run `bundle exec vagrant up`
+    When I run `bundle exec vagrant exec pwd`
+    Then the exit status should be 0
+    And SHH subprocess should execute command "cd /tmp && pwd"
+
+  Scenario: uses custom directory for specific commands
+    Given I write to "Vagrantfile" with:
+      """
+      Vagrant.configure('2') do |config|
+        config.vm.box = 'vagrant_exec'
+        config.exec.commands %w(pwd echo), directory: '/tmp'
+      end
+      """
+    And I run `bundle exec vagrant up`
+    When I run `bundle exec vagrant exec echo 1`
+    Then SHH subprocess should execute command "cd /tmp && echo 1"
+    When I run `bundle exec vagrant exec env`
+    Then SHH subprocess should execute command "cd /vagrant && env"
+

data/features/vagrant-exec/environment_variables.feature

@@ -0,0 +1,68 @@
+@no-clobber
+Feature: vagrant-exec environment variables
+  In order to automatically set environment variables
+  For commands I execute using vagrant-exec
+  As a user
+  I should be able to specify them in Vagrantfile
+
+  Scenario: exports environment variables for all commands
+    Given I write to "Vagrantfile" with:
+      """
+      Vagrant.configure('2') do |config|
+        config.vm.box = 'vagrant_exec'
+        config.exec.commands '*', env: { 'TEST1' => true, 'TEST2' => false }
+      end
+      """
+    And I run `bundle exec vagrant up`
+    When I run `bundle exec vagrant exec pwd`
+    Then the exit status should be 0
+    And SHH subprocess should execute command "cd /vagrant && export TEST1=true && export TEST2=false && pwd"
+
+  Scenario: exports environment variables for specific commands
+    Given I write to "Vagrantfile" with:
+      """
+      Vagrant.configure('2') do |config|
+        config.vm.box = 'vagrant_exec'
+        config.exec.commands 'cmd', env: { 'TEST1' => 'yo' }
+        config.exec.commands %w(pwd echo), env: { 'TEST2' => true, 'TEST3' => false }
+      end
+      """
+    And I run `bundle exec vagrant up`
+    When I run `bundle exec vagrant exec cmd`
+    Then SHH subprocess should execute command "cd /vagrant && export TEST1=yo && cmd"
+    When I run `bundle exec vagrant exec pwd`
+    Then SHH subprocess should execute command "cd /vagrant && export TEST2=true && export TEST3=false && pwd"
+    When I run `bundle exec vagrant exec echo 1`
+    Then SHH subprocess should execute command "cd /vagrant && export TEST2=true && export TEST3=false && echo 1"
+    When I run `bundle exec vagrant exec env`
+    Then SHH subprocess should execute command "cd /vagrant && env"
+
+  Scenario: combines environment variables
+    Given I write to "Vagrantfile" with:
+      """
+      Vagrant.configure('2') do |config|
+        config.vm.box = 'vagrant_exec'
+        config.exec.commands '*', env: { 'TEST1' => true }
+        config.exec.commands 'pwd', env: { 'TEST2' => false }
+        config.exec.commands %w(pwd echo), env: { 'TEST3' => false }
+      end
+      """
+    And I run `bundle exec vagrant up`
+    When I run `bundle exec vagrant exec pwd`
+    Then SHH subprocess should execute command "cd /vagrant && export TEST1=true && export TEST2=false && export TEST3=false && pwd"
+    When I run `bundle exec vagrant exec echo 1`
+    Then SHH subprocess should execute command "cd /vagrant && export TEST1=true && export TEST3=false && echo 1"
+    When I run `bundle exec vagrant exec env`
+    Then SHH subprocess should execute command "cd /vagrant && export TEST1=true && env"
+
+  Scenario: wraps values with spaces to quotes
+    Given I write to "Vagrantfile" with:
+      """
+      Vagrant.configure('2') do |config|
+        config.vm.box = 'vagrant_exec'
+        config.exec.commands 'pwd', env: { 'TEST' => 'one two' }
+      end
+      """
+    And I run `bundle exec vagrant up`
+    When I run `bundle exec vagrant exec pwd`
+    Then SHH subprocess should execute command "cd /vagrant && export TEST="one two" && pwd"

data/features/vagrant-exec/prepend.feature

@@ -0,0 +1,69 @@
+@no-clobber
+Feature: vagrant-exec prepend
+  In order to automatically prepend with custom command
+  Commands I execute using vagrant-exec
+  As a user
+  I should be able to specify it in Vagrantfile
+
+  Scenario: prepends all commands
+    Given I write to "Vagrantfile" with:
+      """
+      Vagrant.configure('2') do |config|
+        config.vm.box = 'vagrant_exec'
+        config.exec.commands '*', prepend: 'echo vagrant-exec &&'
+      end
+      """
+    And I run `bundle exec vagrant up`
+    When I run `bundle exec vagrant exec pwd`
+    Then the exit status should be 0
+    And SHH subprocess should execute command "cd /vagrant && echo vagrant-exec && pwd"
+
+  Scenario: prepends specific commands
+    Given I write to "Vagrantfile" with:
+      """
+      Vagrant.configure('2') do |config|
+        config.vm.box = 'vagrant_exec'
+        config.exec.commands 'cmd', prepend: 'echo vagrant-exec1 &&'
+        config.exec.commands %w(pwd echo), prepend: 'echo vagrant-exec2 &&'
+      end
+      """
+    And I run `bundle exec vagrant up`
+    When I run `bundle exec vagrant exec cmd`
+    Then SHH subprocess should execute command "cd /vagrant && echo vagrant-exec1 && cmd"
+    When I run `bundle exec vagrant exec pwd`
+    Then SHH subprocess should execute command "cd /vagrant && echo vagrant-exec2 && pwd"
+    When I run `bundle exec vagrant exec echo 1`
+    Then SHH subprocess should execute command "cd /vagrant && echo vagrant-exec2 && echo 1"
+    When I run `bundle exec vagrant exec env`
+    Then SHH subprocess should execute command "cd /vagrant && env"
+
+  Scenario: combines prepended
+    Given I write to "Vagrantfile" with:
+      """
+      Vagrant.configure('2') do |config|
+        config.vm.box = 'vagrant_exec'
+        config.exec.commands '*', prepend: 'echo vagrant-exec1 &&'
+        config.exec.commands 'pwd', prepend: 'echo vagrant-exec2 &&'
+        config.exec.commands %w(pwd echo), prepend: 'echo vagrant-exec3 &&'
+      end
+      """
+    And I run `bundle exec vagrant up`
+    When I run `bundle exec vagrant exec pwd`
+    Then SHH subprocess should execute command "cd /vagrant && echo vagrant-exec1 && echo vagrant-exec2 && echo vagrant-exec3 && pwd"
+    When I run `bundle exec vagrant exec echo 1`
+    Then SHH subprocess should execute command "cd /vagrant && echo vagrant-exec1 && echo vagrant-exec3 && echo 1"
+    When I run `bundle exec vagrant exec env`
+    Then SHH subprocess should execute command "cd /vagrant && echo vagrant-exec1 && env"
+
+  Scenario: adds prepend only in the end
+    Given I write to "Vagrantfile" with:
+      """
+      Vagrant.configure('2') do |config|
+        config.vm.box = 'vagrant_exec'
+        config.exec.commands 'pwd', prepend: 'bundle exec'
+        config.exec.commands 'pwd', env: { 'TEST' => true }
+      end
+      """
+    And I run `bundle exec vagrant up`
+    When I run `bundle exec vagrant exec pwd`
+    Then SHH subprocess should execute command "cd /vagrant && export TEST=true && bundle exec pwd"

data/features/vagrant-exec/validations.feature

@@ -0,0 +1,34 @@
+@no-clobber
+Feature: vagrant-exec validations
+  In order to avoid configuration mistakes for vagrant-exec commands
+  As a user
+  I should see proper validation errors
+
+  Background:
+    Given I write to "Vagrantfile" with:
+      """
+      Vagrant.configure('2') do |config|
+        config.vm.box = 'vagrant_exec'
+        config.exec.commands true, directory: nil, prepend: true, env: 0
+      end
+      """
+
+  Scenario: raises error if command is not string or array of strings
+    When I run `bundle exec vagrant up`
+    Then the exit status should not be 0
+    And the output should contain "Commands should be String or Array<String>, received: true"
+
+  Scenario: raises error if directory is improperly set
+    When I run `bundle exec vagrant up`
+    Then the exit status should not be 0
+    And the output should contain ":directory should be String, received: nil"
+
+  Scenario: raises error if prepend is improperly set
+    When I run `bundle exec vagrant up`
+    Then the exit status should not be 0
+    And the output should contain ":prepend should be String, received: true"
+
+  Scenario: raises error if environment variables are improperly set
+    When I run `bundle exec vagrant up`
+    Then the exit status should not be 0
+    And the output should contain ":env should be Hash, received: 0"

data/lib/vagrant-environments.rb

@@ -0,0 +1,6 @@
+require 'vagrant'
+
+require "vagrant-environments/version"
+require "vagrant-environments/plugin"
+require "vagrant-environments/command"
+require "vagrant-environments/config"

data/lib/vagrant-environments/plugin.rb

@@ -0,0 +1,22 @@
+module VagrantPlugins
+  module Environments
+    class Plugin < Vagrant.plugin(2)
+
+      name 'vagrant-environments'
+      description 'Vagrant plugin to config muiltiple environments (dev, test, stage, prod)'
+
+      config :environments do
+        require_relative 'config'
+        Config
+      end
+
+      config :environment do
+        require_relative 'environment'
+        Environment
+      end
+
+     
+
+    end # Plugin
+  end # Environments
+end # VagrantPlugins

data/lib/vagrant-environments/version.rb

@@ -0,0 +1,7 @@
+module VagrantPlugins
+  module Environments
+
+    VERSION = '0.1.0'
+
+  end # Environments
+end # VagrantPlugins

data/vagrant-environments.gemspec

@@ -0,0 +1,20 @@
+$LOAD_PATH.push File.expand_path('../lib', __FILE__)
+require 'vagrant-environments/version'
+
+Gem::Specification.new do |s|
+  s.name        = 'vagrant-environments'
+  s.version     = VagrantPlugins::Environments::VERSION
+  s.platform    = Gem::Platform::RUBY
+  s.author      = 'Igor Rodionov'
+  s.email       = 'goruha@gmail.com'
+  s.homepage    = 'http://github.com/goruha/vagrant-environments'
+  s.summary     = 'Allow to config Vagrant work with multiple environments'
+  s.description = 'Vagrant plugin to config muiltiple environments (dev, test, stage, prod)'
+  s.license     = 'MIT'
+
+  s.files         = `git ls-files`.split("\n")
+  s.test_files    = `git ls-files -- {test,spec,features}/*`.split("\n")
+  s.executables   = `git ls-files -- bin/*`.split("\n").map { |f| File.basename(f) }
+  s.require_paths = %w(lib)
+
+end

metadata

@@ -0,0 +1,63 @@
+--- !ruby/object:Gem::Specification
+name: vagrant-environments
+version: !ruby/object:Gem::Version
+  version: 0.1.0
+platform: ruby
+authors:
+- Igor Rodionov
+autorequire: 
+bindir: bin
+cert_chain: []
+date: 2014-10-27 00:00:00.000000000 Z
+dependencies: []
+description: Vagrant plugin to config muiltiple environments (dev, test, stage, prod)
+email: goruha@gmail.com
+executables: []
+extensions: []
+extra_rdoc_files: []
+files:
+- ".gitignore"
+- ".ruby-version"
+- CHANGELOG.md
+- Gemfile
+- LICENSE.md
+- README.md
+- Rakefile
+- cucumber.yml
+- features/step_definitions/steps.rb
+- features/support/env.rb
+- features/vagrant-exec.feature
+- features/vagrant-exec/binstubs.feature
+- features/vagrant-exec/directory.feature
+- features/vagrant-exec/environment_variables.feature
+- features/vagrant-exec/prepend.feature
+- features/vagrant-exec/validations.feature
+- lib/vagrant-environments.rb
+- lib/vagrant-environments/plugin.rb
+- lib/vagrant-environments/version.rb
+- vagrant-environments.gemspec
+homepage: http://github.com/goruha/vagrant-environments
+licenses:
+- MIT
+metadata: {}
+post_install_message: 
+rdoc_options: []
+require_paths:
+- lib
+required_ruby_version: !ruby/object:Gem::Requirement
+  requirements:
+  - - ">="
+    - !ruby/object:Gem::Version
+      version: '0'
+required_rubygems_version: !ruby/object:Gem::Requirement
+  requirements:
+  - - ">="
+    - !ruby/object:Gem::Version
+      version: '0'
+requirements: []
+rubyforge_project: 
+rubygems_version: 2.4.2
+signing_key: 
+specification_version: 4
+summary: Allow to config Vagrant work with multiple environments
+test_files: []