Jira (PUP-7999) Puppet Lookup should be easily used as a library in other applications

Past Haus (JIRA)

unread,

Sep 27, 2017, 4:13:02 PM9/27/17

to puppe...@googlegroups.com

Past Haus created an issue

Puppet /

PUP-7999

Puppet Lookup should be easily used as a library in other applications

Issue Type:	Improvement
Affects Versions:	PUP 5.0.0
Assignee:	Thomas Hallgren
Components:	Hiera & Lookup
Created:	2017/09/27 1:12 PM
Priority:	Normal
Reporter:	Past Haus

Currently in PE, the pe_infrastructure and pe_manager modules end up recreated a large amount of the puppet lookup application logic to do lookups without shelling out to puppet (which would be expensive). It would be far better if puppet itself exposed the lookup as an easy to use method for other applications. Ideally, if I knew the node name, environment name, and a list of keys to lookup, I should be able to invoke the method to retrieve those lookups.

Add Comment

This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)

Henrik Lindberg (JIRA)

unread,

Sep 28, 2017, 4:47:02 PM9/28/17

to puppe...@googlegroups.com

Henrik Lindberg commented on

PUP-7999

Re: Puppet Lookup should be easily used as a library in other applications

We have been working on the Puppet::Pal API ("Puppet as-a Library) for the purpose of making it easy to do "puppety" things with a degree of separation between the caller and "puppet". We could add "lookup" to that API as well. The API already has various ways to define the environment and node to operate on.

With lookup in general, there is the question if such an API should return the exact same values as would be looked up during compilation, or/and if it should be possible to also give it a separate hierarchy for other purposes than "compiling for a node".