vagrant-registration 1.3.0 → 1.3.1

Sign up to get free protection for your applications and to get access to all the features.
Files changed (10) hide show
  1. checksums.yaml +4 -4
  2. data/CHANGELOG.adoc +86 -0
  3. data/{LICENSE.md → LICENSE} +0 -0
  4. data/{README.md → README.adoc} +211 -153
  5. data/lib/vagrant-registration/action/register.rb +1 -1
  6. data/lib/vagrant-registration/version.rb +1 -1
  7. data/plugins/guests/redhat/cap/rhn_register.rb +1 -1
  8. data/vagrant-registration.gemspec +1 -1
  9. metadata +5 -5
  10. data/CHANGELOG.md +0 -60
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA1:
3
- metadata.gz: 30c4aa8836dba26f3cc2bd37286f4553f0811677
4
- data.tar.gz: 5137ad1f5fee66e21228b4e8be7e8c186aa36076
3
+ metadata.gz: 0ae2e0898314193ed99a22e72128de917787b784
4
+ data.tar.gz: d0d5cd83e7737ad76f734e6252a4fcabebcb12d0
5
5
  SHA512:
6
- metadata.gz: fc371bfb460697d54d35ae498ddf36e50a1483d8cc6544aaa2c7e54a93c113458f67e6c9ba528b5cb9454b7b2ff39d78ca64ad1428a9e52a01cfe187d70f2c26
7
- data.tar.gz: f35f25302ca53fd14c75503b7c4e4bfe4bc70368065ab5eeafcd766e4d3971cdb0b5d5a6887c90c6efc68f25bcc1e7637706309b3cd537c25125b2431c18e6bf
6
+ metadata.gz: 270afc4dbab6b7c41a2ef3b2054378144c5400da875f4ad0549983da9bee28cb4e78dfb751ae6dc2676dcfc09ebdd25688811e2cbb88751d4ec70b097303baac
7
+ data.tar.gz: 1eff5fb09ab17cda82aab2cd42c3c65ef057fd59288659a076c402ede8d71f7bfc619f119ca83db73112e3e4bbf19936b2dfc26653d34178689c04188088fb81
data/CHANGELOG.adoc ADDED
@@ -0,0 +1,86 @@
1
+ = Revision History
2
+ :toc:
3
+
4
+ [[section]]
5
+ == 1.3.1
6
+
7
+ * Fix #111 Default response (yes) for registration prompt not working
8
+ * Fixing rhn_register upload certificate fail #114
9
+ * Converted docs from markdown to asciidoc and format tweaks
10
+ * Fix #117 Updating gemspec file after doc format changes to adoc
11
+
12
+ [[section-1]]
13
+ == 1.3.0
14
+
15
+ * Fixed formatting, typo, grammar in README
16
+ * Added MAINTAINERS file
17
+ * Fix #44 allow more than one try to fill username and password
18
+ * Fixes #99 using proxy info to unregister
19
+ * Fix #107 register when passing credentials as env variables
20
+
21
+ [[section-2]]
22
+ == 1.2.3
23
+
24
+ * Issue #90 Use locale based messaging
25
+ * Issue #65 Adding cucumber tests for proxy settings
26
+ * Issue #65 Adding proxy options to rhn_register and
27
+ subscription_manager
28
+ * Adding minitest as unit test framework and setting up basic test
29
+ harness for Vagrant plugins
30
+ * Issue #65 Removing obsolete bash tests
31
+
32
+ [[section-3]]
33
+ == 1.2.2
34
+
35
+ * Introducing Cucumber based acceptance tests.
36
+ * Fix: Handling of vagrant-registration action hooks depending on
37
+ provider used.
38
+
39
+ [[section-4]]
40
+ == 1.2.1
41
+
42
+ * Fix regression: Use sudo when asking on registration managers being
43
+ present
44
+
45
+ [[section-5]]
46
+ == 1.2.0
47
+
48
+ * Fix: `vagrant destroy` not triggering subscription deactivation and
49
+ removal, issue #57
50
+ * Fix: Allow auto-attach and force options to be configured
51
+ * Fix: Remove unnecessary shebang from python script
52
+ * Support for attaching to specified subscription pool(s), issue #36
53
+ * Fix: rhn_register upload certificate fails, issue #60
54
+
55
+ [[section-6]]
56
+ == 1.1.0
57
+
58
+ * Print warning if specifically selected manager is not available
59
+ * Support running alongside vagrant-vbguest, issue #40
60
+ * Support rhn_register manager
61
+ * Fix: Handle various types of configuration option values, issue #48
62
+ * Fix: Hide password on registration failure, issue #47
63
+
64
+ [[section-7]]
65
+ == 1.0.1
66
+
67
+ * Fix: Set repo_ca_cert option in /etc/rhsm/rhsm.conf after uploading a
68
+ certificate
69
+
70
+ [[section-8]]
71
+ == 1.0.0
72
+
73
+ * Support providing a CA certificate via `config.registration.ca_cert`
74
+ option
75
+ * Issue warnings on unsupported configuration options
76
+ * Do not ship tests
77
+
78
+ [[section-9]]
79
+ == 0.0.19
80
+
81
+ * Remove extra files from installation
82
+
83
+ [[section-20]]
84
+ == 0.0.18
85
+
86
+ * Support `config.registration.unregister_on_halt` option
data/{LICENSE.md → LICENSE} RENAMED
File without changes
data/{README.md → README.adoc} RENAMED
@@ -1,87 +1,96 @@
1
- # vagrant-registration
1
+ [[vagrant-registration]]
2
+ = vagrant-registration
3
+ :toc:
4
+ :toc-placement!:
2
5
 
3
- <!-- MarkdownTOC -->
6
+ The vagrant-registration plugin for Vagrant allows developers to easily
7
+ register their guests for updates on systems with a subscription model
8
+ (like Red Hat Enterprise Linux).
4
9
 
5
- - [Installation](#installation)
6
- - [Usage](#usage)
7
- - [General Configuration](#general-configuration)
8
- - [Credential Configuration](#credential-configuration)
9
- - [HTTP Proxy Configuration](#http-proxy-configuration)
10
- - [subscription-manager Configuration](#subscription-manager-configuration)
11
- - [subscription-manager Default Options](#subscription-manager-default-options)
12
- - [subscription-manager Options Reference](#subscription-manager-options-reference)
13
- - [rhn-register Configuration](#rhn-register-configuration)
14
- - [rhn-register Default Options](#rhn-register-default-options)
15
- - [rhn-register Options Reference](#rhn-register-options-reference)
16
- - [Development](#development)
17
- - [Tests](#tests)
18
- - [Minitest](#minitest)
19
- - [Acceptance tests](#acceptance-tests)
20
- - [Acknowledgements](#acknowledgements)
10
+ This plugin would run _register_ action on `vagrant up` before any
11
+ provisioning and _unregister_ on `vagrant halt` or `vagrant destroy`.
12
+ The actions then call the registration capabilities that have to be
13
+ provided for the given OS.
21
14
 
22
- <!-- /MarkdownTOC -->
15
+ '''
16
+ toc::[]
17
+ '''
23
18
 
24
- The vagrant-registration plugin for Vagrant allows developers to easily register their guests for updates on systems with a subscription model (like Red Hat Enterprise Linux).
25
-
26
- This plugin would run *register* action on `vagrant up` before any provisioning and *unregister* on `vagrant halt` or `vagrant destroy`. The actions then call the registration capabilities that have to be provided for the given OS.
27
-
28
- <a name="installation"></a>
29
- ## Installation
19
+ == Installation
30
20
 
31
21
  Install vagrant-registration as any other Vagrant plugin:
32
22
 
33
- ```shell
23
+ [source,shell]
24
+ ----
34
25
  $ vagrant plugin install vagrant-registration
35
- ```
26
+ ----
36
27
 
37
- If you are on Fedora, you can install the packaged version of the plugin by running:
28
+ If you are on Fedora, you can install the packaged version of the plugin
29
+ by running:
38
30
 
39
- ```shell
31
+ [source,shell]
32
+ ----
40
33
  # dnf install vagrant-registration
41
- ```
34
+ ----
42
35
 
43
- <a name="usage"></a>
44
- ## Usage
36
+ == Usage
45
37
 
46
- The plugin is designed in a registration-manager agnostic way, which means, that the plugin itself, depends neither on any OS nor on the way of registration. The vagrant-registration plugin only calls registration capabilities for the given guest, passes the configuration options to them and handles interactive registration.
38
+ The plugin is designed in a registration-manager agnostic way, which
39
+ means, that the plugin itself, depends neither on any OS nor on the way
40
+ of registration. The vagrant-registration plugin only calls registration
41
+ capabilities for the given guest, passes the configuration options to
42
+ them and handles interactive registration.
47
43
 
48
- That being said, this plugin currently ships only with registration capability files for RHEL's Subscription Manager and `rhn_register`. Feel free to submit others.
44
+ That being said, this plugin currently ships only with registration
45
+ capability files for RHEL's Subscription Manager and `rhn_register`.
46
+ Feel free to submit others.
49
47
 
50
- To configure the plugin, always include the configuration options mentioned in this file within the following configuration block in your Vagrantfile.
48
+ To configure the plugin, always include the configuration options
49
+ mentioned in this file within the following configuration block in your
50
+ Vagrantfile.
51
51
 
52
- ```
52
+ ....
53
53
  Vagrant.configure('2') do |config|
54
54
  ...
55
55
  end
56
- ```
56
+ ....
57
57
 
58
- <a name="general-configuration"></a>
59
- ### General Configuration
58
+ === General Configuration
60
59
 
61
- - **skip** skips the registration. If you wish to skip the registration process altogether, you can do so by setting a `skip` option to `true`:
60
+ * *skip* skips the registration. If you wish to skip the registration
61
+ process altogether, you can do so by setting a `skip` option to `true`:
62
62
 
63
- ```ruby
63
+ [source,ruby]
64
+ ----
64
65
  config.registration.skip = true
65
- ```
66
+ ----
66
67
 
67
- - **unregister_on_halt** disables or enables automatic unregistration on halt (on shut down). By default the plugin unregisters on halt, you can however change that by setting the option to `false` so that the box will unregister only on destroy:
68
+ * *unregister_on_halt* disables or enables automatic unregistration on
69
+ halt (on shut down). By default the plugin unregisters on halt, you can
70
+ however change that by setting the option to `false` so that the box
71
+ will unregister only on destroy:
68
72
 
69
- ```ruby
73
+ [source,ruby]
74
+ ----
70
75
  config.registration.unregister_on_halt = false
71
- ```
76
+ ----
72
77
 
73
- - **manager** selects the registration manager provider. By default the plugin will use the `subscription_manager` as the registration manager provider. You can however, change that by setting the option to a different manager:
78
+ * *manager* selects the registration manager provider. By default the
79
+ plugin will use the `subscription_manager` as the registration manager
80
+ provider. You can however, change that by setting the option to a
81
+ different manager:
74
82
 
75
- ```ruby
83
+ [source,ruby]
84
+ ----
76
85
  config.registration.manager = 'subscription_manager'
77
- ```
86
+ ----
78
87
 
79
- <a name="credential-configuration"></a>
80
- ### Credential Configuration
88
+ === Credential Configuration
81
89
 
82
90
  You can set up the credentials as follows:
83
91
 
84
- ```ruby
92
+ [source,ruby]
93
+ ----
85
94
  Vagrant.configure('2') do |config|
86
95
  ...
87
96
  if Vagrant.has_plugin?('vagrant-registration')
@@ -96,35 +105,40 @@ Vagrant.configure('2') do |config|
96
105
  end
97
106
  ...
98
107
  end
99
- ```
108
+ ----
100
109
 
101
- This should go, preferably, into the Vagrantfile in your Vagrant home directory
102
- (defaults to ~/.vagrant.d), to make it available for every project. It can be
103
- later overridden in an individual project's Vagrantfile if needed.
110
+ This should go, preferably, into the Vagrantfile in your Vagrant home
111
+ directory (defaults to ~/.vagrant.d), to make it available for every
112
+ project. It can be later overridden in an individual project's
113
+ Vagrantfile if needed.
104
114
 
105
- If you prefer not to store your username and/or password on your filesystem,
106
- you can optionally configure vagrant-registration plugin to use environment
107
- variables such as:
115
+ If you prefer not to store your username and/or password on your
116
+ filesystem, you can optionally configure vagrant-registration plugin to
117
+ use environment variables such as:
108
118
 
109
- ```ruby
119
+ [source,ruby]
120
+ ----
110
121
  Vagrant.configure('2') do |config|
111
122
  ...
112
123
  config.registration.username = ENV['SUB_USERNAME']
113
124
  config.registration.password = ENV['SUB_PASSWORD']
114
125
  ...
115
126
  end
116
- ```
127
+ ----
117
128
 
118
- If you do not configure your credentials as outlined above, you will receive a maximum of 3 prompts for them during the `vagrant up` process.
129
+ If you do not configure your credentials as outlined above, you will
130
+ receive a maximum of 3 prompts for them during the `vagrant up` process.
119
131
 
120
- Please note that the interactive mode asks you for the preferred registration pair only for the configured manager.
132
+ Please note that the interactive mode asks you for the preferred
133
+ registration pair only for the configured manager.
121
134
 
122
- <a name="http-proxy-configuration"></a>
123
- ### HTTP Proxy Configuration
135
+ === HTTP Proxy Configuration
124
136
 
125
- HTTP Proxy can be configured via the _proxy_, _proxyUser_ and _proxyPassword_ configuration options:
137
+ HTTP Proxy can be configured via the __proxy__, _proxyUser_ and
138
+ _proxyPassword_ configuration options:
126
139
 
127
- ```ruby
140
+ [source,ruby]
141
+ ----
128
142
  Vagrant.configure('2') do |config|
129
143
  ...
130
144
  if Vagrant.has_plugin?('vagrant-registration')
@@ -134,18 +148,21 @@ Vagrant.configure('2') do |config|
134
148
  end
135
149
  ...
136
150
  end
137
- ```
151
+ ----
138
152
 
139
- As described in the [credentials configuration](#credentials-configuration) section, these settings
140
- can be placed either into the Vagrantfile in the Vagrant home directory or provided as
141
- environment variables.
153
+ As described in the link:#credentials-configuration[credentials
154
+ configuration] section, these settings can be placed either into the
155
+ Vagrantfile in the Vagrant home directory or provided as environment
156
+ variables.
142
157
 
143
- <a name="subscription-manager-configuration"></a>
144
- ### subscription-manager Configuration
158
+ === subscription-manager Configuration
145
159
 
146
- The vagrant-registration plugin uses `subscription_manager` as the default manager. This can also be explicitly configured by setting the `manager` option to `subscription_manager`:
160
+ The vagrant-registration plugin uses `subscription_manager` as the
161
+ default manager. This can also be explicitly configured by setting the
162
+ `manager` option to `subscription_manager`:
147
163
 
148
- ```ruby
164
+ [source,ruby]
165
+ ----
149
166
  Vagrant.configure('2') do |config|
150
167
  ...
151
168
  if Vagrant.has_plugin?('vagrant-registration')
@@ -153,38 +170,48 @@ Vagrant.configure('2') do |config|
153
170
  end
154
171
  ...
155
172
  end
156
- ```
173
+ ----
157
174
 
158
- In case you choose `subscription_manager` as the manager, you would be asked for your user credentials, such as the username and password.
175
+ In case you choose `subscription_manager` as the manager, you would be
176
+ asked for your user credentials, such as the username and password.
159
177
 
160
- The vagrant-registration plugin supports all the options for the subscription-manager's register command.
161
- You can set any option easily by setting `config.registration.OPTION_NAME = 'OPTION_VALUE'`
162
- in your Vagrantfile (please see the subscription-manager's documentation for option
163
- description).
178
+ The vagrant-registration plugin supports all the options for the
179
+ subscription-manager's register command. You can set any option easily
180
+ by setting `config.registration.OPTION_NAME = 'OPTION_VALUE'` in your
181
+ Vagrantfile (please see the subscription-manager's documentation for
182
+ option description).
164
183
 
165
- <a name="subscription-manager-default-options"></a>
166
- #### subscription-manager Default Options
184
+ ==== subscription-manager Default Options
167
185
 
168
- - **--force**: Subscription Manager will fail if you attempt to register an already registered machine (see the man page for explanation), therefore vagrant-registration appends the `--force` flag automatically when subscribing. If you would like to disable this feature, set `force` option to `false`:
186
+ * **--force**: Subscription Manager will fail if you attempt to register
187
+ an already registered machine (see the man page for explanation),
188
+ therefore vagrant-registration appends the `--force` flag automatically
189
+ when subscribing. If you would like to disable this feature, set `force`
190
+ option to `false`:
169
191
 
170
- ```ruby
192
+ [source,ruby]
193
+ ----
171
194
  config.registration.force = false
172
- ```
195
+ ----
173
196
 
174
- - **--auto-attach**: Vagrant would fail to install packages on registered RHEL system if the subscription is not attached, therefore vagrant-registration appends the
175
- `--auto-attach` flag automatically when subscribing. To disable this option, set `auto_attach` option to `false`:
197
+ * **--auto-attach**: Vagrant would fail to install packages on
198
+ registered RHEL system if the subscription is not attached, therefore
199
+ vagrant-registration appends the `--auto-attach` flag automatically when
200
+ subscribing. To disable this option, set `auto_attach` option to
201
+ `false`:
176
202
 
177
- ```ruby
203
+ [source,ruby]
204
+ ----
178
205
  config.registration.auto_attach = false
179
- ```
206
+ ----
180
207
 
181
- Note that the `auto_attach` option is set to false when using org/activationkey for registration
182
- or if pools are specified.
208
+ Note that the `auto_attach` option is set to false when using
209
+ org/activationkey for registration or if pools are specified.
183
210
 
184
- <a name="subscription-manager-options-reference"></a>
185
- #### subscription-manager Options Reference
211
+ ==== subscription-manager Options Reference
186
212
 
187
- ```ruby
213
+ [source,ruby]
214
+ ----
188
215
  # The username to subscribe with (required)
189
216
  config.registration.username
190
217
 
@@ -251,14 +278,15 @@ or if pools are specified.
251
278
  # Example:
252
279
  # config.registration.pools = [ 'POOL-ID-1', 'POOL-ID-2' ]
253
280
  config.registration.pools
254
- ```
281
+ ----
255
282
 
256
- <a name="rhn-register-configuration"></a>
257
- ### rhn-register Configuration
283
+ === rhn-register Configuration
258
284
 
259
- vagrant-registration will use the `rhn_register` manager only if explicitly configured by setting the `manager` option to `rhn_register`:
285
+ vagrant-registration will use the `rhn_register` manager only if
286
+ explicitly configured by setting the `manager` option to `rhn_register`:
260
287
 
261
- ```ruby
288
+ [source,ruby]
289
+ ----
262
290
  Vagrant.configure('2') do |config|
263
291
  ...
264
292
  if Vagrant.has_plugin?('vagrant-registration')
@@ -266,27 +294,36 @@ Vagrant.configure('2') do |config|
266
294
  end
267
295
  ...
268
296
  end
269
- ```
297
+ ----
270
298
 
271
- In case of a `rhn_register` manager, the preferred registration pair is the username/password/serverurl combination.
299
+ In case of a `rhn_register` manager, the preferred registration pair is
300
+ the username/password/serverurl combination.
272
301
 
273
- vagrant-registration supports most of the options of rhnreg_ks's command. You can set any option easily by setting `config.registration.OPTION_NAME = 'OPTION_VALUE'` in your Vagrantfile (please see the `rhnreg_ks`'s documentation for option description).
302
+ vagrant-registration supports most of the options of rhnreg_ks's
303
+ command. You can set any option easily by setting
304
+ `config.registration.OPTION_NAME = 'OPTION_VALUE'` in your Vagrantfile
305
+ (please see the `rhnreg_ks`'s documentation for option description).
274
306
 
275
- `rhn_register` manager reuses the naming of `subscription-manager`'s command options where possible.
307
+ `rhn_register` manager reuses the naming of `subscription-manager`'s
308
+ command options where possible.
276
309
 
277
- <a name="rhn-register-default-options"></a>
278
- #### rhn-register Default Options
310
+ ==== rhn-register Default Options
279
311
 
280
- - **--force**: `rhnreg_ks` command will fail if you attempt to register an already registered machine (see the man page for explanation), therefore vagrant-registration appends the `--force` flag automatically when subscribing. If you would like to disable this feature, set `force` option to `false`:
312
+ * **--force**: `rhnreg_ks` command will fail if you attempt to register
313
+ an already registered machine (see the man page for explanation),
314
+ therefore vagrant-registration appends the `--force` flag automatically
315
+ when subscribing. If you would like to disable this feature, set `force`
316
+ option to `false`:
281
317
 
282
- ```ruby
318
+ [source,ruby]
319
+ ----
283
320
  config.registration.force = false
284
- ```
321
+ ----
285
322
 
286
- <a name="rhn-register-options-reference"></a>
287
- #### rhn-register Options Reference
323
+ ==== rhn-register Options Reference
288
324
 
289
- ```ruby
325
+ [source,ruby]
326
+ ----
290
327
  # The username to register the system with under Spacewalk Server, Red Hat Satellite or
291
328
  # Red Hat Network Classic. This can be an existing Spacewalk, Red Hat Satellite or
292
329
  # Red Hat Network Classic username, or a new user‐name.
@@ -357,61 +394,82 @@ vagrant-registration supports most of the options of rhnreg_ks's command. You ca
357
394
 
358
395
  # Specify a password to use with an authenticated HTTP proxy
359
396
  config.registration.proxyPassword
360
- ```
397
+ ----
361
398
 
362
- <a name="development"></a>
363
- ## Development
399
+ == Development
364
400
 
365
- To install a development environment, clone the repo and prepare dependencies by:
401
+ To install a development environment, clone the repo and prepare
402
+ dependencies by:
366
403
 
367
- ```
404
+ ....
368
405
  gem install bundler
369
406
  bundler install
370
- ```
407
+ ....
371
408
 
372
- The use of [RVM](https://rvm.io) is recommended. Verified to work with ruby 2.0.0p643.
409
+ The use of https://rvm.io[RVM] is recommended. Verified to work with
410
+ ruby 2.0.0p643.
373
411
 
374
- <a name="tests"></a>
375
- ### Tests
412
+ === Tests
376
413
 
377
- <a name="minitest"></a>
378
- #### Minitest
414
+ ==== Minitest
379
415
 
380
- The source contains a set of [Minitest](http://ruby-doc.org/stdlib-2.0.0/libdoc/minitest/rdoc/MiniTest.html)
416
+ The source contains a set of
417
+ http://ruby-doc.org/stdlib-2.0.0/libdoc/minitest/rdoc/MiniTest.html[Minitest]
381
418
  based unit tests. They can be run via:
382
419
 
383
- $ bundle exec rake test
420
+ ....
421
+ $ bundle exec rake test
422
+ ....
384
423
 
385
- <a name="acceptance-tests"></a>
386
- #### Acceptance tests
424
+ ==== Acceptance tests
387
425
 
388
- The source also contains a set of [Cucumber](https://cucumber.io/) based acceptance tests. They can be run via:
426
+ The source also contains a set of https://cucumber.io/[Cucumber] based
427
+ acceptance tests. They can be run via:
389
428
 
390
- $ bundle exec rake features
429
+ ....
430
+ $ bundle exec rake features
431
+ ....
391
432
 
392
433
  The tests assume that the CDK box files are available under
393
- _build/boxes/cdk-\<provider\>.box_. You can either copy the box files manually or
394
- use the _get_cdk_ rake task to download them.
395
-
396
- As per default, only the scenarios for CDK in combination with VirtualBox
397
- are run. You can also run the tests against Libvirt, using the environment variable _PROVIDER_:
398
-
399
- # Run tests against Libvirt
400
- $ bundle exec rake features PROVIDER=libvirt
401
-
402
- # Run against VirtualBox and Libvirt
403
- $ bundle exec rake features PROVIDER=virtualbox,libvirt
404
-
405
- You can also run a single feature specifying the explicit feature file to use:
406
-
407
- $ bundle exec rake features FEATURE=features/<feature-filename>.feature
408
-
409
- After test execution the acceptance test reports can be found under _build/features_report.html_.
410
- They can also be opened via:
411
-
412
- $ bundle exec rake features:open_report
413
-
414
- <a name="acknowledgements"></a>
415
- ## Acknowledgements
416
-
417
- The project would like to make sure we thank [purpleidea](https://github.com/purpleidea/), [humaton](https://github.com/humaton/), [strzibny](https://github.com/strzibny), [scollier](https://github.com/scollier/), [puzzle](https://github.com/puzzle), [voxik](https://github.com/voxik), [lukaszachy](https://github.com/lukaszachy), [goern](https://github.com/goern), [iconoeugen](https://github.com/iconoeugen) and [pvalena](https://github.com/pvalena) (in no particular order) for their contributions of ideas, code and testing for this project.
434
+ __build/boxes/cdk-<provider>.box__. You can either copy the box files
435
+ manually or use the _get_cdk_ rake task to download them.
436
+
437
+ As per default, only the scenarios for CDK in combination with
438
+ VirtualBox are run. You can also run the tests against Libvirt, using
439
+ the environment variable __PROVIDER__:
440
+
441
+ ....
442
+ # Run tests against Libvirt
443
+ $ bundle exec rake features PROVIDER=libvirt
444
+
445
+ # Run against VirtualBox and Libvirt
446
+ $ bundle exec rake features PROVIDER=virtualbox,libvirt
447
+ ....
448
+
449
+ You can also run a single feature specifying the explicit feature file
450
+ to use:
451
+
452
+ ....
453
+ $ bundle exec rake features FEATURE=features/<feature-filename>.feature
454
+ ....
455
+
456
+ After test execution the acceptance test reports can be found under
457
+ __build/features_report.html__. They can also be opened via:
458
+
459
+ ....
460
+ $ bundle exec rake features:open_report
461
+ ....
462
+
463
+ == Acknowledgements
464
+
465
+ The project would like to make sure we thank
466
+ https://github.com/purpleidea/[purpleidea],
467
+ https://github.com/humaton/[humaton],
468
+ https://github.com/strzibny[strzibny],
469
+ https://github.com/scollier/[scollier],
470
+ https://github.com/puzzle[puzzle], https://github.com/voxik[voxik],
471
+ https://github.com/lukaszachy[lukaszachy],
472
+ https://github.com/goern[goern],
473
+ https://github.com/iconoeugen[iconoeugen] and
474
+ https://github.com/pvalena[pvalena] (in no particular order) for their
475
+ contributions of ideas, code and testing for this project.
data/lib/vagrant-registration/action/register.rb CHANGED
@@ -30,7 +30,7 @@ module VagrantPlugins
30
30
 
31
31
  # Offer to register ATM or skip
32
32
  register_now = ui.ask I18n.t('registration.action.register.prompt')
33
- process_registration(guest, machine, ui, config) if register_now == 'y'
33
+ process_registration(guest, machine, ui, config) if register_now == 'y' || register_now.empty?
34
34
  end
35
35
  end
36
36
 
data/lib/vagrant-registration/version.rb CHANGED
@@ -1,6 +1,6 @@
1
1
  module VagrantPlugins
2
2
  # Registration plugin to auto-register guests on `vagrant up`
3
3
  module Registration
4
- VERSION = '1.3.0'
4
+ VERSION = '1.3.1'
5
5
  end
6
6
  end
data/plugins/guests/redhat/cap/rhn_register.rb CHANGED
@@ -81,7 +81,7 @@ module VagrantPlugins
81
81
  if File.exist?(machine.config.registration.ca_cert)
82
82
  # Make sure the provided CA certificate file will be configured
83
83
  cert_file_name = File.basename(machine.config.registration.ca_cert)
84
- cert_file_content = File.read(machine.config.registration.ca_cert, tmp)
84
+ cert_file_content = File.read(machine.config.registration.ca_cert)
85
85
  machine.communicate.sudo("echo '#{cert_file_content}' > /usr/share/rhn/#{cert_file_name}")
86
86
  else
87
87
  ui.warn("WARNING: Provided CA certificate file #{machine.config.registration.ca_cert} does not exist, skipping")
data/vagrant-registration.gemspec CHANGED
@@ -21,7 +21,7 @@ Gem::Specification.new do |s|
21
21
  Dir.glob('plugins/**/{*,.*}') +
22
22
  Dir.glob('locales/**/{*,.*}') +
23
23
  Dir.glob('resources/**/{*,.*}') +
24
- ['Rakefile', 'Gemfile', 'README.md', 'CHANGELOG.md', 'LICENSE.md', 'vagrant-registration.gemspec']
24
+ ['Rakefile', 'Gemfile', 'README.adoc', 'CHANGELOG.adoc', 'LICENSE', 'vagrant-registration.gemspec']
25
25
  end
26
26
  all_files.reject! { |file| ['.', '..'].include?(File.basename(file)) }
27
27
  gitignore_path = File.join(root_path, '.gitignore')
metadata CHANGED
@@ -1,7 +1,7 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: vagrant-registration
3
3
  version: !ruby/object:Gem::Version
4
- version: 1.3.0
4
+ version: 1.3.1
5
5
  platform: ruby
6
6
  authors:
7
7
  - Langdon White
@@ -10,7 +10,7 @@ authors:
10
10
  autorequire:
11
11
  bindir: bin
12
12
  cert_chain: []
13
- date: 2016-09-02 00:00:00.000000000 Z
13
+ date: 2016-11-08 00:00:00.000000000 Z
14
14
  dependencies: []
15
15
  description: Enables guests to be registered automatically which is especially useful
16
16
  for RHEL or SLES guests.
@@ -21,10 +21,10 @@ executables: []
21
21
  extensions: []
22
22
  extra_rdoc_files: []
23
23
  files:
24
- - CHANGELOG.md
24
+ - CHANGELOG.adoc
25
25
  - Gemfile
26
- - LICENSE.md
27
- - README.md
26
+ - LICENSE
27
+ - README.adoc
28
28
  - Rakefile
29
29
  - lib/vagrant-registration.rb
30
30
  - lib/vagrant-registration/action.rb
data/CHANGELOG.md DELETED
@@ -1,60 +0,0 @@
1
- # Changelog
2
-
3
- ## 1.3.0
4
-
5
- - Fixed formatting, typo, grammar in README
6
- - Added MAINTAINERS file
7
- - Fix #44 allow more than one try to fill username and password
8
- - Fixes #99 using proxy info to unregister
9
- - Fix #107 register when passing credentials as env variables
10
-
11
- ## 1.2.3
12
-
13
- - Issue #90 Use locale based messaging
14
- - Issue #65 Adding cucumber tests for proxy settings
15
- - Issue #65 Adding proxy options to rhn_register and subscription_manager
16
- - Adding minitest as unit test framework and setting up basic test harness for Vagrant plugins
17
- - Issue #65 Removing obsolete bash tests
18
-
19
- ## 1.2.2
20
-
21
- - Introducing Cucumber based acceptance tests.
22
- - Fix: Handling of vagrant-registration action hooks depending on provider used.
23
-
24
- ## 1.2.1
25
-
26
- - Fix regression: Use sudo when asking on registration managers being present
27
-
28
- ## 1.2.0
29
-
30
- - Fix: `vagrant destroy` not triggering subscription deactivation and removal, issue #57
31
- - Fix: Allow auto-attach and force options to be configured
32
- - Fix: Remove unnecessary shebang from python script
33
- - Support for attaching to specified subscription pool(s), issue #36
34
- - Fix: rhn_register upload certificate fails, issue #60
35
-
36
- ## 1.1.0
37
-
38
- - Print warning if specifically selected manager is not available
39
- - Support running alongside vagrant-vbguest, issue #40
40
- - Support rhn_register manager
41
- - Fix: Handle various types of configuration option values, issue #48
42
- - Fix: Hide password on registration failure, issue #47
43
-
44
- ## 1.0.1
45
-
46
- - Fix: Set repo_ca_cert option in /etc/rhsm/rhsm.conf after uploading a certificate
47
-
48
- ## 1.0.0
49
-
50
- - Support providing a CA certificate via `config.registration.ca_cert` option
51
- - Issue warnings on unsupported configuration options
52
- - Do not ship tests
53
-
54
- ## 0.0.19
55
-
56
- - Remove extra files from installation
57
-
58
- ## 0.0.18
59
-
60
- - Support `config.registration.unregister_on_halt` option