commit | 9c4653a07172d96e80d475f41fb5d8fd3b524a9d | [log] [tgz] |
---|---|---|
author | Geoffrey Corey <geoffcorey7@gmail.com> | Thu Nov 05 11:06:15 2015 -0800 |
committer | Geoffrey Corey <geoffcorey7@gmail.com> | Thu Nov 05 11:06:15 2015 -0800 |
tree | 9d734bd1d0602856726a6f2d539b548f1bd48765 | |
parent | 9e84db8f87eb371dbe54835315124565df179946 [diff] |
Update .kitchen.yml to what I currently use
Test Kitchen + Puppet
git clone https://github.com/apache/infrastructure-puppet
gem install bundler bundle install
mkdir -p $puppet-kitchen-root/puppet/modules cd puppet/modules for i in $(ls <path to infra-pupet 3rdParty>); do ln -s <path to infra-puppet 3rdParty>/$i ./; done for i in $(ls <path to infra-puppet modules>); do ln -s <path to infra-puppet modules>/$i ./; done
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.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 option work with puppet, however make sure to see the kitchen-puppet documentation (even though the explanations aren't nearly as detailed as it needs to be).
Most information has been taken from here