At work we try, and sometimes even succeed, in using Test Driven Deployment so as one of my background projects I’ve been wrapping certaintools in to cucumber friendly forms. Over the last couple of days I’ve been grabbing ten minutes here and there to incorporate Puppet 2.6 in to the pile.
Feature:Puppetwrappers Puppet Provider Examples Scenario:Confirming package installation When a machine has been puppeted Then the bash package should be installed Scenario:Confirm doodoodoo package is absent When a machine has been puppeted Then the doodoodoo package should not be installed Scenario:Confirm cron service is running When a machine has been puppeted Then the cron service should be running Scenario:Confirm tomcat6 service is not running When a machine has been puppeted Then the tomcat6service should not be running Scenario:Confirm dwilson is in libvirtd group When a machine has been puppeted Then dwilson should be a member of libvirtd Scenario:Confirm dwilson has a uid of 1000 When a machine has been puppeted Then dwilson should have a uid of 1000Scenario:Confirm dwilson has a given shell When a machine has been puppeted Then dwilson should have the /bin/bash shell I really like using the puppet providers for this because of the abstraction benefits they provide.
↧
