| commit | f4ba1a40058e7f3e1bc8e5b1880c9be312c57ca7 | [log] [tgz] |
|---|---|---|
| author | Matt Chu <matt.chu@gmail.com> | Thu Aug 21 14:12:42 2014 -0700 |
| committer | Matt Chu <matt.chu@gmail.com> | Thu Aug 21 14:12:42 2014 -0700 |
| tree | 24bb1ec265157d4c611f6009a78593d7c37897c2 | |
| parent | 869365b2f79e341028360ce9ff71880b5d9c79df [diff] |
add step_into during chefspec tests to correctly test custom resources
Chef cookbook for installing Continuum Analytic's Anaconda: "completely free Python distribution for large-scale data processing, predictive analytics, and scientific computing".
This also serves as a live example of the most up-to-date best practices for writing, maintaining, and testing Chef cookbooks:
This repo has only been tested with RVM; YMMV with other installation methods (rbenv, chef-dk, etc).
>= 2.0.1 is requiredIt sounds like Chef-DK is the new recommended installation path, but I have not had a good experience with it (as of 0.1.0-1). Again, YMMV.
The Vagrantfile is written to get you an Anaconda environment with minimal effort:
$> vagrant up --provision ... $> vagrant ssh $vagrant> export PATH=/opt/anaconda/2.0.1/bin:${PATH} $vagrant> conda --version conda 3.5.5 # if you included `recipe[anaconda::shell_conveniences]` you don't have to do anything; # it's sourced in /etc/profile.d $> vagrant ssh $vagrant> conda --version conda 3.5.5
To use it in a cookbook:
include_recipe 'anaconda::default'
The main recipe is anaconda::default. Include it in your runlist, and it will install the package as well as any necessary dependencies.
The following are user-configurable attributes. Check attributes/default.rb for default values.
anacondaversion: the version to installflavor: either x86 (32-bit) or x86_64 (64-bit)install_root: the parent directory of all anaconda installs. note that individual installs go into #{install_root}/#{version}accept_license: must be explicitly set to the string yes; any other value will reject the license.owner: the user who owns the installgroup: the group who owns the installrecipe[anaconda::shell_conveniences]Include this to have the environment set for all users (login shells) via /etc/profile.d. Useful for development.
$> vagrant ssh $vagrant> which conda /opt/anaconda/2.0.1/bin/conda
anaconda_packageYou can use the anaconda_package resource to install new packages into the Anaconda environment:
# I do not know what 'astroid' is, just using it as a sample package anaconda_package 'astroid' do # the other supported action is `:remove` action :install end
See the resource definition for additional options; in general, all it does is present the same options as conda install/conda remove.
Run the full test suite:
# this will take a really long time $> script/cibuild ... # check the final result; bash return codes: 0 is good, anything else is not $> echo $?
Run just the chefspecs:
$> rspec
Run just the test kitchen serverspec integration tests:
# this is what takes so long: every platform and version is fully built in vagrant # the list of OSes is defined in [.kitchen.yml](.kitchen.yml) $> kitchen verify # test a specific OS; `kitchen list` $> kitchen verify default-ubuntu-1204
Check the style with Foodcritic:
$> foodcritic
Standard stuff:
git tag'edIssues should be opened in the Github issue tracker
suggests, supports, etcAuthor:: Matt Chu (matt.chu@gmail.com)