We have embraced Hiera; we use the YAML configuration system currently and on the whole everyone finds it easy to use and intuitive.
However, as our manifests have grown more complex, we have a need to "compile" multiple narrowly-focused classes together into different types of high-level roles. For example, we might have a "webmail" class that pulls together classes for configuring Apache, PHP, etc. The low-level classes look to hiera for various configuration options -- e.g. Apache might look to Hiera for values on configuring server tokens or enabling the enhanced status or SSL information, PHP might want to check for security-related options configured, etc. Ideally, we would like to expose simple values in the YAML file: (e.g.) --- webmail.use_https: true Which gets translated into various "apache.*" configuration options. We don't want to make operators learn all the small levers that need to be tweaked in the individual components in order to make the system function together. (I apologize if this particular example doesn't make much real-world sense; this is somewhat contrived.) I don't think there's a way to set Hiera options, right? (I haven't seen one; we're on Puppet 2.7.x, so maybe newer Puppet does this differently?) We could maybe use parameterized classes, but we are currently heavily reliant on the "singleton" guarantee with multiple includes. Am curious how/whether others address this problem of abstracting configuration and using composition pattern to bring together small classes into sophisticated functionality? Thanks in advance! Hans -- 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. For more options, visit https://groups.google.com/groups/opt_out.
