[PDB-4371] Add initial support for catalog input related queries Created: 2019/05/14  Updated: 2019/08/16  Resolved: 2019/08/14

Status: Closed
Project: PuppetDB
Component/s: None
Affects Version/s: None
Fix Version/s: PDB 6.5.0

Type: New Feature Priority: Normal
Reporter: Rob Browning Assignee: Rob Browning
Resolution: Fixed Votes: 0
Labels: resolved-issue-added
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Blocks
blocks PDB-4455 Add support for syncing catalog inputs Resolved
blocks PDB-4456 Add support for import/export for "re... Resolved
blocks PDB-4464 SPIKE - investigate performance of hi... Closed
is blocked by PDB-4370 Adjust storage to accommodate catalog... Resolved
Template:
Epic Link: Add initial support for hiera impact analysis
Team: PuppetDB
Release Notes: New Feature
Release Notes Summary: An experimental
[`catalog-input-contents`](./api/query/v4/catalog_input_contents.markdown)
endpoint has been added. It allows querying for the most recent
catalog inputs that PuppetDB has received for any nodes.
([PDB-4371](https://tickets.puppetlabs.com/browse/PDB-4371)
QA Risk Assessment: Needs Assessment

 Description   

At a minimum, we need some query that can return a list of certnames whose catalogs mention any one of a provided set of inputs. Where this should end up hasn't been determined yet.

Inputs may also be returned under a new optional key in the catalog response. Whether or not we'll want/need to make that field opt-in is as yet undetermined, but our versioning policy does require clients to ignore unexpected new fields, so we're not obligated to make it opt-in, nor to increment the endpoint versions, and adding it to the catalog response means we wouldn't have to adjust sync or import/export.


Generated at Thu Jul 16 11:23:08 PDT 2020 using Jira 8.5.2#805002-sha1:a66f9354b9e12ac788984e5d84669c903a370049.