[PUP-1157] puppet should support data in modules Created: 2013/12/17  Updated: 2019/04/04  Resolved: 2016/01/04

Status: Closed
Project: Puppet
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: New Feature Priority: Normal
Reporter: redmine.exporter Assignee: Unassigned
Resolution: Duplicate Votes: 27
Labels: customer, redmine
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Blocks
is blocked by PUP-1640 Provide agnostic mechanism for Hiera ... Closed
Duplicate
duplicates PUP-4474 Complete the lookup, "data in modules... Closed
Relates
relates to PUP-1640 Provide agnostic mechanism for Hiera ... Closed
Template:
Epic Link: Data in Modules
QA Contact: Kurt Wall

 Description   

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



 Comments   
Comment by Alexander Pánek [ 2014/05/06 ]

Has there been any more recent work on this subject, or are there any plans for Puppet 4 in this regard?

Comment by Damon Atkins [ 2014/09/08 ]

+1 Private Data in modules. e.g. Instead of if this OS then set this multiple page case statement.

Comment by Amos Shapira [ 2014/11/30 ]

PUP-1640 addresses the same requirement.

Comment by Henrik Lindberg [ 2014/11/30 ]

Amos Shapira thanks for pointing to PUP-1640 - that ticket is about the mechanism that makes it possible to plugin technology for automatic data lookup from both modules and directory environments - it comes with one implementation that supports functions. The function support may be sufficient for many module author's needs, but it is also expected that there will be other implementations made by the community.

Comment by Henrik Lindberg [ 2015/04/29 ]

PUP-4474 is the new Epic targeting Puppet 4.2.0 (replacing the old attempt to implement this described in the epic PUP-42).

Comment by Jo Rhett [ 2016/01/03 ]

In the interest of closing old issues, this functionality is now available and seems to work as documented at https://docs.puppetlabs.com/puppet/latest/reference/lookup_quick.html

Perhaps we can close this issue?

Comment by Henrik Lindberg [ 2016/01/04 ]

Jo Rhett, yes, thanks - I will close this.

Comment by Henrik Lindberg [ 2016/01/04 ]

Closed as duplicate of ticket PUP-4474 (as that is the Epic that best describes what is already implemented and what remains.

Generated at Fri Oct 18 01:21:30 PDT 2019 using JIRA 7.7.1#77002-sha1:e75ca93d5574d9409c0630b81c894d9065296414.