vagrant-registration 1.3.2 → 1.3.3

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 7e6fbd467ace0a36ad6a8ed998000cd0c636519b320664c7ab33d5bc2c6fc9bc
-  data.tar.gz: 86eb123fdd8e92205ee2e39e265b4cae3b0db1ad9d655ed18d2e606d075d3c01
+  metadata.gz: 4ee8b2a17b88c5522eab39cbb431b498ae16fad453cfa16245f90a8951cd7190
+  data.tar.gz: 26f32e4322d3ef312bda7700fcd3a6056119aebc8414ce8a79f3ebb1f88b7dd9
 SHA512:
-  metadata.gz: 88295a8a884ba2d1da7b1912b9900d01328557f77b12ae1970d7fe12c06a3f34d7e0499c29d83b4ba1fd6b29472225378bbd8079fee6a8447ad24b9b15d7191e
-  data.tar.gz: 1014dd664621d43ea0d8c95aaaeddfa6066eb219bae4f47b8d5f0b23fc3c4c93755b2c21118c714f1e4b22bc15c87b1c42af2f4ab36aff61ab6411584ad72a2a
+  metadata.gz: 649c9c60d3db370b14be048ea35a3e49881cd1f1912e24f9563aa41256a082c296984f03f8dc4f2b1ce8313f4a987cd826fd3802cc7255d0e1adfd95ebb452b6
+  data.tar.gz: 97ef3fa04ba7310a4265ca3a2fb1a0cbf5556a8ca8e464060cf91a8d932735ae9802772e76043e241d1700a8ef02784c2c915ded39f9748ddcfce18b50464ce4

data/README.adoc

@@ -398,12 +398,11 @@ option to `false`:
 
 == Development
 
-The use of https://rvm.io[RVM] is recommended. Verified to work with
-ruby 2.0.0p648.
+The use of https://rvm.io[RVM] is recommended. Verified to work with ruby-2.2.10.
 
 ....
-rvm install 2.0
-rvm use 2.0
+rvm install 2.2
+rvm use 2.2
 ....
 
 To install a development environment, clone the repo and prepare
@@ -475,10 +474,10 @@ To release a new version of vagrant-registration you will need to do the followi
     * 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/devopsgroup-io/vagrant-hostmanager/releases
+    * https://github.com/projectatomic/adb-vagrant-registration/releases
 3. You will then need to build and push the new gem to RubyGems:
-    * `rake gem:build`
-    * `gem push pkg/vagrant-registration-1.6.1.gem`
+    * `rake build`
+    * `gem push pkg/vagrant-registration-1.3.2.gem`
 4. Then, when John Doe runs the following, they will receive the updated vagrant-registration plugin:
     * `vagrant plugin update`
     * `vagrant plugin update vagrant-registration`

data/lib/vagrant-registration/version.rb

@@ -1,6 +1,6 @@
 module VagrantPlugins
   # Registration plugin to auto-register guests on `vagrant up`
   module Registration
-    VERSION = '1.3.2'
+    VERSION = '1.3.3'
   end
 end

data/plugins/guests/redhat/cap/subscription_manager.rb

@@ -4,9 +4,9 @@ module VagrantPlugins
       class SubscriptionManager
         # Test that the machine is already registered
         def self.subscription_manager_registered?(machine)
-          false if machine.communicate.sudo("/usr/sbin/subscription-manager list --consumed | grep 'No consumed subscription pools to list'")
+          true if machine.communicate.sudo("/usr/sbin/subscription-manager list --consumed --pool-only | grep -E '^[a-f0-9]{32}$'")
         rescue
-          true
+          false
         end
 
         # Test that we have subscription-manager installed

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: vagrant-registration
 version: !ruby/object:Gem::Version
-  version: 1.3.2
+  version: 1.3.3
 platform: ruby
 authors:
 - Langdon White
@@ -10,7 +10,7 @@ authors:
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2019-12-17 00:00:00.000000000 Z
+date: 2020-03-20 00:00:00.000000000 Z
 dependencies: []
 description: Enables guests to be registered automatically which is especially useful
   for RHEL or SLES guests.
@@ -60,7 +60,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
     - !ruby/object:Gem::Version
       version: 1.3.6
 requirements: []
-rubygems_version: 3.0.4
+rubygems_version: 3.0.6
 signing_key: 
 specification_version: 4
 summary: Automatic guest registration for Vagrant