vagrant-norequiretty 0.0.2 → 0.0.3

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 38f0ef4f13060fcbaa6fe92d181463695c003f32
-  data.tar.gz: 8d31c3986baa3f8fb92106c94b402b9b54e64a70
+  metadata.gz: 69d5478c850807408b38d24a8fa60b91c001f277
+  data.tar.gz: cd68e552dc9cc2ebd2bd2f0b57e4384675772451
 SHA512:
-  metadata.gz: 29e8ca5232e89325ee63c797262c9e103c4e06ae2cc565d53f295e7605e8fefc77b26cc3be5145f5827e18a1d5a3a6720841067ad33dd9116c0d0e6b90ee186c
-  data.tar.gz: b46c3b4e12a52587e26e74e5a302bcd20e5d69a58d817608c691f539dafe370c730ff91132deaa73d33f2dfd8d62b0ea1ed50b5ea43cc25323515c560daff234
+  metadata.gz: 474d10f1a07c90ea01bd4de8d4d921c4d94f36e33b5d2ab48a23bf966c25e04eac8cea38471a2de9213b8018692063d263edd164025bc33af9354e1ebe0d8d68
+  data.tar.gz: 731e6969d7c7d922db8b6f10c649a9daa1432b0b0fec29dcaffd244217b69b3c5cb1bb06d24bce6b48648107f918f0cb1468fa2286a9d1ea11e2a7ba4e16a5dd

data/CHANGELOG

@@ -1,6 +1,17 @@
 CHANGELOG
 =========
 
+0.0.3
+-----
+
+2016-04-06
+
+This is a backwards compatible feature release.
+
+  * (GH-2) Add support for vagrant-openstack-provider and
+    vagrant-openstack-plugin.
+
+
 0.0.2
 -----
 

data/README.markdown

@@ -45,8 +45,9 @@ clear. For many cases,
 >
 > I see no pros.  Do you?
 
-This Vagrant plugin hooks into startup actions for VirtualBox, vSphere and
-VMware Desktop providers and runs a `sed` command to purge the `requiretty`
-setting before provisioners, synced folders and networking actions are executed.
+This Vagrant plugin hooks into startup actions for VirtualBox, vSphere, VMware
+Desktop, and OpenStack providers by running a `sed` command to purge the
+`requiretty` setting from `/etc/sudoers` before provisioners, synced folders
+and networking actions are executed.
 
 Support for additional providers coming soon.

data/lib/vagrant-norequiretty/action.rb

@@ -26,7 +26,11 @@ module VagrantNoRequireTTY
     end
 
     def supports_requiretty?(machine)
-      machine.communicate.ready? && machine.guest.capability?(:norequiretty)
+      # Some versions of the OpenStack provider crash if
+      # machine.communicate.ready? is called before the machine is created.
+      (machine.state.id != :not_created) &&
+      machine.communicate.ready? &&
+      machine.guest.capability?(:norequiretty)
     rescue Vagrant::Errors::VagrantError
       # WinRM will raise an error if the VM isn't running instead of
       # returning false.

data/lib/vagrant-norequiretty/plugin.rb

@@ -16,6 +16,9 @@ class VagrantNoRequireTTY::Plugin < Vagrant.plugin(2)
 
     # For RSync.
     hook.after(Vagrant::Action::Builtin::SyncedFolders, action)
+    if defined? VagrantPlugins::Openstack::Action::SyncFolders
+      hook.after(VagrantPlugins::Openstack::Action::SyncFolders, action)
+    end
   end
 
   # For everything else.

data/lib/vagrant-norequiretty/version.rb

@@ -1,3 +1,3 @@
 module VagrantNoRequireTTY
-  VERSION = '0.0.2'
+  VERSION = '0.0.3'
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: vagrant-norequiretty
 version: !ruby/object:Gem::Version
-  version: 0.0.2
+  version: 0.0.3
 platform: ruby
 authors:
 - Charlie Sharpsteen
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2016-04-03 00:00:00.000000000 Z
+date: 2016-04-07 00:00:00.000000000 Z
 dependencies: []
 description: |
   Ever get a "sorry, you must have a tty to run sudo" error? Maybe