On Jan 31, 2011 9:10 AM, "James Turnbull" <ja...@puppetlabs.com> wrote:
> Pieter Baele wrote:
> > I would like to delegate access to puppet to other teams in our company.
> >
> > It has to be possible for them to:
> > - create new recipes
> > - doing some sort of check if their recipes / templates work.
> >
> > How should I do this without giving other teams the ability to create
havoc?
> >
>
> Version control potentially combined with Puppet environments works well
> for this.
At my previous job we did this: using a testing environment where the ops
team could proof the "code" beforevit went to production, combined with code
review worked at our scale.
All the changes ended up merged in by an ops team member; today, I would
probably use git and pull/merge from the other teams repo.
Once you start to trust the other teams not to blow too much up, I would
just trust them - but make sure the only route to production is through the
*immutable* VCS history, and that everyone knows that.
There is a lot of social encouragement not to blow things up when folks know
that every change they make can be unambiguously tracked back to them.
Regards,
Daniel
--
Puppet Labs Developer –http://puppetlabs.com
Daniel Pittman <dan...@puppetlabs.com>
Contact me via gtalk, email, or phone: +1 (877) 575-9775
Sent from a mobile device. Please forgive me if this is briefer than usual.
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
