Puppet users - Oct 2014 - Using r10k to deploy production. How to setup a local dev environment for modules?

Hi,

We're using r10k with a 'control' repo to deploy to our production
server
following Gary Larizza's excellent series 
<http://garylarizza.com/blog/2014/03/07/puppet-workflow-part-3b/> workflow
with r10k. Our current workflow requires engineers to commit changes to the 
repo on a feature branch which is then deployed to a test environment using 
r10k. They are unable to test changes locally before making a commit as 
they don't have a local development puppetmaster. We'd like to implement
a
local dev environment using VM's and vagrant. 

Our aim is to allow a developer to spin up a local development environment 
that has a puppetmaster VM and multiple puppet clients for testing. The 
developer should be able to test changes locally before committing changes 
for the live test environment. To spin up the environment we expect to 
build a puppetmaster VM that will be deployed as a vagrant box. This box 
will be more or less a generic puppetmaster without any of our manifests 
installed. The developer would then run some scripts to clone the
'control'
repo and checkout the repo's in the Puppetfile. We can't use r10k to 
checkout the modules in the Puppetfile as we need each individual module 
cloned so developers can work on each module. Is the only solution to 
manually clone each module in the Puppetfile?

Any advice on how local development environments are being used with r10k 
in production would be much appreciated!

Jeremy.

-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscribe@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/bdcd73e3-4e04-48f0-98e9-e483aedbdf6b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.