Jira (PDB-4370) Adjust storage to accommodate catalog inputs

Rob Browning (JIRA)

unread,

May 14, 2019, 5:25:03 PM5/14/19

to puppe...@googlegroups.com

Rob Browning created an issue

PuppetDB /

PDB-4370

Adjust storage to accommodate catalog inputs

Issue Type:	New Feature
Assignee:	Unassigned
Created:	2019/05/14 2:24 PM
Priority:	Normal
Reporter:	Rob Browning

Add Comment

This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)

Rob Browning (JIRA)

unread,

May 14, 2019, 5:41:03 PM5/14/19

to puppe...@googlegroups.com

Rob Browning updated an issue

PuppetDB /

PDB-4370

Adjust storage to accommodate catalog inputs

Change By:	Rob Browning

For now, by catalog input, we mean one of the following items that might influence a given catalog:

- heira key: string (name)
- function: string (name)
- template: string (name)

Though for the first pass, we may or may not need all of these.

One storage option would be a new catalog_inputs table recording [certname_id type name] for each input. There may also be some details to work out regarding timestamps ([~zachary.kent] and/or [~rob.browning] have been discussing the issues).

As far as lifetime goes, the inputs should be tied to the certname, not to a given catalog, and should behave like facts (expiring, etc. with the certname).