kitchen-puppet 1.44.2 → 1.45.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: cd58c9e24c4ed130d895099fb48c088aa5218700
-  data.tar.gz: b579886df2009d4f4fe00c2c804d37825268c353
+  metadata.gz: bc9867719f776ed274af4071a93f2e596f874741
+  data.tar.gz: 46b3fec2a7f164ec354ff6787f47f66c4508b83d
 SHA512:
-  metadata.gz: fe0ae57bd4aabe8c93f42c952b7e0f43a88a747f6e150154d1c0cc727254f70c58b6d867d87f7601a4df32bea284202c4aa352975261db6adefd95f51f0b4fb7
-  data.tar.gz: f1462b3dfd3568b16eaa8ce952193bb107e900124e8319c9a0ba2803e855fecf0f639f32636cd3cfea2de8a88dcb1c7b3eb2237aeb34d4c17b6a119423a8c146
+  metadata.gz: 1263a1c2d9d8dd8d9ff5150efa040cf4db40080fd509e916473991c105ff82f9979fe15f278f002555f4d83dbf49e2ba064ed1f793df4b184e86fe662e0ec3e8
+  data.tar.gz: f68fa758a2873c03ecec436ddb13e321531f3d34da14c2879da990170148f67ea7ebb85ffab02694d5701fe6050dbde47016192a6d26d953ed732f6bbfd9c89f

data/README.md

@@ -1,197 +1,197 @@
-# Kitchen Puppet
-
-[![Gem Version](https://badge.fury.io/rb/kitchen-puppet.svg)](http://badge.fury.io/rb/kitchen-puppet)
-[![Gem Downloads](http://ruby-gem-downloads-badge.herokuapp.com/kitchen-puppet?type=total&color=brightgreen)](https://rubygems.org/gems/kitchen-puppet)
-[![Build Status](https://travis-ci.org/neillturner/kitchen-puppet.png)](https://travis-ci.org/neillturner/kitchen-puppet)
-
-# kitchen-puppet
-A Test Kitchen Provisioner for Puppet
-
-The providers supports both puppet apply and puppet agent clients
-
-The PuppetApply provider works by passing the puppet repository based on attributes in .kitchen.yml & calling puppet apply.
-
-The PuppetAgent provider works by passing the puppetmaster and other attributes in .kitchen.yml & calling puppet agent.
-
-
-This provider has been tested against the Ubuntu 1204 and Centos 6.5 boxes running in vagrant/virtualbox as well as various docker .
-
-## Windows Workstation Install
-You need to download the puppet msi and install it and run everything inside the puppet window.
-
-1. Download and install puppet from the windows msi file from https://downloads.puppetlabs.com/windows
-  * I recommend the using the 32 bit version as not all ruby gems works with the 64 bit version.
-  * Don't do a 'gem install puppet' !!!.
-
-2. Select "Start Command Prompt with Puppet" to go to a Command Window.
-
-3. Install the Ruby DevKit:
-   * Download and install devkit from http://rubyinstaller.org/downloads
-     * (Use a 32 or 64 bit version that matches version of the ruby install)
-   * In the devkit directory run “ruby dk.rb init”.
-   * Edit the config.yml generated and add the the path of the ruby install for puppet
-     * (it will be <install dir of puppet>/sys/ruby).
-   * Run “ruby dk.rb install” to bind it to the puppet ruby installation.
-
-4. From a Command prompt:
-  * gem install librarian-puppet
-  * gem install test-kitchen
-  * gem install kitchen-puppet
-
-## Mac-OSX Workstation Install
-
-1. Download and install the mac packages from https://downloads.puppetlabs.com/mac/
-  * The most recent Facter package (facter-<VERSION>.dmg)
-  * The most recent Hiera package (hiera-<VERSION>.dmg)
-  * The most recent Puppet package (puppet-<VERSION>.dmg)
-  * See [How to Install Software from DMG Files on a Mac](http://www.ofzenandcomputing.com/how-to-install-dmg-files-mac/) for details.
-
-2. From a Command prompt:
-  * gem install librarian-puppet
-  * gem install test-kitchen
-  * gem install kitchen-puppet
-
-## Requirements
-It is recommended to have a metadata.json file of your puppet module. It is used by kitchen-puppet to configure the module path.
-The puppet docs describe (https://docs.puppetlabs.com/puppet/latest/reference/modules_publishing.html#write-a-metadatajson-file) how to create one.
-
-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.
-
-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.
-
-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.
-
-## Windows Support
-
-There is windows/winrm support, currently not all functionality is supported.
-  * `require_chef_for_busser: false` (it is possible to call rspec over winrm to run the tests)
-  * `resolve_with_librarian_puppet: false` (librarian-puppet is not working on windows server)
-
-Sample Puppet Repositories
-  * A sample hello world example puppet repository: https://github.com/neillturner/puppet_windows_repo
-  * A more extensive sample installing virtualbox on windows: https://github.com/red-gate/puppet-virtualbox_windows
-
-## Test-Kitchen Serverspec
-
-To run the verify step with the test-kitchen serverspec setup your puppet repository as follows:
-
-In the root directory for your puppet repository:
-
-Create a `.kitchen.yml`, much like one the described above:
-
-```yaml
-    ---
-    driver:
-      name: vagrant
-
-    provisioner:
-      name: puppet_apply
-      manifests_path: /repository/puppet_repo/manifests
-      modules_path: /repository/puppet_repo/modules-mycompany
-      hiera_data_path: /repository/puppet_repo/hieradata
-
-    platforms:
-    - name: nocm_ubuntu-12.04
-      driver_plugin: vagrant
-      driver_config:
-        box: nocm_ubuntu-12.04
-        box_url: http://puppet-vagrant-boxes.puppetlabs.com/ubuntu-server-12042-x64-vbox4210-nocm.box
-
-    suites:
-     - name: default
-```
-
-Then for serverspec:
-
-```bash
-  mkdir -p test/integration/default/serverspec/localhost
-  echo "require 'serverspec'" >> test/integration/default/serverspec/spec_helper.rb
-  echo "set :backend, :exec" >> test/integration/default/serverspec/spec_helper.rb
-```
-
-Create your serverspec tests in `test/integration/default/serverspec/localhost/xxxxxx_spec.rb`:
-
-```ruby
-  require 'spec_helper'
-
-  if os[:family] == 'ubuntu'
-        describe '/etc/lsb-release' do
-          it "exists" do
-              expect(file('/etc/lsb-release')).to be_file
-          end
-        end
-  end
-
-  if os[:family] == 'redhat'
-    describe '/etc/redhat-release' do
-      it "exists" do
-          expect(file('/etc/redhat-release')).to be_file
-      end
-    end
-  end
-```
-
-## Test-Kitchen Beaker
-
-test-kitchen normally uses tests setup in `test/integration/....` directory. Beaker format puts the tests with the
-`spec/acceptance` directory in the puppet repository and the `spec_helper.rb` under the `spec` directory which is more logical.
-
-For examples see:
-* https://gitlab.com/joshbeard/puppet-module-test
-* https://github.com/puppetlabs/puppetlabs-mysql/tree/master/spec
-
-To implement this with test-kitchen setup the puppet repository with:
-
-* the spec files with the spec/acceptance directory.
-
-* the spec_helper in the spec folder.
-
-* install kitchen-verifier-serverspec on your workstation i.e. 'gem install kitchen-verifier-serverspec'
-
-
-See example [https://github.com/neillturner/puppet_repo](https://github.com/neillturner/puppet_repo)
-
-```
-.
-+-- spec
-¦   +-- acceptance
-¦   ¦   +-- mariadb_spec.rb
-¦   ¦   +-- nginx_spec.rb
-¦   ¦
-    +-- spec_helper.rb
-
-```
-
-In the root directory for your puppet repository create a `.kitchen.yml` with
-
-* a verifier of 'serverspec'
-* a pattern parameter with the spec tests to run
-
-```yaml
-verifier:
-  name: serverspec
-
-suites:
-  - name: base
-    verifier:
-      patterns:
-      - modules/mycompany_base/spec/acceptance/base_spec.rb
-```
-
-See [busser-beaker](https://github.com/neillturner/kitchen-verifier-serverspec)
-
-
-## Provisioner Options
-Please see the Provisioner Options (https://github.com/neillturner/kitchen-puppet/blob/master/provisioner_options.md).
-
-## Contributing
-To contribute to the repository, please follow the Fork / PR model:
-
-1. Fork The Repository
-2. Work on epic changes
-3. Write tests for your changes, see [TESTING](TESTING.md)
-4. Update Documentation
-5. Commit
-6. Push
-7. Create PR
-8. Profit(?)
+# Kitchen Puppet
+
+[![Gem Version](https://badge.fury.io/rb/kitchen-puppet.svg)](http://badge.fury.io/rb/kitchen-puppet)
+[![Gem Downloads](http://ruby-gem-downloads-badge.herokuapp.com/kitchen-puppet?type=total&color=brightgreen)](https://rubygems.org/gems/kitchen-puppet)
+[![Build Status](https://travis-ci.org/neillturner/kitchen-puppet.png)](https://travis-ci.org/neillturner/kitchen-puppet)
+
+# kitchen-puppet
+A Test Kitchen Provisioner for Puppet
+
+The providers supports both puppet apply and puppet agent clients
+
+The PuppetApply provider works by passing the puppet repository based on attributes in .kitchen.yml & calling puppet apply.
+
+The PuppetAgent provider works by passing the puppetmaster and other attributes in .kitchen.yml & calling puppet agent.
+
+
+This provider has been tested against the Ubuntu 1204 and Centos 6.5 boxes running in vagrant/virtualbox as well as various docker .
+
+## Windows Workstation Install
+You need to download the puppet msi and install it and run everything inside the puppet window.
+
+1. Download and install puppet from the windows msi file from https://downloads.puppetlabs.com/windows
+  * I recommend the using the 64 bit version now.
+  * Don't do a 'gem install puppet' !!!.
+
+2. Select "Start Command Prompt with Puppet" to go to a Command Window.
+
+3. Install the Ruby DevKit:
+   * Download and install devkit from http://rubyinstaller.org/downloads
+     * (Use the 32 or 64 bit version that matches version of the puppet install)
+   * In the devkit directory run “ruby dk.rb init”.
+   * Edit the config.yml generated and add the the path of the ruby install for puppet
+     * (it will be <install dir of puppet>/sys/ruby).
+   * Run “ruby dk.rb install” to bind it to the puppet ruby installation.
+
+4. From a Command prompt:
+  * gem install librarian-puppet
+  * gem install test-kitchen
+  * gem install kitchen-puppet
+
+## Mac-OSX Workstation Install
+
+1. Download and install the mac packages from https://downloads.puppetlabs.com/mac/
+  * The most recent Facter package (facter-<VERSION>.dmg)
+  * The most recent Hiera package (hiera-<VERSION>.dmg)
+  * The most recent Puppet package (puppet-<VERSION>.dmg)
+  * See [How to Install Software from DMG Files on a Mac](http://www.ofzenandcomputing.com/how-to-install-dmg-files-mac/) for details.
+
+2. From a Command prompt:
+  * gem install librarian-puppet
+  * gem install test-kitchen
+  * gem install kitchen-puppet
+
+## Requirements
+It is recommended to have a metadata.json file of your puppet module. It is used by kitchen-puppet to configure the module path.
+The puppet docs describe (https://docs.puppetlabs.com/puppet/latest/reference/modules_publishing.html#write-a-metadatajson-file) how to create one.
+
+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.
+
+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.
+
+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.
+
+## Windows Support
+
+There is windows/winrm support, currently not all functionality is supported.
+  * `require_chef_for_busser: false` (it is possible to call rspec over winrm to run the tests)
+  * `resolve_with_librarian_puppet: false` (librarian-puppet is not working on windows server)
+
+Sample Puppet Repositories
+  * A sample hello world example puppet repository: https://github.com/neillturner/puppet_windows_repo
+  * A more extensive sample installing virtualbox on windows: https://github.com/red-gate/puppet-virtualbox_windows
+
+## Test-Kitchen Serverspec
+
+To run the verify step with the test-kitchen serverspec setup your puppet repository as follows:
+
+In the root directory for your puppet repository:
+
+Create a `.kitchen.yml`, much like one the described above:
+
+```yaml
+    ---
+    driver:
+      name: vagrant
+
+    provisioner:
+      name: puppet_apply
+      manifests_path: /repository/puppet_repo/manifests
+      modules_path: /repository/puppet_repo/modules-mycompany
+      hiera_data_path: /repository/puppet_repo/hieradata
+
+    platforms:
+    - name: nocm_ubuntu-12.04
+      driver_plugin: vagrant
+      driver_config:
+        box: nocm_ubuntu-12.04
+        box_url: http://puppet-vagrant-boxes.puppetlabs.com/ubuntu-server-12042-x64-vbox4210-nocm.box
+
+    suites:
+     - name: default
+```
+
+Then for serverspec:
+
+```bash
+  mkdir -p test/integration/default/serverspec/localhost
+  echo "require 'serverspec'" >> test/integration/default/serverspec/spec_helper.rb
+  echo "set :backend, :exec" >> test/integration/default/serverspec/spec_helper.rb
+```
+
+Create your serverspec tests in `test/integration/default/serverspec/localhost/xxxxxx_spec.rb`:
+
+```ruby
+  require 'spec_helper'
+
+  if os[:family] == 'ubuntu'
+        describe '/etc/lsb-release' do
+          it "exists" do
+              expect(file('/etc/lsb-release')).to be_file
+          end
+        end
+  end
+
+  if os[:family] == 'redhat'
+    describe '/etc/redhat-release' do
+      it "exists" do
+          expect(file('/etc/redhat-release')).to be_file
+      end
+    end
+  end
+```
+
+## Test-Kitchen Beaker
+
+test-kitchen normally uses tests setup in `test/integration/....` directory. Beaker format puts the tests with the
+`spec/acceptance` directory in the puppet repository and the `spec_helper.rb` under the `spec` directory which is more logical.
+
+For examples see:
+* https://gitlab.com/joshbeard/puppet-module-test
+* https://github.com/puppetlabs/puppetlabs-mysql/tree/master/spec
+
+To implement this with test-kitchen setup the puppet repository with:
+
+* the spec files with the spec/acceptance directory.
+
+* the spec_helper in the spec folder.
+
+* install kitchen-verifier-serverspec on your workstation i.e. 'gem install kitchen-verifier-serverspec'
+
+
+See example [https://github.com/neillturner/puppet_repo](https://github.com/neillturner/puppet_repo)
+
+```
+.
++-- spec
+¦   +-- acceptance
+¦   ¦   +-- mariadb_spec.rb
+¦   ¦   +-- nginx_spec.rb
+¦   ¦
+    +-- spec_helper.rb
+
+```
+
+In the root directory for your puppet repository create a `.kitchen.yml` with
+
+* a verifier of 'serverspec'
+* a pattern parameter with the spec tests to run
+
+```yaml
+verifier:
+  name: serverspec
+
+suites:
+  - name: base
+    verifier:
+      patterns:
+      - modules/mycompany_base/spec/acceptance/base_spec.rb
+```
+
+See [busser-beaker](https://github.com/neillturner/kitchen-verifier-serverspec)
+
+
+## Provisioner Options
+Please see the Provisioner Options (https://github.com/neillturner/kitchen-puppet/blob/master/provisioner_options.md).
+
+## Contributing
+To contribute to the repository, please follow the Fork / PR model:
+
+1. Fork The Repository
+2. Work on epic changes
+3. Write tests for your changes, see [TESTING](TESTING.md)
+4. Update Documentation
+5. Commit
+6. Push
+7. Create PR
+8. Profit(?)

data/kitchen-puppet.gemspec

@@ -1,35 +1,35 @@
-# encoding: utf-8
-
-$LOAD_PATH.unshift File.expand_path('../lib', __FILE__)
-require 'kitchen-puppet/version'
-
-Gem::Specification.new do |s|
-  s.name          = 'kitchen-puppet'
-  s.license       = 'Apache-2.0'
-  s.version       = Kitchen::Puppet::VERSION
-  s.authors       = ['Neill Turner']
-  s.email         = ['neillwturner@gmail.com']
-  s.homepage      = 'https://github.com/neillturner/kitchen-puppet'
-  s.summary       = 'puppet provisioner for test-kitchen'
-  candidates = Dir.glob('{lib}/**/*') + ['README.md', 'provisioner_options.md', 'kitchen-puppet.gemspec']
-  s.files = candidates.sort
-  s.platform      = Gem::Platform::RUBY
-  s.require_paths = ['lib']
-  s.rubyforge_project = '[none]'
-  s.add_dependency 'test-kitchen', '~> 1.4'
-  if RUBY_VERSION >= '2.0'
-    s.add_dependency 'net-ssh', '~> 3'
-  else
-    s.add_dependency 'net-ssh', '~> 2.9'
-  end
-  s.description = <<-EOF
-== DESCRIPTION:
-
-Puppet Provisioner for Test Kitchen
-
-== FEATURES:
-
-Supports puppet apply, puppet agent, hiera, hiera-eyaml, custom facts, librarian-puppet, puppet collections (v4)
-
-EOF
-end
+# encoding: utf-8
+
+$LOAD_PATH.unshift File.expand_path('../lib', __FILE__)
+require 'kitchen-puppet/version'
+
+Gem::Specification.new do |s|
+  s.name          = 'kitchen-puppet'
+  s.license       = 'Apache-2.0'
+  s.version       = Kitchen::Puppet::VERSION
+  s.authors       = ['Neill Turner']
+  s.email         = ['neillwturner@gmail.com']
+  s.homepage      = 'https://github.com/neillturner/kitchen-puppet'
+  s.summary       = 'puppet provisioner for test-kitchen'
+  candidates = Dir.glob('{lib}/**/*') + ['README.md', 'provisioner_options.md', 'kitchen-puppet.gemspec']
+  s.files = candidates.sort
+  s.platform      = Gem::Platform::RUBY
+  s.require_paths = ['lib']
+  s.rubyforge_project = '[none]'
+  s.add_dependency 'test-kitchen', '~> 1.4'
+  if RUBY_VERSION >= '2.0'
+    s.add_dependency 'net-ssh', '~> 3'
+  else
+    s.add_dependency 'net-ssh', '~> 2.9'
+  end
+  s.description = <<-EOF
+== DESCRIPTION:
+
+Puppet Provisioner for Test Kitchen
+
+== FEATURES:
+
+Supports puppet apply, puppet agent, hiera, hiera-eyaml, custom facts, librarian-puppet, puppet collections (v4)
+
+EOF
+end