2009/10/7 Luke Kanies <[email protected]>: > > On Oct 6, 2009, at 1:00 PM, James Turnbull wrote: > >> > It's very straightforward - you provide a command in the > 'config_version' setting, and Puppet runs that command at compile time > to determine the config version. This version then gets attached to > the catalog and, by extension, to all resources. When these resources > create logs, the version is attached to the log instances (not in > syslog, but the actual objects in memory, which get serialized and > sent in the report to the server).
So each resource is tagged with this "version"? > So, basically, you now have a way to correlate every log message you > receive to a specific configuration version. You just have to define > what 'configuration version' means to you. Is "version" expected to be in some format? Any restricted characters, etc? > If you don't provide a command, then the compile time is used. What if the command fails? Regards James Turnbull -- Author of: * Pro Linux Systems Administration (http://tinyurl.com/linuxadmin) * Pulling Strings with Puppet (http://tinyurl.com/pupbook) * Pro Nagios 2.0 (http://tinyurl.com/pronagios) * Hardening Linux (http://tinyurl.com/hardeninglinux) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Developers" 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-dev?hl=en -~----------~----~----~----~------~----~------~--~---
