vagrant-notify 0.5.4 → 0.5.5

Sign up to get free protection for your applications and to get access to all the features.
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA1:
3
- metadata.gz: 1cc808b0736ce22d4855eafd7f920afa8d97834b
4
- data.tar.gz: 51a1e2b03a29dac79356b8169a13ae7ee0f28bae
3
+ metadata.gz: ce5183e2af2924f3e36012a0192cdc47e85cea86
4
+ data.tar.gz: e0687251ff6fe0c3f5910c7653de6974f8bfbf66
5
5
  SHA512:
6
- metadata.gz: 727b9a5fbe52de21b671fa23acec9a767f17b935daeb8f6bee6753ce0713bfee81a94f7d59840e6abdf05d8d7562b5cc4d606104bc87cb927ffe8262cf8ff031
7
- data.tar.gz: 3cdcf5e597f15b9e4502b5cba71eccde7accff59322963af74129e19e5a87cc0ec03af66f8b507544287a294bd66cb366ad0135c2eef83692b3debf94c160265
6
+ metadata.gz: f7fbaf96735f55579d4915037f2e202dac6b21fa0ba1ca7683884300c9c2930fbd05a1ea935ec46529aaa45f33b0cd60cd202bb8c3a1176b2e1beb4c754e053a
7
+ data.tar.gz: 2c936be449932589cd77d4af61f8fdafe80e831f4754cd33a11aaea5335813db8ee30687d8325da51c37fd757d4d2997f8edb109badbf35590081d2935ec7f82
data/CHANGELOG.md CHANGED
@@ -1,3 +1,12 @@
1
+ ## [0.5.5](https://github.com/fgrehm/vagrant-notify/compare/v0.5.4...v0.5.5) (May 13, 2017)
2
+ IMPROVEMENTS
3
+
4
+ - Support for Hyper-V and VMWare Workstation providers. [[GH-32]](https://github.com/fgrehm/vagrant-notify/issues/32) [[GH-33]](https://github.com/fgrehm/vagrant-notify/issues/33)
5
+ - Disable plugin for google, vultr, vcloudair, skytap, and scaleway cloud providers.
6
+
7
+ BUG FIXES
8
+ - Notifcation server suspend fix on VMWare Fusion.
9
+
1
10
  ## [0.5.4](https://github.com/fgrehm/vagrant-notify/compare/v0.5.3...v0.5.4) (May 4, 2017)
2
11
  IMPROVEMENTS
3
12
 
data/README.md CHANGED
@@ -44,7 +44,7 @@ Since Linux distributions have `notify-send` pre-installed, everything should wo
44
44
 
45
45
  Check out our OS X notify-send compatible [scripts](https://github.com/fgrehm/vagrant-notify/tree/master/examples#os-x).
46
46
 
47
- ### Windows (beta)
47
+ ### Windows
48
48
 
49
49
  Check out our Windows notify-send compatible [scripts](https://github.com/fgrehm/vagrant-notify/tree/master/examples#windows).
50
50
 
@@ -60,9 +60,9 @@ end
60
60
  ```
61
61
 
62
62
  _Please note that as of v0.5.1, the notification server will automatically be disabled for any of the following
63
- [cloud providers](lib/vagrant-notify/plugin.rb#L77-L79)._
63
+ [cloud providers](lib/vagrant-notify/plugin.rb#L81-L83)._
64
64
 
65
- By default, the notification server is binded to [local interfaces](lib/vagrant-notify/plugin.rb#L82-L86). For networking different than your provider's default network configuration, you can use the ***notify.bind\_ip*** configuration option to bind the notification server onto a different local ip address.
65
+ By default, the notification server is binded to [local interfaces](lib/vagrant-notify/plugin.rb#L86-L93). For networking different than your provider's default network configuration, you can use the ***notify.bind\_ip*** configuration option to bind the notification server onto a different local ip address.
66
66
 
67
67
  ```ruby
68
68
  Vagrant.configure(2) do |config|
@@ -81,9 +81,11 @@ vagrant-notify supports the following providers:
81
81
 
82
82
  - VirtualBox
83
83
  - Docker
84
+ - Hyper-V
84
85
  - [LXC](https://github.com/fgrehm/vagrant-lxc)
85
86
  - [Parallels](https://github.com/Parallels/vagrant-parallels)
86
87
  - [VMWare Fusion](https://www.vagrantup.com/vmware)
88
+ - [VMWare Workstation](https://www.vagrantup.com/vmware)
87
89
 
88
90
  vagrant-notify has been tested and known to work with Linux, Solaris 11, FreeBSD, OpenBSD, and NetBSD guests. (notify-send icon forwarding feature is not supported on BSD guests)
89
91
 
data/examples/README.md CHANGED
@@ -44,3 +44,9 @@ Compile using [PS1toEXE](https://github.com/aravindvcyber/PS1toEXE):
44
44
 
45
45
 
46
46
  * [Notification Center](https://github.com/fgrehm/vagrant-notify/blob/master/examples/windows/notification-center/notify-send.ps1)
47
+
48
+ ##### Hyper-V
49
+
50
+ Due to Hyper-V's [networking configuration limitation within Vagrant](https://www.vagrantup.com/docs/hyperv/limitations.html). You will most likely need to manually ***bind*** the vagrant-notify notification server to whatever gateway your virtual NAT switch is using. See https://github.com/fgrehm/vagrant-notify#configuration
51
+
52
+ [Default NATSwitch IP](https://github.com/fgrehm/vagrant-notify/blob/master/lib/vagrant-notify/plugin.rb#L84) used by vagrant-notify.
@@ -9,7 +9,7 @@ module Vagrant
9
9
  def call(env)
10
10
  begin
11
11
  unless env[:machine].config.notify.enable == false
12
- host_dir = Pathname("/tmp/vagrant-notify/#{env[:machine].id}")
12
+ host_dir = Pathname("/tmp/vagrant-notify/#{env[:machine].index_uuid}")
13
13
  FileUtils.mkdir_p host_dir.to_s unless host_dir.exist?
14
14
  env[:machine].config.vm.synced_folder host_dir, "/tmp/vagrant-notify", id: "vagrant-notify"
15
15
  end
@@ -48,9 +48,13 @@ module Vagrant
48
48
 
49
49
  # Third party provider plugins:
50
50
  if defined?(HashiCorp::VagrantVMwarefusion)
51
- require 'vagrant-parallels/action'
51
+ require 'vagrant-vmware-fusion/action'
52
52
  hook.before HashiCorp::VagrantVMwarefusion::Action::Suspend, Vagrant::Notify::Action.action_stop_server
53
53
  end
54
+ if defined?(HashiCorp::VagrantVMwareworkstation)
55
+ require 'vagrant-vmware-workstation/action'
56
+ hook.before HashiCorp::VagrantVMwareworkstation::Action::Suspend, Vagrant::Notify::Action.action_stop_server
57
+ end
54
58
  if defined?(VagrantPlugins::Parallels)
55
59
  require 'vagrant-parallels/action'
56
60
  hook.before VagrantPlugins::Parallels::Action::Suspend, Vagrant::Notify::Action.action_stop_server
@@ -76,13 +80,15 @@ module Vagrant
76
80
  # Keep an eye on https://github.com/mitchellh/vagrant/wiki/Available-Vagrant-Plugins#wiki-providers for more.
77
81
  CLOUD_PROVIDERS = %w( aws cloudstack digital_ocean hp joyent openstack rackspace
78
82
  softlayer proxmox managed azure brightbox cloudstack vcloud
79
- vsphere )
83
+ vsphere google vultr vcloudair skytap scaleway )
80
84
 
81
85
  # Supported providers and default IPs used to bind the notifcation server too.
82
86
  SUPPORTED_PROVIDERS = { :virtualbox => '127.0.0.1',
83
87
  :docker => '172.17.0.1',
88
+ :hyperv => '172.21.21.1',
84
89
  :lxc => '10.0.3.1',
85
90
  :parallels => '10.211.55.2',
86
- :vmware_fusion => '192.168.172.1'
91
+ :vmware_fusion => '192.168.172.1',
92
+ :vmware_workstation => '192.168.38.1'
87
93
  }
88
94
  end
@@ -1,5 +1,5 @@
1
1
  module Vagrant
2
2
  module Notify
3
- VERSION = "0.5.4"
3
+ VERSION = "0.5.5"
4
4
  end
5
5
  end
metadata CHANGED
@@ -1,7 +1,7 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: vagrant-notify
3
3
  version: !ruby/object:Gem::Version
4
- version: 0.5.4
4
+ version: 0.5.5
5
5
  platform: ruby
6
6
  authors:
7
7
  - Fabio Rehm
@@ -9,7 +9,7 @@ authors:
9
9
  autorequire:
10
10
  bindir: bin
11
11
  cert_chain: []
12
- date: 2017-05-04 00:00:00.000000000 Z
12
+ date: 2017-05-13 00:00:00.000000000 Z
13
13
  dependencies: []
14
14
  description: A Vagrant plugin that forwards `notify-send` from guest to host machine
15
15
  and notifies provisioning status