Cucumber-Puppet

• silence a rake warning with newer rake

• fix #10851 by adding support for puppet 2.7.6

• move puppet gem dependency to development dependencies, as not everyone uses the puppet gem, noticed by Hai Wu

• improve error logging in case of catalog compilation failure

Version 0.3.3 introduced error handling to the compilation step, so one could test for expected compilation failure. As this turned out to hinder debugging the regular case, where compilation failed unexpectedly, I restored the old behaviour of When I compile its catalog to throw an error and output an error message. To test for expected compilation failures, use the new step When I try to compile its catalog.

• fixed #9000 by adding support for puppet 2.7 series
• add support for inclusion of multiple classes per node, from Oliver Hookins
• from Matthaus Litteken
  • add support to test for failed compilation
  • add support for booleans in parameterized classes
  • add support for arrays, content with newlines, Puppet::Resource objects

Fixed #8431 by changing the way cucumber is called from inside cucumber-puppet and cucumber-puppet is called from its rake task.

It is no longer necessary to have either program in your PATH.

0.3.0 adds a more flexible way to specify puppet configuration options as submitted by mfournier (https://github.com/mfournier)

Old way in hooks.rb:

@confdir = '/etc/puppet/'
@manifest = /etc/puppet/manifests/site.pp'

New way in hooks.rb:

@puppetcfg['confdir'] = ...

You can set any puppet command line option this way.

• fixed #5895 by adding support for parameterised classes

• fixed #5066 by adding support for resource aliases

I just released cucumber-puppet 0.1.0.

New features:

• support for puppet 2.6
• generate a catalog policy with cucumber-puppet-gen policy

See wiki for a detailed explanation of catalog policies and how to use them.