Issue #5784 has been updated by Daniel Pittman. Assignee deleted (Daniel Pittman)
---------------------------------------- Feature #5784: Support 'audit' on a machine without any 'agent' run... https://projects.puppetlabs.com/issues/5784#change-92415 * Author: Daniel Pittman * Status: Closed * Priority: Normal * Assignee: * Category: auditing/compliance * Target version: * Affected Puppet version: * Keywords: * Branch: ---------------------------------------- The single biggest use of the audit feature I can identify would be to see what puppet would start managing on those nasty, terrible legacy machines that I still have to support for a bunch of years - before I allow the agent to do any darn thing on the machine. So, my expected use-case would be: 1. Write up the manifest establishing our baseline configuration and host-specific stuff. 2. Run puppet audit to identify how the machine diverges. 3. Identify where those mismatch unexpectedly (ideally, close to zero.) 4. Fix those in the manifests, return to 2, until I am happy. 5. Run puppet agent to apply those changes. This is absolutely, totally a wonderful thing: previously we had to do all sorts of scary things to migrate those machines in, and this early visibility would be a huge bonus. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" 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 http://groups.google.com/group/puppet-bugs?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
