vagrant-hostmanager 1.8.1 → 1.8.2

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 01a7af3c6beb7ab58a6a947d15c748145e731f0b
-  data.tar.gz: 9280476ebe529451069972c6b7a7b5971ef7965f
+  metadata.gz: 20391c2e9ad7167864e2778e8cd81ce144558883
+  data.tar.gz: 49f58ab529f9a1b45302d0ea9a4ede21e5fff8d5
 SHA512:
-  metadata.gz: bf54aafe8e2b1e067a087c4915179e0029c214b237be0f56b74bc4fcc0bb82b3c9d76b628e4967efdfe3f2315e9f7962c25cc9a372808faa705e53f6b2a0762d
-  data.tar.gz: bad430453627d73031fcf3689c387154d72ecd27610348242347d4c925901ec05097fd0b7c9c00a754114c68f071c6da6dc77a7af284c840b2dad0756abf4701
+  metadata.gz: 5fb5405db5405e03aa33b4d6a1be3967a34714cd37c4832d5e7cf068f8eb0067e37431eb56de310f893429109c15d77b30b96a042dbcb6a9739047312b902ceb
+  data.tar.gz: 86ebee7b435cb91694049cf5de4781d151a5186a699962062a2fe842e50ae4df1154336bae678d2adb922c4dac226a5f5b483fe8c3ea84a98c1d70e75d51f8f3

data/README.md

@@ -4,24 +4,9 @@ Vagrant Host Manager
 [![Gem](https://img.shields.io/gem/v/vagrant-hostmanager.svg)](https://rubygems.org/gems/vagrant-hostmanager)
 [![Gem](https://img.shields.io/gem/dt/vagrant-hostmanager.svg)](https://rubygems.org/gems/vagrant-hostmanager)
 [![Gem](https://img.shields.io/gem/dtv/vagrant-hostmanager.svg)](https://rubygems.org/gems/vagrant-hostmanager)
-[![Twitter](https://img.shields.io/twitter/url/https/github.com/smdahlen/vagrant-hostmanager.svg?style=social)](https://twitter.com/intent/tweet?text=Check%20out%20this%20awesome%20Vagrant%20plugin%21&url=https%3A%2F%2Fgithub.com%2Fsmdahlen%2Fvagrant-hostmanager&hashtags=vagrant%hostmanager&original_referer=)
+[![Twitter](https://img.shields.io/twitter/url/https/github.com/devopsgroup-io/vagrant-hostmanager.svg?style=social)](https://twitter.com/intent/tweet?text=Check%20out%20this%20awesome%20Vagrant%20plugin%21&url=https%3A%2F%2Fgithub.com%devopsgroup-io%2Fvagrant-hostmanager&hashtags=vagrant%hostmanager&original_referer=)
 
-`vagrant-hostmanager` is a Vagrant 1.1+ plugin that manages the `/etc/hosts`
-file on guest machines (and optionally the host). Its goal is to enable
-resolution of multi-machine environments deployed with a cloud provider
-where IP addresses are not known in advance.
-
-*NOTE:* Version 1.1 of the plugin prematurely introduced a feature to hook into
-commands other than `vagrant up` and `vagrant destroy`. Version 1.1 broke support
-for some providers. Version 1.2 reverts this feature until a suitable implementation
-supporting all providers is available.
-
-***Potentially breaking change in v1.5.0:*** the running order on `vagrant up` has changed
-so that hostmanager runs before provisioning takes place.  This ensures all hostnames are 
-available to the guest when it is being provisioned 
-(see [#73](https://github.com/smdahlen/vagrant-hostmanager/issues/73)).
-Previously, hostmanager would run as the very last action.  If you depend on the old behavior, 
-see the [provisioner](#provisioner) section.
+`vagrant-hostmanager` is a plugin that manages the `/etc/hosts` file on guest machines (and optionally the host). Its goal is to enable resolution of multi-machine environments deployed with a cloud provider where IP addresses are not known in advance.
 
 Installation
 ------------
@@ -172,6 +157,31 @@ Due to limitations caused by UAC, cancelling out of the UAC prompt will not caus
 visible errors, however the ```hosts``` file will not be updated.
 
 
+Compatibility
+-------------
+This Vagrant plugin has been tested with the following technology.
+
+Date Tested | Vagrant Version | vagrant-hostmanager Version | Host (Workstation) Operating System | Guest (DigitalOcean) Operating System
+------------|-----------------|-----------------------------|-------------------------------------|--------------------------------------
+03/23/2016  | 1.8.1           | 1.8.1                       | Ubuntu 14.04 LTS                    | CentOS 7.2
+03/22/2016  | 1.8.1           | 1.8.1                       | OS X 10.11.4                        | CentOS 7.2
+
+
+Troubleshooting
+-------------
+* Version 1.1 of the plugin prematurely introduced a feature to hook into
+commands other than `vagrant up` and `vagrant destroy`. Version 1.1 broke support
+for some providers. Version 1.2 reverts this feature until a suitable implementation
+supporting all providers is available.
+
+* Potentially breaking change in v1.5.0: the running order on `vagrant up` has changed
+so that hostmanager runs before provisioning takes place.  This ensures all hostnames are 
+available to the guest when it is being provisioned 
+(see [#73](https://github.com/devopsgroup-io/vagrant-hostmanager/issues/73)).
+Previously, hostmanager would run as the very last action.  If you depend on the old behavior, 
+see the [provisioner](#provisioner) section.
+
+
 Contribute
 ----------
 To contribute, fork then clone the repository, and then the following:
@@ -205,7 +215,7 @@ To release a new version of vagrant-hostmanager you will need to do the followin
     * Follow [Semantic Versioning](http://semver.org/).
 2. Then, create a matching GitHub Release (this will also create a tag):
     * Preface the version number with a `v`.
-    * https://github.com/smdahlen/vagrant-hostmanager/releases
+    * https://github.com/devopsgroup-io/vagrant-hostmanager/releases
 3. You will then need to build and push the new gem to RubyGems:
     * `rake gem:build`
     * `gem push pkg/vagrant-hostmanager-1.6.1.gem`

data/lib/vagrant-hostmanager/hosts_file/updater.rb

@@ -10,6 +10,8 @@ module VagrantPlugins
           @global_env = global_env
           @config = Util.get_config(@global_env)
           @provider = provider
+          @logger = Log4r::Logger.new('vagrant::hostmanager::updater')
+          @logger.debug("init updater")
         end
 
         def update_guest(machine)
@@ -29,10 +31,14 @@ module VagrantPlugins
           # download and modify file with Vagrant-managed entries
           file = @global_env.tmp_path.join("hosts.#{machine.name}")
           machine.communicate.download(realhostfile, file)
+
+          @logger.debug("file is: #{file.to_s}")
+          @logger.debug("class of file is: #{file.class}")
+
           if update_file(file, machine, false)
 
             # upload modified file and remove temporary file
-            machine.communicate.upload(file, '/tmp/hosts')
+            machine.communicate.upload(file.to_s, '/tmp/hosts')
             if windir
               machine.communicate.sudo("mv -force /tmp/hosts/hosts.#{machine.name} #{realhostfile}")
             else
@@ -56,7 +62,7 @@ module VagrantPlugins
             copy_proc = Proc.new { windows_copy_file(file, hosts_location) }
           else
             hosts_location = '/etc/hosts'
-            copy_proc = Proc.new { `sudo cp #{file} #{hosts_location}` }
+            copy_proc = Proc.new { `[ -w #{hosts_location} ] && cat #{file} > #{hosts_location} || sudo cp #{file} #{hosts_location}` }
           end
 
           FileUtils.cp(hosts_location, file)

data/lib/vagrant-hostmanager/version.rb

@@ -1,5 +1,5 @@
 module VagrantPlugins
   module HostManager
-    VERSION = '1.8.1'
+    VERSION = '1.8.2'
   end
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: vagrant-hostmanager
 version: !ruby/object:Gem::Version
-  version: 1.8.1
+  version: 1.8.2
 platform: ruby
 authors:
 - Shawn Dahlen
@@ -9,7 +9,7 @@ authors:
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2016-02-11 00:00:00.000000000 Z
+date: 2016-06-17 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: bundler
@@ -91,7 +91,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
       version: '0'
 requirements: []
 rubyforge_project: 
-rubygems_version: 2.4.6
+rubygems_version: 2.4.5
 signing_key: 
 specification_version: 4
 summary: A Vagrant plugin that manages the /etc/hosts file within a multi-machine