On Oct 6, 2009, at 2:47 PM, James Turnbull wrote: > > 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"?
Yes, although it's an attribute, not a tag. > >> 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? Nope; opaque string. > >> If you don't provide a command, then the compile time is used. > > What if the command fails? Erm. Bad stuff? -- Ninety-eight percent of the adults in this country are decent, hard-working, honest Americans. It's the other lousy two percent that get all the publicity. But then--we elected them. --Lily Tomlin --------------------------------------------------------------------- Luke Kanies | http://reductivelabs.com | http://madstop.com --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
