vagrant-plugin-dummy 0.0.1

data/.gitignore

@@ -0,0 +1,20 @@
+*.gem
+*.rbc
+Gemfile.lock
+.bundle
+.config
+.yardoc
+InstalledFiles
+_yardoc
+coverage
+doc/
+lib/bundler/man
+pkg
+rdoc
+spec/reports
+test/tmp
+test/version_tmp
+tmp
+.vagrant
+Vagrantfile
+.*.swp

data/Gemfile

@@ -0,0 +1,11 @@
+source "https://rubygems.org"
+
+# Specify your gem's dependencies in my_gem.gemspec
+gemspec
+
+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", :tag => 'v1.2.7'
+end

data/README.md

@@ -0,0 +1,24 @@
+vagrant-plugin-dummy
+==========================
+
+This is a "dummy" plugin for vagrant. This is useful if you want to only use vagrant for creating and destroying clean guests.
+
+Installing vagrant-plugin-dummy
+==========================
+
+### Installing from source
+
+```
+bundle install
+bundle exec rake
+vagrant plugin install pkg/vagrant-plugin-dummy-0.0.1.gem
+```
+
+Usage
+==========================
+
+Addd this to a Vagrantfile:
+
+```
+config.vm.guest :dummy
+```

data/Rakefile

@@ -0,0 +1,15 @@
+require 'rubygems'
+require 'bundler/setup'
+require 'rspec/core/rake_task'
+
+# Change to the directory of this file.
+Dir.chdir(File.expand_path("../", __FILE__))
+
+# For gem creation and bundling
+require "bundler/gem_tasks"
+
+# Install the `spec` task so that we can run tests.
+RSpec::Core::RakeTask.new
+
+# Default task is to build the gem
+task :default => "build"

data/lib/vagrant-plugin-dummy/communication/communicator.rb

@@ -0,0 +1,51 @@
+require 'timeout'
+require 'log4r'
+require_relative '../errors'
+
+module VagrantPluginDummy
+  module Communication
+    # Provides no communication with the machine.
+    class DummyCommunicator < Vagrant.plugin("2", :communicator)
+
+      attr_reader :logger
+      attr_reader :machine
+
+      def self.match?(machine)
+        machine.config.vm.guest.eql? :dummy
+      end
+
+      def initialize(machine)
+        @machine = machine
+        @logger = Log4r::Logger.new("vagrant_plugin_dummy::communication::dummycommunicator")
+        @logger.debug("initializing DummyCommunicator")
+      end
+
+      def ready?
+        @logger.warn("Assuming the machine is ready.")
+        return true
+      end
+
+      def execute(command, opts={}, &block)
+        @logger.warn("DummyCommunicator.execute isn't implemented")
+        return 0
+      end
+      alias_method :sudo, :execute
+
+      def test(command, opts=nil)
+        return false unless @machine.config.vm.guest.eql? :dummy
+      end
+
+      def upload(from, to)
+        @logger.warn("DummyCommunicator.upload isn't implemented")
+      end
+
+      def download(from, to=nil)
+        @logger.warn("DummyCommunicator.download isn't implemented")
+      end
+
+      def session
+        @session ||= new_session
+      end
+    end
+  end
+end

data/lib/vagrant-plugin-dummy/errors.rb

@@ -0,0 +1,13 @@
+require 'vagrant/errors'
+
+module VagrantPluginDummy
+  module Errors
+    class VagrantPluginDummyError < ::Vagrant::Errors::VagrantError
+      error_namespace("vagrant_plugin_dummy.errors")
+    end
+
+    class PluginDummyError < VagrantPluginDummyError
+      error_key(:plugin_dummy_error)
+    end
+  end
+end

data/lib/vagrant-plugin-dummy/guest/dummy.rb

@@ -0,0 +1,48 @@
+require "vagrant"
+
+module VagrantPluginDummy
+  module Guest
+    class Dummy < Vagrant.plugin("2", :guest)
+
+      # Vagrant 1.1.x compatibibility methods
+      # Implement the 1.1.x methods and call through to the new 1.2.x capabilities
+
+      attr_reader :machine
+
+      def initialize(machine = nil)
+        super(machine) unless machine == nil
+        @machine = machine
+      end
+
+      def change_host_name(name)
+        false
+      end
+
+      def distro_dispatch
+        :dummy
+      end
+
+      def halt
+        false
+      end
+
+      def mount_virtualbox_shared_folder(name, guestpath, options)
+        false
+      end
+
+      def mount_vmware_shared_folder(name, guestpath, options)
+        false
+      end
+
+      def configure_networks(networks)
+        false
+      end
+
+      # Vagrant 1.2.x compatibibility methods
+
+      def detect?(machine)
+        @machine.communicate.test("")
+      end
+    end
+  end
+end

data/lib/vagrant-plugin-dummy/monkey_patches/lib/vagrant/machine.rb

@@ -0,0 +1,27 @@
+require_relative '../../../communication/communicator'
+
+module Vagrant
+  class Machine
+
+    ssh_communicate = instance_method(:communicate)
+
+    # This patch is needed until Vagrant supports a configurable communication channel
+    define_method(:communicate) do
+      unless @communicator
+        if @config.vm.guest.eql? :dummy
+          @logger.info("guest is #{@config.vm.guest}, using no communication channel")
+          @communicator = ::VagrantPluginDummy::Communication::DummyCommunicator.new(self)
+        else
+          @logger.info("guest is #{@config.vm.guest}, using SSH for communication channel")
+          @communicator = ssh_communicate.bind(self).()
+        end
+      end
+      @communicator
+    end
+
+    def is_dummy?
+      return @config.vm.guest.eql? :dummy
+    end
+
+  end
+end

data/lib/vagrant-plugin-dummy/plugin.rb

@@ -0,0 +1,100 @@
+begin
+  require "vagrant"
+rescue LoadError
+  raise "The vagrant-plugin-dummy vagrant plugin must be run with vagrant."
+end
+
+# This is a sanity check to make sure no one is attempting to install
+# this into an early Vagrant version.
+if Vagrant::VERSION < "1.1.0"
+  raise "The vagrant-plugin-dummy vagrant plugin is only compatible with Vagrant 1.1+"
+end
+
+# Monkey Patch the VM object to support a non-existing communication channel
+# TODO: is this necessary?
+require_relative "monkey_patches/lib/vagrant/machine"
+
+module VagrantPluginDummy
+  class Plugin < Vagrant.plugin("2")
+    name "Dummy guest"
+    description <<-DESC
+    This plugin installs a provider that tries its best to not touch the
+    machine.
+    DESC
+
+    guest(:dummy) do
+      require_relative "guest/dummy"
+      VagrantPluginDummy::Guest::Dummy
+    end
+
+    # Vagrant 1.2 introduced the concept of capabilities instead of implementing
+    # an interface on the guest.
+#    if Vagrant::VERSION >= "1.2.0"
+#
+#      guest_capability(:windows, :change_host_name) do
+#        require_relative "guest/cap/change_host_name"
+#        VagrantPluginDummy::Guest::Cap::ChangeHostName
+#      end
+#
+#      guest_capability(:windows, :configure_networks) do
+#        require_relative "guest/cap/configure_networks"
+#        VagrantPluginDummy::Guest::Cap::ConfigureNetworks
+#      end
+#
+#      guest_capability(:windows, :halt) do
+#        require_relative "guest/cap/halt"
+#        VagrantPluginDummy::Guest::Cap::Halt
+#      end
+#
+#      guest_capability(:windows, :mount_virtualbox_shared_folder) do
+#        require_relative "guest/cap/mount_virtualbox_shared_folder"
+#        VagrantPluginDummy::Guest::Cap::MountVirtualBoxSharedFolder
+#      end
+#
+#      guest_capability(:windows, :mount_vmware_shared_folder) do
+#        require_relative "guest/cap/mount_vmware_shared_folder"
+#        VagrantPluginDummy::Guest::Cap::MountVMwareSharedFolder
+#      end
+#
+#    end
+
+    # This initializes the internationalization strings.
+    def self.setup_i18n
+      I18n.load_path << File.expand_path("locales/en.yml", VagrantPluginDummy.vagrant_plugin_dummy_root)
+      I18n.reload!
+    end
+
+    # This sets up our log level to be whatever VAGRANT_LOG is.
+    def self.setup_logging
+      require "log4r"
+
+      level = nil
+      begin
+        level = Log4r.const_get(ENV["VAGRANT_LOG"].upcase)
+      rescue NameError
+        # This means that the logging constant wasn't found,
+        # which is fine. We just keep `level` as `nil`. But
+        # we tell the user.
+        level = nil
+      end
+
+      # Some constants, such as "true" resolve to booleans, so the
+      # above error checking doesn't catch it. This will check to make
+      # sure that the log level is an integer, as Log4r requires.
+      level = nil if !level.is_a?(Integer)
+
+      # Set the logging level on all "vagrant" namespaced
+      # logs as long as we have a valid level.
+      if level
+        logger = Log4r::Logger.new("vagrant_plugin_dummy")
+        logger.outputters = Log4r::Outputter.stderr
+        logger.level = level
+        logger = nil
+      end
+    end
+
+  end
+end
+
+VagrantPluginDummy::Plugin.setup_logging()
+VagrantPluginDummy::Plugin.setup_i18n()

data/lib/vagrant-plugin-dummy/version.rb

@@ -0,0 +1,3 @@
+module VagrantPluginDummy
+  VERSION = "0.0.1"
+end

data/lib/vagrant-plugin-dummy.rb

@@ -0,0 +1,24 @@
+require "pathname"
+
+module VagrantPluginDummy
+
+  def self.vagrant_plugin_dummy_root
+    @vagrant_plugin_dummy_root ||= Pathname.new(File.expand_path("../../", __FILE__))
+  end
+
+  def self.load_script(script_file_name)
+    File.read(expand_script_path(script_file_name))
+  end
+
+  def self.load_script_template(script_file_name, options)
+    Vagrant::Util::TemplateRenderer.render(expand_script_path(script_file_name), options)
+  end
+
+  # TODO: unnecessary?
+  def self.expand_script_path(script_file_name)
+    File.expand_path("lib/vagrant-plugin-dummy/scripts/#{script_file_name}", VagrantPluginDummy.vagrant_plugin_dummy_root)
+  end
+
+end
+
+require "vagrant-plugin-dummy/plugin"

data/locales/en.yml

@@ -0,0 +1,8 @@
+en:
+  vagrant_plugin_dummy:
+
+    errors:
+      plugin_dummy_error: |-
+        An error has occurred in the VagrantPluginDummy plugin provided by
+        vagrant-plugin-dummy.
+

data/oldgit/FETCH_HEAD

@@ -0,0 +1,4 @@
+10332b013b911516b20c344f933aadafefc9b752	not-for-merge	branch 'chef-schtasks' of github.com:WinRb/vagrant-windows
+a98d27d5b4f16de29bd3bf9c486d25b14d5960c3	not-for-merge	branch 'master' of github.com:WinRb/vagrant-windows
+b4c93197e40d3c2b38d06f316bfb1fd5f0a120de	not-for-merge	branch 'vagrant-1.2' of github.com:WinRb/vagrant-windows
+f09f1b803ab437ec9e31d28560df03add6944308	not-for-merge	branch 'winrm-2.0' of github.com:WinRb/vagrant-windows

data/oldgit/HEAD

@@ -0,0 +1 @@
+ref: refs/heads/dummy-master

data/oldgit/ORIG_HEAD

@@ -0,0 +1 @@
+b4c93197e40d3c2b38d06f316bfb1fd5f0a120de

data/oldgit/config

@@ -0,0 +1,12 @@
+[core]
+	repositoryformatversion = 0
+	filemode = true
+	bare = false
+	logallrefupdates = true
+[branch "master"]
+[remote "origin"]
+	url = git@github.com:WinRb/vagrant-windows.git
+	fetch = +refs/heads/*:refs/remotes/origin/*
+[branch "vagrant-1.2"]
+	remote = origin
+	merge = refs/heads/vagrant-1.2

data/oldgit/description

@@ -0,0 +1 @@
+Unnamed repository; edit this file 'description' to name the repository.

data/oldgit/hooks/applypatch-msg.sample

@@ -0,0 +1,15 @@
+#!/bin/sh
+#
+# An example hook script to check the commit log message taken by
+# applypatch from an e-mail message.
+#
+# The hook should exit with non-zero status after issuing an
+# appropriate message if it wants to stop the commit.  The hook is
+# allowed to edit the commit message file.
+#
+# To enable this hook, rename this file to "applypatch-msg".
+
+. git-sh-setup
+test -x "$GIT_DIR/hooks/commit-msg" &&
+	exec "$GIT_DIR/hooks/commit-msg" ${1+"$@"}
+:

data/oldgit/hooks/commit-msg.sample

@@ -0,0 +1,24 @@
+#!/bin/sh
+#
+# An example hook script to check the commit log message.
+# Called by "git commit" with one argument, the name of the file
+# that has the commit message.  The hook should exit with non-zero
+# status after issuing an appropriate message if it wants to stop the
+# commit.  The hook is allowed to edit the commit message file.
+#
+# To enable this hook, rename this file to "commit-msg".
+
+# Uncomment the below to add a Signed-off-by line to the message.
+# Doing this in a hook is a bad idea in general, but the prepare-commit-msg
+# hook is more suited to it.
+#
+# SOB=$(git var GIT_AUTHOR_IDENT | sed -n 's/^\(.*>\).*$/Signed-off-by: \1/p')
+# grep -qs "^$SOB" "$1" || echo "$SOB" >> "$1"
+
+# This example catches duplicate Signed-off-by lines.
+
+test "" = "$(grep '^Signed-off-by: ' "$1" |
+	 sort | uniq -c | sed -e '/^[ 	]*1[ 	]/d')" || {
+	echo >&2 Duplicate Signed-off-by lines.
+	exit 1
+}

data/oldgit/hooks/post-update.sample

@@ -0,0 +1,8 @@
+#!/bin/sh
+#
+# An example hook script to prepare a packed repository for use over
+# dumb transports.
+#
+# To enable this hook, rename this file to "post-update".
+
+exec git update-server-info

data/oldgit/hooks/pre-applypatch.sample

@@ -0,0 +1,14 @@
+#!/bin/sh
+#
+# An example hook script to verify what is about to be committed
+# by applypatch from an e-mail message.
+#
+# The hook should exit with non-zero status after issuing an
+# appropriate message if it wants to stop the commit.
+#
+# To enable this hook, rename this file to "pre-applypatch".
+
+. git-sh-setup
+test -x "$GIT_DIR/hooks/pre-commit" &&
+	exec "$GIT_DIR/hooks/pre-commit" ${1+"$@"}
+:

data/oldgit/hooks/pre-commit.sample

@@ -0,0 +1,50 @@
+#!/bin/sh
+#
+# An example hook script to verify what is about to be committed.
+# Called by "git commit" with no arguments.  The hook should
+# exit with non-zero status after issuing an appropriate message if
+# it wants to stop the commit.
+#
+# To enable this hook, rename this file to "pre-commit".
+
+if git rev-parse --verify HEAD >/dev/null 2>&1
+then
+	against=HEAD
+else
+	# Initial commit: diff against an empty tree object
+	against=4b825dc642cb6eb9a060e54bf8d69288fbee4904
+fi
+
+# If you want to allow non-ascii filenames set this variable to true.
+allownonascii=$(git config hooks.allownonascii)
+
+# Redirect output to stderr.
+exec 1>&2
+
+# Cross platform projects tend to avoid non-ascii filenames; prevent
+# them from being added to the repository. We exploit the fact that the
+# printable range starts at the space character and ends with tilde.
+if [ "$allownonascii" != "true" ] &&
+	# Note that the use of brackets around a tr range is ok here, (it's
+	# even required, for portability to Solaris 10's /usr/bin/tr), since
+	# the square bracket bytes happen to fall in the designated range.
+	test $(git diff --cached --name-only --diff-filter=A -z $against |
+	  LC_ALL=C tr -d '[ -~]\0' | wc -c) != 0
+then
+	echo "Error: Attempt to add a non-ascii file name."
+	echo
+	echo "This can cause problems if you want to work"
+	echo "with people on other platforms."
+	echo
+	echo "To be portable it is advisable to rename the file ..."
+	echo
+	echo "If you know what you are doing you can disable this"
+	echo "check using:"
+	echo
+	echo "  git config hooks.allownonascii true"
+	echo
+	exit 1
+fi
+
+# If there are whitespace errors, print the offending file names and fail.
+exec git diff-index --check --cached $against --

data/oldgit/hooks/pre-rebase.sample

@@ -0,0 +1,169 @@
+#!/bin/sh
+#
+# Copyright (c) 2006, 2008 Junio C Hamano
+#
+# The "pre-rebase" hook is run just before "git rebase" starts doing
+# its job, and can prevent the command from running by exiting with
+# non-zero status.
+#
+# The hook is called with the following parameters:
+#
+# $1 -- the upstream the series was forked from.
+# $2 -- the branch being rebased (or empty when rebasing the current branch).
+#
+# This sample shows how to prevent topic branches that are already
+# merged to 'next' branch from getting rebased, because allowing it
+# would result in rebasing already published history.
+
+publish=next
+basebranch="$1"
+if test "$#" = 2
+then
+	topic="refs/heads/$2"
+else
+	topic=`git symbolic-ref HEAD` ||
+	exit 0 ;# we do not interrupt rebasing detached HEAD
+fi
+
+case "$topic" in
+refs/heads/??/*)
+	;;
+*)
+	exit 0 ;# we do not interrupt others.
+	;;
+esac
+
+# Now we are dealing with a topic branch being rebased
+# on top of master.  Is it OK to rebase it?
+
+# Does the topic really exist?
+git show-ref -q "$topic" || {
+	echo >&2 "No such branch $topic"
+	exit 1
+}
+
+# Is topic fully merged to master?
+not_in_master=`git rev-list --pretty=oneline ^master "$topic"`
+if test -z "$not_in_master"
+then
+	echo >&2 "$topic is fully merged to master; better remove it."
+	exit 1 ;# we could allow it, but there is no point.
+fi
+
+# Is topic ever merged to next?  If so you should not be rebasing it.
+only_next_1=`git rev-list ^master "^$topic" ${publish} | sort`
+only_next_2=`git rev-list ^master           ${publish} | sort`
+if test "$only_next_1" = "$only_next_2"
+then
+	not_in_topic=`git rev-list "^$topic" master`
+	if test -z "$not_in_topic"
+	then
+		echo >&2 "$topic is already up-to-date with master"
+		exit 1 ;# we could allow it, but there is no point.
+	else
+		exit 0
+	fi
+else
+	not_in_next=`git rev-list --pretty=oneline ^${publish} "$topic"`
+	/usr/bin/perl -e '
+		my $topic = $ARGV[0];
+		my $msg = "* $topic has commits already merged to public branch:\n";
+		my (%not_in_next) = map {
+			/^([0-9a-f]+) /;
+			($1 => 1);
+		} split(/\n/, $ARGV[1]);
+		for my $elem (map {
+				/^([0-9a-f]+) (.*)$/;
+				[$1 => $2];
+			} split(/\n/, $ARGV[2])) {
+			if (!exists $not_in_next{$elem->[0]}) {
+				if ($msg) {
+					print STDERR $msg;
+					undef $msg;
+				}
+				print STDERR " $elem->[1]\n";
+			}
+		}
+	' "$topic" "$not_in_next" "$not_in_master"
+	exit 1
+fi
+
+<<\DOC_END
+
+This sample hook safeguards topic branches that have been
+published from being rewound.
+
+The workflow assumed here is:
+
+ * Once a topic branch forks from "master", "master" is never
+   merged into it again (either directly or indirectly).
+
+ * Once a topic branch is fully cooked and merged into "master",
+   it is deleted.  If you need to build on top of it to correct
+   earlier mistakes, a new topic branch is created by forking at
+   the tip of the "master".  This is not strictly necessary, but
+   it makes it easier to keep your history simple.
+
+ * Whenever you need to test or publish your changes to topic
+   branches, merge them into "next" branch.
+
+The script, being an example, hardcodes the publish branch name
+to be "next", but it is trivial to make it configurable via
+$GIT_DIR/config mechanism.
+
+With this workflow, you would want to know:
+
+(1) ... if a topic branch has ever been merged to "next".  Young
+    topic branches can have stupid mistakes you would rather
+    clean up before publishing, and things that have not been
+    merged into other branches can be easily rebased without
+    affecting other people.  But once it is published, you would
+    not want to rewind it.
+
+(2) ... if a topic branch has been fully merged to "master".
+    Then you can delete it.  More importantly, you should not
+    build on top of it -- other people may already want to
+    change things related to the topic as patches against your
+    "master", so if you need further changes, it is better to
+    fork the topic (perhaps with the same name) afresh from the
+    tip of "master".
+
+Let's look at this example:
+
+		   o---o---o---o---o---o---o---o---o---o "next"
+		  /       /           /           /
+		 /   a---a---b A     /           /
+		/   /               /           /
+	       /   /   c---c---c---c B         /
+	      /   /   /             \         /
+	     /   /   /   b---b C     \       /
+	    /   /   /   /             \     /
+    ---o---o---o---o---o---o---o---o---o---o---o "master"
+
+
+A, B and C are topic branches.
+
+ * A has one fix since it was merged up to "next".
+
+ * B has finished.  It has been fully merged up to "master" and "next",
+   and is ready to be deleted.
+
+ * C has not merged to "next" at all.
+
+We would want to allow C to be rebased, refuse A, and encourage
+B to be deleted.
+
+To compute (1):
+
+	git rev-list ^master ^topic next
+	git rev-list ^master        next
+
+	if these match, topic has not merged in next at all.
+
+To compute (2):
+
+	git rev-list master..topic
+
+	if this is empty, it is fully merged to "master".
+
+DOC_END