I do. Although rather than use environments we have a number of different
puppetmasters, one per location (which is a logical collection of
servers for us) and puppet changes get pushed from staging to live in
the same way as everything else does in our workflow. But with even more
scrutiny ;)
In theory that catches any puppet issues in my personal dev environment or
early staging and way before they could break production. Anything that
slips through is my own fault for not testing it enough.
Makes sense, and I think that's the route we're going to take, too
(separate puppet masters for our dev environment versus having different
environments on a single puppet master - we want to keep testing
completely separate).
However, don't you have concerns that a change could get introduced to
your puppet config that would cause your puppetmaster to have issues?
This is why I'm leaning towards not regulating my puppetmaster with
puppet (as I make the same decision to not have my LDAP server
authenticate with LDAP). It's kind of the chicken + egg problem, no?
--
You received this message because you are subscribed to the Google Groups "Puppet
Users" group.
To post to this group, send email to puppet-us...@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.
