Display in a machine-readable form all the changes that have been performed
|Affected Puppet version:||0.25.0||Branch:|
Add a parameter to puppetd that permit to see what changes that has been made, for example :
puppetd --server cors002.ocre.cea.fr --changes --no-daemonize --onetime File: file_changed: /etc/munge (2) Package: package_installed: munge package_installed: slurm-munge Service: service_started: munge
#2 Updated by Luke Kanies almost 4 years ago
- Subject changed from Display all the changes that have been performed to Display in a machine-readable form all the changes that have been performed
- Category set to transactions
- Status changed from Unreviewed to Accepted
I’m working on something like this right now. Basically take all of the internal events, include them in the reports, and also provide a means of displaying them in yaml or something.
#3 Updated by Stéphan Gorget almost 4 years ago
I’ve already done things like this, http://groups.google.fr/group/puppet-dev/browse_thread/thread/919d230fc9e4727c, that print the output I past and send the changes in YAML through the report.
I have also written a YAML parser in python that runs on server side and parse the YAML, a classical output look like this :
./puppet-monitor ./examples/*.yaml [cors[005-008,010].ocre.cea.fr] Service: service_started : slurm File: file_changed : /root/os.txt (2) Package: package_installed : openmpi package_installed : openmpi-devel [cors006.ocre.cea.fr] Service: service_started : slurm (2) service_started : munge
With cron you can trigger it and send mail when the output is not null so that I can see if the configuration is drifting.