Issue #16856 has been updated by Andrew Parker.
R.I. Pienaar wrote: > > When the module author wants to add another Operating System or update an > existing OS he'd only change the data files, this is significant because: > > [snip] > * I found while deploying modules configurable by data and not code in large > environments with complex change control requirements that changes to > configuration data required less change control than changes to case > statements. In some cases we even got agreement to not require any code > review on data changes. In any event the change review process is easier if > all you have to consider is data changes and no logic changes. Aha! I think you've identified the new use case that all of the present ways of doing this cannot handle. In the case where an organization makes a distinction between data in the code and the code itself having this kind of separation can be an immense help. Given this, then I agree with the basic idea of the feature. I'm still not too happy with the way it is implemented right now in the pull request, but as you pointed out in one of the comments there, a lot of that is related to just the current structure of hiera. > [snip] > Doing this in a way that is consistant with the design of the already present > hiera enhances the overall solution and get us nearer to the point of having > a single way to handle data thats adopted by a majority of the community and > I believe ultimately to a better forge eco system. I agree that this would enhance the integration with hiera that was started with the inclusion of data bindings for parameterized classes. Would still like to get an idea of where exactly we are trying to take all of this so that we aren't just blowing from one feature to the next without a larger plan, but that concern is beyond this one ticket. ---------------------------------------- Feature #16856: puppet should support data in modules https://projects.puppetlabs.com/issues/16856#change-79158 Author: R.I. Pienaar Status: Needs More Information Priority: Normal Assignee: R.I. Pienaar 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 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-bugs?hl=en.
