Hello!
I stumbled across
http://projects.puppetlabs.com/projects/1/wiki/Change_Management today
but I couldn't find any newer version in the new wiki.
As I am currently facing changes which could cause problems in existing
infrastructure I would like to implement some approval concept on a per
resource or module basis.
For now I am going with a define called "featurebit" which checks on a
global variable in the ENC and then includes the "real" class but I
don't think this is a good solution (I'd prefer something like the
"approved" function as mentioned on the wiki page) and running the hosts
via cron on a regular basis in noop mode.
If someone knows about best practices can you please give me some
directions where I could go or what approach would fit better to my
needs?
I also thought about some meta class that would set a default for every
possible Ressource to be noop but that would be just insane ;-)
Thanks for your help in advance!
Cheers
Hannes
--
You received this message because you are subscribed to the Google Groups "Puppet
Users" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
