Hello, We have some cases where first line support staff etc could manage low level changes via the Foreman UI using Smart Class Parameters.
Right now, all our Puppet code is version controlled via GIT and etckeeper. This is a very basic setup but has suited our needs so far (I'd be happy to rework this setup). How can I incorporate a level of 'version control' if I start using Smart Class Parameters? A simple example being... Lets say I give our monitoring team the ability to manage nrpe.cfg for Nagios using Smart Class Parameters in the Foreman UI. The monitoring team would be allowed to override the default values and manipulate strings in the Puppet managed nrpe.cfg (updating nagios checks, allowed hosts etc). How could we roll back a change to the Smart Class Parameters if required? Say perhaps our monitoring team made some changes to nrpe.cfg but decided they want to roll back the changes to the known good state. Is there a way of doing this? Right now, the UNIX team apply and manage the changes to nrpe.cfg from CLI on the Puppet Master (we leave the 'nrpe' module assigned to our Host Groups in Foreman). This allows the UNIX team to version control the changes (they can easily roll back to a known good version if needed) I think Smart Class Parameters could offer some huge benefits buy opening up access to other technical groups, but we'd need some level of version control before implementing it. Any advise, thoughts welcome. Ta, -- You received this message because you are subscribed to the Google Groups "Foreman users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout.
