Hi, > I confess that I find it a bit strange, however, that you want to > separate module data so completely from the rest of the module while > using Hiera's Puppet backend. It runs rather against the idea of > modules as self-contained entities. Even with the YAML backend I > might expect module-specific data to be located within modules' own > directory tree. It's a good idea to separate data from declarations, > but I'm not so keen on pulling the data entirely out of its context.
Yes... I guess it's a weird case of module, since it's not going to be included by any class, but still has the syntax of a module. I consider it more like the YAML tree, that sits completely outside of the modules (with an addition... you can use conditionals!!!). I would rather organize the tree following the logic more than the syntax. Also, if I extend the module path, I will have to either: - include /etc/puppet/manifests as a module path, which is probably not a good idea - or create an additional level on the tree: /etc/puppet/manifests/data/data/, which is ugly. I feel better using the manual import, or globbing, if this becomes too big. Thanks for the hints! Pablo -- 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.
