I'd like to look at improving facter to get to a 2.0 and want to think about getting volatile/dynamic facts working properly. To fix issues such as:
http://projects.reductivelabs.com/issues/show/1365 http://projects.reductivelabs.com/issues/show/1424 We were thinking about namespacing with an _ for collections such as interfaces and registering a dynamic fact type. Particularly when running in a long running process such as puppet, we have some static facts across the process lifetime which are unlikely to change - kernel version springs to mind as an obvious one. Others such as ip addresses may be volatile on different systems but static Is it worth branching the main facter repo for dev and for basic bug fixes for 1.5 series now? Paul --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
