Hi, We are trying to use a custom fact to tell us the version of our service in order to do hot deployment. The idea is that we poll mco for servers with this fact matching the new version until it returns that there are some, which is a signal we can move on to the next server.
Unfortunately we're bumping into the cache of facts mentioned in the server config here: http://docs.puppetlabs.com/mcollective/reference/basic/configuration.html For reasons it would be tedious to explain we can't directly control the fact cache configuration value. Is there any way dynamically to tell mco to flush the cache, either for all facts or this one fact? Or to use a different cache value for a particular fact? Thanks for any advice, Rob -- ------------------------------ This email was sent by a company owned by Pearson plc, registered office at 80 Strand, London WC2R 0RL. Registered in England and Wales with company number 53723. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
