Yeah. It wasn't a fully baked idea, I'd imagined that there was similar, but not identical support in osx/solaris/windows, but didn't poke to see what they looked like.
The advantage of tying into something OS level would be the ability to tell other pieces of software something relevant to them (and having a chance of getting them to listen) The metadata could be stored in a known location on the local fs, and then lookups could be run against that… seems like generating and storing that file on the node every run wouldn't cost much.. or add too many extra iops as the number of files managed grew.. but would it be beneficial at all? Would other configuration management softwares even be interested in collaboratively establishing a mechanism for politely and efficiently conveying each other's presence? would softwares be willing to check for the existence of that db and if it's there, parse thru it? dunno. -- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/puppet-dev?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
