commit | 00018d435830b21f04a0ad8d38c74bd7ea1546d0 | [log] [tgz] |
---|---|---|
author | Geoffrey Corey <geoffcorey7@gmail.com> | Thu Jan 15 11:44:30 2015 -0800 |
committer | Geoffrey Corey <geoffcorey7@gmail.com> | Thu Jan 15 11:44:30 2015 -0800 |
tree | d9f608fdb2cf34b47ad91b4f5083be17e3840af7 | |
parent | f373cdffbcf4785efaeed4aca6124f74e06d5e87 [diff] |
Stop downloading chef Since the testing part of test kitchen is not being used, stop downloading and installing chef.
Test Kitchen + Puppet
gem install bundler bundle install
Make sure to have some puppet modules in the puppet/modules/
directory. The current hiera setup assumes you have the following modules:
If using GitHub to obtain modules, make sure when you clone the module, it only has the module name on the resulting folder. Example:
git clone https://github.com/puppetlabs/puppetlabs-apt.git apt
Then edit puppet/data/node/default-ubuntu14.vagrantup.com.yaml
to start adding classes and setting class parameters.
When you're ready to test, just run:
kitchen converge default
This will bring up a vm, run puppet apply. From there, you can continue writing your puppet module (in puppet/modules/$module
) and testing by running the above command.
Most the the test-kitchen work with puppet, however make sure to see the kitchen-puppet documentation (even though the explanation isn't nearly as it needs to be).
Most information has been taken from here