Issue #16856 has been updated by R.I. Pienaar.
> TL;DR, I don't wish to integrate in-module hiera data into the modulefile. > > You have stated in the past that you (I'm paraphrasing) expect in-module data > to allow module consumers to more easily contribute patches upstream that > support additional operating systems. Cool. > > The Modulefile/metadata.json files are the authors expression of module > metadata that allow them to publish to the Forge. It's only meant for their > manipulation and it's critical to the operation of Forge and the module tool. > If we store hiera data in this file, we're introducing a use-case for the > consumer to manipulate this file. If they decide to carry a patch locally or > their submitted patch isn't accepted upstream, now you cannot upgrade your > module without resolving the conflict in the modules metadata. This doesn't > seem optimal. If all we're buying is reducing the number of files that make > up a module, I don't think it's worth it. Instead, I suggest that you go with > another file or folder/file structure for this purpose. We weren't suggesting storing *data* in this file, only the hierarchy description. In the most common case people contributing to the module would not edit the modulefile they'd just add data. I agree though - overloading the modulefile for different purposes is not desirable though I am not bothered personally where this stuff goes. ---------------------------------------- Feature #16856: puppet should support data in modules https://projects.puppetlabs.com/issues/16856#change-89049 * Author: R.I. Pienaar * Status: Needs More Information * Priority: Normal * Assignee: eric sorenson * Category: * Target version: * Affected Puppet version: * Keywords: * Branch: https://github.com/puppetlabs/puppet/pull/1217 ---------------------------------------- At present there is a way to store data in modules using the puppet backend for hiera but it is optional and kind of broken. The site hierarchy impacts how the puppet backend behaves which makes it impossible for module authors to supply data in their modules they can rely on I propose a new hiera backend that loads a hierarchy of data from the 'data' directory in the module, this module must always be present in a puppet install. This ability is key to the ability to create configurable forge modules that do not have hard coded values thanks to the puppet 3 hiera integration reference the users list thread https://groups.google.com/d/topic/puppet-users/pvqzeyHkrY4/discussion -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" 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-bugs?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
