hello,

> A new configuration option, config_version, is now available:
> 
> config_version = /usr/local/bin/return_version
> 
> The option allows you to specify a command that returns a version
> for the configuration that is being applied to your hosts. The
> command should return a string, such as a version number or name.
> 
> Puppet then runs this command at compile time. Each resource is
> marked with the value returned from this command. This value is also
> added to the log instance, serialised and sent along with any report
> generated. This allows you to parse your report output and ascertain
> which configuration version was used to generate the resource.


I don't think this is working too hot, if i set it to:

config_version = /bin/date

it works, i get the message:

info: Applying configuration version 'Sat Oct 10 17:53:33 BST 2009'

If i set it to a script - bash script, executable by puppet user etc - that 
runs /bin/date i get '' 

But that aside, I question the usefulness - reports getting tagged with this 
information, that's just not happening in a way thats useful at all, the only 
place where this shows up is in Puppet::Util::Log instance for the line above 
and its in the middle of the string in a way that hard to get it out.

See http://pastie.org/649615 for such a report.

Much more useful would have been say a property on the main 
Puppet::Transaction::Report object for the version applied, or even just in 
syslog if the logs would get tagged with this on each log entry since the 
'Applying configuration version' message above only show up in for example 
--test not in normal use.

I think it has potential for being useful.  For instance if I've just pushed 
out a new revision of my code I might wait 30 minutes and quickly run through 
the last reports received and check the version property and report any 
machines that dont have the new code, or my reporting app could checks whats 
the manifest revision and report on any nodes not yet on that version.  

The current implimentation force us to do this by running through an array of 
Puppet::Util::Log objects and doing regex matching on the 'message' property - 
that just isn't useful.
-- 
R.I.Pienaar

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to