Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
16856 - Add a module data directory and hiera backend to consume it #1217
While hiera does a decent job of separating code and data for users
With this commit we add a new module_data backend that loads data from
The goal of this backend is to allow module authors to specify true
This backend is always loaded as the least important tier in the
Given a module layout:
The hiera.yaml is optional in this example it would be:
But when no hiera.yaml exist in the module, the default would be:
The data directory is then a standard Hiera data store.
My understanding is that this pull request doesn't address all the requirements for hiera data in modules, per the conversation in the redmine ticket (http://projects.puppetlabs.com/issues/16856). I'm closing this pull request for the time being until these things get resolved so we don't have stale/forgotten pull requests. Thanks!