Re: [Puppet Users] Testing a single module

2012-04-23 Thread Christopher Wood
In your situation I would set up a virtual machine on my laptop where I would merrily munge mail service at will. (Or a VM anywhere else for similar fun.) If you break something you can roll back to your known good snapshot and try again. On Mon, Apr 23, 2012 at 06:10:59AM -0700, James Patterson

Re: [Puppet Users] Testing a single module

2012-04-23 Thread James Patterson
Thanks for your reply. I do not have reliable access to an internet connection at the moment. Just to flesh out my problem a bit more: I need to update my sendmail module, but want to test it first. I have two puppet environments (dev and prod), but mail is critical in both. Ideally I would choose

Re: [Puppet Users] Testing a single module

2012-04-12 Thread Gary Larizza
James, If the modules are in your modulepath and environments are defined in puppet.conf, you can actually use puppet apply to declare classes from the command line. For example, if you just wanted to test the nginx::config class you could run: puppet apply -v -e 'include nginx::config' This (

[Puppet Users] Testing a single module

2012-04-12 Thread James Patterson
Hello, I have a production puppet environment that is working well. Now more people are developing modules for it we are using a test environment using environment=test in the puppet.conf file. This prevents changes to modules in the production environment being affected by changes in the test en