kitchen-puppet 1.0.36 → 1.0.37
Sign up to get free protection for your applications and to get access to all the features.
- checksums.yaml +4 -4
- data/README.md +187 -187
- data/kitchen-puppet.gemspec +31 -31
- data/lib/kitchen-puppet/version.rb +7 -7
- data/lib/kitchen/provisioner/puppet/librarian.rb +78 -78
- data/lib/kitchen/provisioner/puppet_agent.rb +388 -388
- data/lib/kitchen/provisioner/puppet_apply.rb +1014 -1006
- data/provisioner_options.md +258 -258
- metadata +10 -10
checksums.yaml
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
---
|
|
2
2
|
SHA1:
|
|
3
|
-
metadata.gz:
|
|
4
|
-
data.tar.gz:
|
|
3
|
+
metadata.gz: 0ec6e8a4314d3fd7eaaf678f211cf13069d04786
|
|
4
|
+
data.tar.gz: fb7cece3c7762cbc6d018f87cb2e96da95c49af0
|
|
5
5
|
SHA512:
|
|
6
|
-
metadata.gz:
|
|
7
|
-
data.tar.gz:
|
|
6
|
+
metadata.gz: f3af7659697d626850a0af5ff1f896bc3c259f1cd344b53c14b79497711f4aa4cdc8faf38545469d619bde364f5a6fe8b0595bedbba077b8adb00045819d4e41
|
|
7
|
+
data.tar.gz: e7d93b7ae91bf5a89aa1c841c9b4e24e5bf06e027860311ef16dcf3769ceab10dcf35d43c357ef8f2e2b831946f1fb850291bbd03a36d312ea4815650368142a
|
data/README.md
CHANGED
|
@@ -1,187 +1,187 @@
|
|
|
1
|
-
# Kitchen Puppet
|
|
2
|
-
|
|
3
|
-
[](http://badge.fury.io/rb/kitchen-puppet)
|
|
4
|
-
[](https://rubygems.org/gems/kitchen-puppet)
|
|
5
|
-
[](https://travis-ci.org/neillturner/kitchen-puppet)
|
|
6
|
-
|
|
7
|
-
# kitchen-puppet
|
|
8
|
-
A Test Kitchen Provisioner for Puppet
|
|
9
|
-
|
|
10
|
-
The providers supports both puppet apply and puppet agent clients
|
|
11
|
-
|
|
12
|
-
The PuppetApply provider works by passing the puppet repository based on attributes in .kitchen.yml & calling puppet apply.
|
|
13
|
-
|
|
14
|
-
The PuppetAgent provider works by passing the puppetmaster and other attributes in .kitchen.yml & calling puppet agent.
|
|
15
|
-
|
|
16
|
-
|
|
17
|
-
This provider has been tested against the Ubuntu 1204 and Centos 6.5 boxes running in vagrant/virtualbox as well as various docker .
|
|
18
|
-
|
|
19
|
-
## Windows Workstation Install
|
|
20
|
-
You need to download the puppet msi and install it and run everything inside the puppet window.
|
|
21
|
-
|
|
22
|
-
1. Download and install puppet from the windows msi file from https://downloads.puppetlabs.com/windows
|
|
23
|
-
* I recommend the using the 32 bit version as not all ruby gems works with the 64 bit version.
|
|
24
|
-
* Don't do a 'gem install puppet' !!!.
|
|
25
|
-
|
|
26
|
-
2. Select "Start Command Prompt with Puppet" to go to a Command Window.
|
|
27
|
-
|
|
28
|
-
3. Install the Ruby DevKit:
|
|
29
|
-
* Download and install devkit from http://rubyinstaller.org/downloads
|
|
30
|
-
* (Use a 32 or 64 bit version that matches version of the ruby install)
|
|
31
|
-
* In the devkit directory run “ruby dk.rb init”.
|
|
32
|
-
* Edit the config.yml generated and add the the path of the ruby install for puppet
|
|
33
|
-
* (it will be <install dir of puppet>/sys/ruby).
|
|
34
|
-
* Run “ruby dk.rb install” to bind it to the puppet ruby installation.
|
|
35
|
-
|
|
36
|
-
4. From a Command prompt:
|
|
37
|
-
* gem install librarian-puppet
|
|
38
|
-
* gem install test-kitchen
|
|
39
|
-
* gem install kitchen-puppet
|
|
40
|
-
|
|
41
|
-
## Mac-OSX Workstation Install
|
|
42
|
-
|
|
43
|
-
1. Download and install the mac packages from https://downloads.puppetlabs.com/mac/
|
|
44
|
-
* The most recent Facter package (facter-<VERSION>.dmg)
|
|
45
|
-
* The most recent Hiera package (hiera-<VERSION>.dmg)
|
|
46
|
-
* The most recent Puppet package (puppet-<VERSION>.dmg)
|
|
47
|
-
* See [How to Install Software from DMG Files on a Mac](http://www.ofzenandcomputing.com/how-to-install-dmg-files-mac/) for details.
|
|
48
|
-
|
|
49
|
-
2. From a Command prompt:
|
|
50
|
-
* gem install librarian-puppet
|
|
51
|
-
* gem install test-kitchen
|
|
52
|
-
* gem install kitchen-puppet
|
|
53
|
-
|
|
54
|
-
## Requirements
|
|
55
|
-
It is recommended to have a metadata.json file of your puppet module. It is used by kitchen-puppet to configure the module path.
|
|
56
|
-
The puppet docs describe (https://docs.puppetlabs.com/puppet/latest/reference/modules_publishing.html#write-a-metadatajson-file) how to create one.
|
|
57
|
-
|
|
58
|
-
You'll need a driver box without a chef installation so puppet can be installed. Puppet have one at http://puppet-vagrant-boxes.puppetlabs.com/ubuntu-server-12042-x64-vbox4210-nocm.box or http://puppet-vagrant-boxes.puppetlabs.com/centos-65-x64-virtualbox-nocm.box.
|
|
59
|
-
|
|
60
|
-
For PuppetAgent a server with a puppet master is required that can resolve the hostname ip address of the server. The server must also be able to resolve the hostname ip address of the puppet master.
|
|
61
|
-
|
|
62
|
-
You can also use the PuppetApply driver with a docker container, provided the necessary box requirements to install puppet are included inside the container. The easiest way to do this is to supply Kitchen-Docker with a custom dockerfile to install the needed dependencies for puppet installation.
|
|
63
|
-
|
|
64
|
-
## Test-Kitchen Serverspec
|
|
65
|
-
|
|
66
|
-
To run the verify step with the test-kitchen serverspec setup your puppet repository as follows:
|
|
67
|
-
|
|
68
|
-
In the root directory for your puppet repository:
|
|
69
|
-
|
|
70
|
-
Create a `.kitchen.yml`, much like one the described above:
|
|
71
|
-
|
|
72
|
-
```yaml
|
|
73
|
-
---
|
|
74
|
-
driver:
|
|
75
|
-
name: vagrant
|
|
76
|
-
|
|
77
|
-
provisioner:
|
|
78
|
-
name: puppet_apply
|
|
79
|
-
manifests_path: /repository/puppet_repo/manifests
|
|
80
|
-
modules_path: /repository/puppet_repo/modules-mycompany
|
|
81
|
-
hiera_data_path: /repository/puppet_repo/hieradata
|
|
82
|
-
|
|
83
|
-
platforms:
|
|
84
|
-
- name: nocm_ubuntu-12.04
|
|
85
|
-
driver_plugin: vagrant
|
|
86
|
-
driver_config:
|
|
87
|
-
box: nocm_ubuntu-12.04
|
|
88
|
-
box_url: http://puppet-vagrant-boxes.puppetlabs.com/ubuntu-server-12042-x64-vbox4210-nocm.box
|
|
89
|
-
|
|
90
|
-
suites:
|
|
91
|
-
- name: default
|
|
92
|
-
```
|
|
93
|
-
|
|
94
|
-
Then for serverspec:
|
|
95
|
-
|
|
96
|
-
```bash
|
|
97
|
-
mkdir -p test/integration/default/serverspec/localhost
|
|
98
|
-
echo "require 'serverspec'" >> test/integration/default/serverspec/spec_helper.rb
|
|
99
|
-
echo "set :backend, :exec" >> test/integration/default/serverspec/spec_helper.rb
|
|
100
|
-
```
|
|
101
|
-
|
|
102
|
-
Create your serverspec tests in `test/integration/default/serverspec/localhost/xxxxxx_spec.rb`:
|
|
103
|
-
|
|
104
|
-
```ruby
|
|
105
|
-
require 'spec_helper'
|
|
106
|
-
|
|
107
|
-
if os[:family] == 'ubuntu'
|
|
108
|
-
describe '/etc/lsb-release' do
|
|
109
|
-
it "exists" do
|
|
110
|
-
expect(file('/etc/lsb-release')).to be_file
|
|
111
|
-
end
|
|
112
|
-
end
|
|
113
|
-
end
|
|
114
|
-
|
|
115
|
-
if os[:family] == 'redhat'
|
|
116
|
-
describe '/etc/redhat-release' do
|
|
117
|
-
it "exists" do
|
|
118
|
-
expect(file('/etc/redhat-release')).to be_file
|
|
119
|
-
end
|
|
120
|
-
end
|
|
121
|
-
end
|
|
122
|
-
```
|
|
123
|
-
|
|
124
|
-
## Test-Kitchen Beaker
|
|
125
|
-
|
|
126
|
-
test-kitchen normally uses tests setup in `test/integration/....` directory. Beaker format puts the tests with the
|
|
127
|
-
`spec/acceptance` directory in the puppet repository and the `spec_helper.rb` under the `spec` directory.
|
|
128
|
-
|
|
129
|
-
For examples see:
|
|
130
|
-
* https://gitlab.com/joshbeard/puppet-module-test
|
|
131
|
-
* https://github.com/puppetlabs/puppetlabs-mysql/tree/master/spec
|
|
132
|
-
|
|
133
|
-
To implement this with test-kitchen setup the puppet repository with:
|
|
134
|
-
|
|
135
|
-
* the spec files with the spec/acceptance directory.
|
|
136
|
-
|
|
137
|
-
* the spec_helper in the spec folder.
|
|
138
|
-
|
|
139
|
-
* install kitchen-verifier-serverspec on your workstation i.e. 'gem install kitchen-verifier-serverspec'
|
|
140
|
-
|
|
141
|
-
|
|
142
|
-
See example [https://github.com/neillturner/
|
|
143
|
-
|
|
144
|
-
```
|
|
145
|
-
.
|
|
146
|
-
+-- spec
|
|
147
|
-
¦ +-- acceptance
|
|
148
|
-
¦ ¦ +-- mariadb_spec.rb
|
|
149
|
-
¦ ¦ +-- nginx_spec.rb
|
|
150
|
-
¦ ¦
|
|
151
|
-
+-- spec_helper.rb
|
|
152
|
-
|
|
153
|
-
```
|
|
154
|
-
|
|
155
|
-
In the root directory for your puppet repository create a `.kitchen.yml` with
|
|
156
|
-
|
|
157
|
-
* a verifier of 'serverspec'
|
|
158
|
-
* a pattern parameter with the spec tests to run
|
|
159
|
-
|
|
160
|
-
```yaml
|
|
161
|
-
verifier:
|
|
162
|
-
name: serverspec
|
|
163
|
-
|
|
164
|
-
suites:
|
|
165
|
-
- name: base
|
|
166
|
-
verifier:
|
|
167
|
-
patterns:
|
|
168
|
-
- modules/mycompany_base/spec/acceptance/base_spec.rb
|
|
169
|
-
```
|
|
170
|
-
|
|
171
|
-
See [busser-beaker](https://github.com/neillturner/kitchen-verifier-serverspec)
|
|
172
|
-
|
|
173
|
-
|
|
174
|
-
## Provisioner Options
|
|
175
|
-
Please see the Provisioner Options (https://github.com/neillturner/kitchen-puppet/blob/master/provisioner_options.md).
|
|
176
|
-
|
|
177
|
-
## Contributing
|
|
178
|
-
To contribute to the repository, please follow the Fork / PR model:
|
|
179
|
-
|
|
180
|
-
1. Fork The Repository
|
|
181
|
-
2. Work on epic changes
|
|
182
|
-
3. Write tests for your changes, see [TESTING](TESTING.md)
|
|
183
|
-
4. Update Documentation
|
|
184
|
-
5. Commit
|
|
185
|
-
6. Push
|
|
186
|
-
7. Create PR
|
|
187
|
-
8. Profit(?)
|
|
1
|
+
# Kitchen Puppet
|
|
2
|
+
|
|
3
|
+
[](http://badge.fury.io/rb/kitchen-puppet)
|
|
4
|
+
[](https://rubygems.org/gems/kitchen-puppet)
|
|
5
|
+
[](https://travis-ci.org/neillturner/kitchen-puppet)
|
|
6
|
+
|
|
7
|
+
# kitchen-puppet
|
|
8
|
+
A Test Kitchen Provisioner for Puppet
|
|
9
|
+
|
|
10
|
+
The providers supports both puppet apply and puppet agent clients
|
|
11
|
+
|
|
12
|
+
The PuppetApply provider works by passing the puppet repository based on attributes in .kitchen.yml & calling puppet apply.
|
|
13
|
+
|
|
14
|
+
The PuppetAgent provider works by passing the puppetmaster and other attributes in .kitchen.yml & calling puppet agent.
|
|
15
|
+
|
|
16
|
+
|
|
17
|
+
This provider has been tested against the Ubuntu 1204 and Centos 6.5 boxes running in vagrant/virtualbox as well as various docker .
|
|
18
|
+
|
|
19
|
+
## Windows Workstation Install
|
|
20
|
+
You need to download the puppet msi and install it and run everything inside the puppet window.
|
|
21
|
+
|
|
22
|
+
1. Download and install puppet from the windows msi file from https://downloads.puppetlabs.com/windows
|
|
23
|
+
* I recommend the using the 32 bit version as not all ruby gems works with the 64 bit version.
|
|
24
|
+
* Don't do a 'gem install puppet' !!!.
|
|
25
|
+
|
|
26
|
+
2. Select "Start Command Prompt with Puppet" to go to a Command Window.
|
|
27
|
+
|
|
28
|
+
3. Install the Ruby DevKit:
|
|
29
|
+
* Download and install devkit from http://rubyinstaller.org/downloads
|
|
30
|
+
* (Use a 32 or 64 bit version that matches version of the ruby install)
|
|
31
|
+
* In the devkit directory run “ruby dk.rb init”.
|
|
32
|
+
* Edit the config.yml generated and add the the path of the ruby install for puppet
|
|
33
|
+
* (it will be <install dir of puppet>/sys/ruby).
|
|
34
|
+
* Run “ruby dk.rb install” to bind it to the puppet ruby installation.
|
|
35
|
+
|
|
36
|
+
4. From a Command prompt:
|
|
37
|
+
* gem install librarian-puppet
|
|
38
|
+
* gem install test-kitchen
|
|
39
|
+
* gem install kitchen-puppet
|
|
40
|
+
|
|
41
|
+
## Mac-OSX Workstation Install
|
|
42
|
+
|
|
43
|
+
1. Download and install the mac packages from https://downloads.puppetlabs.com/mac/
|
|
44
|
+
* The most recent Facter package (facter-<VERSION>.dmg)
|
|
45
|
+
* The most recent Hiera package (hiera-<VERSION>.dmg)
|
|
46
|
+
* The most recent Puppet package (puppet-<VERSION>.dmg)
|
|
47
|
+
* See [How to Install Software from DMG Files on a Mac](http://www.ofzenandcomputing.com/how-to-install-dmg-files-mac/) for details.
|
|
48
|
+
|
|
49
|
+
2. From a Command prompt:
|
|
50
|
+
* gem install librarian-puppet
|
|
51
|
+
* gem install test-kitchen
|
|
52
|
+
* gem install kitchen-puppet
|
|
53
|
+
|
|
54
|
+
## Requirements
|
|
55
|
+
It is recommended to have a metadata.json file of your puppet module. It is used by kitchen-puppet to configure the module path.
|
|
56
|
+
The puppet docs describe (https://docs.puppetlabs.com/puppet/latest/reference/modules_publishing.html#write-a-metadatajson-file) how to create one.
|
|
57
|
+
|
|
58
|
+
You'll need a driver box without a chef installation so puppet can be installed. Puppet have one at http://puppet-vagrant-boxes.puppetlabs.com/ubuntu-server-12042-x64-vbox4210-nocm.box or http://puppet-vagrant-boxes.puppetlabs.com/centos-65-x64-virtualbox-nocm.box.
|
|
59
|
+
|
|
60
|
+
For PuppetAgent a server with a puppet master is required that can resolve the hostname ip address of the server. The server must also be able to resolve the hostname ip address of the puppet master.
|
|
61
|
+
|
|
62
|
+
You can also use the PuppetApply driver with a docker container, provided the necessary box requirements to install puppet are included inside the container. The easiest way to do this is to supply Kitchen-Docker with a custom dockerfile to install the needed dependencies for puppet installation.
|
|
63
|
+
|
|
64
|
+
## Test-Kitchen Serverspec
|
|
65
|
+
|
|
66
|
+
To run the verify step with the test-kitchen serverspec setup your puppet repository as follows:
|
|
67
|
+
|
|
68
|
+
In the root directory for your puppet repository:
|
|
69
|
+
|
|
70
|
+
Create a `.kitchen.yml`, much like one the described above:
|
|
71
|
+
|
|
72
|
+
```yaml
|
|
73
|
+
---
|
|
74
|
+
driver:
|
|
75
|
+
name: vagrant
|
|
76
|
+
|
|
77
|
+
provisioner:
|
|
78
|
+
name: puppet_apply
|
|
79
|
+
manifests_path: /repository/puppet_repo/manifests
|
|
80
|
+
modules_path: /repository/puppet_repo/modules-mycompany
|
|
81
|
+
hiera_data_path: /repository/puppet_repo/hieradata
|
|
82
|
+
|
|
83
|
+
platforms:
|
|
84
|
+
- name: nocm_ubuntu-12.04
|
|
85
|
+
driver_plugin: vagrant
|
|
86
|
+
driver_config:
|
|
87
|
+
box: nocm_ubuntu-12.04
|
|
88
|
+
box_url: http://puppet-vagrant-boxes.puppetlabs.com/ubuntu-server-12042-x64-vbox4210-nocm.box
|
|
89
|
+
|
|
90
|
+
suites:
|
|
91
|
+
- name: default
|
|
92
|
+
```
|
|
93
|
+
|
|
94
|
+
Then for serverspec:
|
|
95
|
+
|
|
96
|
+
```bash
|
|
97
|
+
mkdir -p test/integration/default/serverspec/localhost
|
|
98
|
+
echo "require 'serverspec'" >> test/integration/default/serverspec/spec_helper.rb
|
|
99
|
+
echo "set :backend, :exec" >> test/integration/default/serverspec/spec_helper.rb
|
|
100
|
+
```
|
|
101
|
+
|
|
102
|
+
Create your serverspec tests in `test/integration/default/serverspec/localhost/xxxxxx_spec.rb`:
|
|
103
|
+
|
|
104
|
+
```ruby
|
|
105
|
+
require 'spec_helper'
|
|
106
|
+
|
|
107
|
+
if os[:family] == 'ubuntu'
|
|
108
|
+
describe '/etc/lsb-release' do
|
|
109
|
+
it "exists" do
|
|
110
|
+
expect(file('/etc/lsb-release')).to be_file
|
|
111
|
+
end
|
|
112
|
+
end
|
|
113
|
+
end
|
|
114
|
+
|
|
115
|
+
if os[:family] == 'redhat'
|
|
116
|
+
describe '/etc/redhat-release' do
|
|
117
|
+
it "exists" do
|
|
118
|
+
expect(file('/etc/redhat-release')).to be_file
|
|
119
|
+
end
|
|
120
|
+
end
|
|
121
|
+
end
|
|
122
|
+
```
|
|
123
|
+
|
|
124
|
+
## Test-Kitchen Beaker
|
|
125
|
+
|
|
126
|
+
test-kitchen normally uses tests setup in `test/integration/....` directory. Beaker format puts the tests with the
|
|
127
|
+
`spec/acceptance` directory in the puppet repository and the `spec_helper.rb` under the `spec` directory which is more logical.
|
|
128
|
+
|
|
129
|
+
For examples see:
|
|
130
|
+
* https://gitlab.com/joshbeard/puppet-module-test
|
|
131
|
+
* https://github.com/puppetlabs/puppetlabs-mysql/tree/master/spec
|
|
132
|
+
|
|
133
|
+
To implement this with test-kitchen setup the puppet repository with:
|
|
134
|
+
|
|
135
|
+
* the spec files with the spec/acceptance directory.
|
|
136
|
+
|
|
137
|
+
* the spec_helper in the spec folder.
|
|
138
|
+
|
|
139
|
+
* install kitchen-verifier-serverspec on your workstation i.e. 'gem install kitchen-verifier-serverspec'
|
|
140
|
+
|
|
141
|
+
|
|
142
|
+
See example [https://github.com/neillturner/puppet_repo](https://github.com/neillturner/puppet_repo)
|
|
143
|
+
|
|
144
|
+
```
|
|
145
|
+
.
|
|
146
|
+
+-- spec
|
|
147
|
+
¦ +-- acceptance
|
|
148
|
+
¦ ¦ +-- mariadb_spec.rb
|
|
149
|
+
¦ ¦ +-- nginx_spec.rb
|
|
150
|
+
¦ ¦
|
|
151
|
+
+-- spec_helper.rb
|
|
152
|
+
|
|
153
|
+
```
|
|
154
|
+
|
|
155
|
+
In the root directory for your puppet repository create a `.kitchen.yml` with
|
|
156
|
+
|
|
157
|
+
* a verifier of 'serverspec'
|
|
158
|
+
* a pattern parameter with the spec tests to run
|
|
159
|
+
|
|
160
|
+
```yaml
|
|
161
|
+
verifier:
|
|
162
|
+
name: serverspec
|
|
163
|
+
|
|
164
|
+
suites:
|
|
165
|
+
- name: base
|
|
166
|
+
verifier:
|
|
167
|
+
patterns:
|
|
168
|
+
- modules/mycompany_base/spec/acceptance/base_spec.rb
|
|
169
|
+
```
|
|
170
|
+
|
|
171
|
+
See [busser-beaker](https://github.com/neillturner/kitchen-verifier-serverspec)
|
|
172
|
+
|
|
173
|
+
|
|
174
|
+
## Provisioner Options
|
|
175
|
+
Please see the Provisioner Options (https://github.com/neillturner/kitchen-puppet/blob/master/provisioner_options.md).
|
|
176
|
+
|
|
177
|
+
## Contributing
|
|
178
|
+
To contribute to the repository, please follow the Fork / PR model:
|
|
179
|
+
|
|
180
|
+
1. Fork The Repository
|
|
181
|
+
2. Work on epic changes
|
|
182
|
+
3. Write tests for your changes, see [TESTING](TESTING.md)
|
|
183
|
+
4. Update Documentation
|
|
184
|
+
5. Commit
|
|
185
|
+
6. Push
|
|
186
|
+
7. Create PR
|
|
187
|
+
8. Profit(?)
|
data/kitchen-puppet.gemspec
CHANGED
|
@@ -1,31 +1,31 @@
|
|
|
1
|
-
# encoding: utf-8
|
|
2
|
-
|
|
3
|
-
$LOAD_PATH.unshift File.expand_path('../lib', __FILE__)
|
|
4
|
-
require 'kitchen-puppet/version'
|
|
5
|
-
|
|
6
|
-
Gem::Specification.new do |s|
|
|
7
|
-
s.name = 'kitchen-puppet'
|
|
8
|
-
s.license = 'Apache-2.0'
|
|
9
|
-
s.version = Kitchen::Puppet::VERSION
|
|
10
|
-
s.authors = ['Neill Turner']
|
|
11
|
-
s.email = ['neillwturner@gmail.com']
|
|
12
|
-
s.homepage = 'https://github.com/neillturner/kitchen-puppet'
|
|
13
|
-
s.summary = 'puppet provisioner for test-kitchen'
|
|
14
|
-
candidates = Dir.glob('{lib}/**/*') + ['README.md', 'provisioner_options.md', 'kitchen-puppet.gemspec']
|
|
15
|
-
s.files = candidates.sort
|
|
16
|
-
s.platform = Gem::Platform::RUBY
|
|
17
|
-
s.require_paths = ['lib']
|
|
18
|
-
s.rubyforge_project = '[none]'
|
|
19
|
-
s.add_dependency 'test-kitchen', '~> 1.4'
|
|
20
|
-
s.add_dependency 'net-ssh', '~> 2.0'
|
|
21
|
-
s.description = <<-EOF
|
|
22
|
-
== DESCRIPTION:
|
|
23
|
-
|
|
24
|
-
Puppet Provisioner for Test Kitchen
|
|
25
|
-
|
|
26
|
-
== FEATURES:
|
|
27
|
-
|
|
28
|
-
Supports puppet apply, puppet agent, hiera, hiera-eyaml, custom facts, librarian-puppet, puppet collections (v4)
|
|
29
|
-
|
|
30
|
-
EOF
|
|
31
|
-
end
|
|
1
|
+
# encoding: utf-8
|
|
2
|
+
|
|
3
|
+
$LOAD_PATH.unshift File.expand_path('../lib', __FILE__)
|
|
4
|
+
require 'kitchen-puppet/version'
|
|
5
|
+
|
|
6
|
+
Gem::Specification.new do |s|
|
|
7
|
+
s.name = 'kitchen-puppet'
|
|
8
|
+
s.license = 'Apache-2.0'
|
|
9
|
+
s.version = Kitchen::Puppet::VERSION
|
|
10
|
+
s.authors = ['Neill Turner']
|
|
11
|
+
s.email = ['neillwturner@gmail.com']
|
|
12
|
+
s.homepage = 'https://github.com/neillturner/kitchen-puppet'
|
|
13
|
+
s.summary = 'puppet provisioner for test-kitchen'
|
|
14
|
+
candidates = Dir.glob('{lib}/**/*') + ['README.md', 'provisioner_options.md', 'kitchen-puppet.gemspec']
|
|
15
|
+
s.files = candidates.sort
|
|
16
|
+
s.platform = Gem::Platform::RUBY
|
|
17
|
+
s.require_paths = ['lib']
|
|
18
|
+
s.rubyforge_project = '[none]'
|
|
19
|
+
s.add_dependency 'test-kitchen', '~> 1.4'
|
|
20
|
+
s.add_dependency 'net-ssh', '~> 2.0'
|
|
21
|
+
s.description = <<-EOF
|
|
22
|
+
== DESCRIPTION:
|
|
23
|
+
|
|
24
|
+
Puppet Provisioner for Test Kitchen
|
|
25
|
+
|
|
26
|
+
== FEATURES:
|
|
27
|
+
|
|
28
|
+
Supports puppet apply, puppet agent, hiera, hiera-eyaml, custom facts, librarian-puppet, puppet collections (v4)
|
|
29
|
+
|
|
30
|
+
EOF
|
|
31
|
+
end
|
|
@@ -1,7 +1,7 @@
|
|
|
1
|
-
# encoding: UTF-8
|
|
2
|
-
|
|
3
|
-
module Kitchen
|
|
4
|
-
module Puppet
|
|
5
|
-
VERSION = '1.0.
|
|
6
|
-
end
|
|
7
|
-
end
|
|
1
|
+
# encoding: UTF-8
|
|
2
|
+
|
|
3
|
+
module Kitchen
|
|
4
|
+
module Puppet
|
|
5
|
+
VERSION = '1.0.37'.freeze
|
|
6
|
+
end
|
|
7
|
+
end
|