Add a fact that's derived from parsing /var/lib/puppet/state/classes.txt. It will be exactly one run behind, but it will have the complete list of classes as of the previous run and it's reliable.
On Feb 3, 2011, at 9:58 AM, Richard Crowley wrote: > On Thursday, February 3, 2011 at 9:53 AM, Adam Gibbins wrote: > >> Hi All, >> I'm trying to implement a template (for my collectd config) that gives >> different results depending on the other modules included on that machine. >> I tried to do this by checking for the class tags but it turns out that due >> to bug #3049 this is a huge pain and 90% of the time the tags aren't >> registered by the time the template is parsed so I don't get my expected >> result. > Use multiple collectd configuration files if you possibly can. Then each > class can manage its own little corner of collectd. Putting > > Include "/etc/collectd.d/*.conf" > > in your main /etc/collectd.conf should make this possible if it isn't by > default. > > Rich > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" 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-users?hl=en. -- You received this message because you are subscribed to the Google Groups "Puppet Users" 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-users?hl=en.
