Jira (PDB-4895) Use top level hash to check catalog inputs submission

[Austin Blatt (Jira)]

Austin Blatt created an issue

PuppetDB / PDB-4895 Use top level hash to check catalog inputs submission Issue Type: New Feature Assignee: Unassigned Created: 2020/09/15 11:29 AM Priority: Normal Reporter: Austin Blatt Add Comment

This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)

[Austin Blatt (Jira)]

Austin Blatt updated an issue

PuppetDB / PDB-4895 Use top level hash to check catalog inputs submission

Change By: Austin Blatt Most of the time, the hiera inputs of a catalog won't have changed because it requires a user to commit a change to the control repo. We should hash the entire set, store that hash in the {{certnames}} table and check that to identify _if_ there's anything that has changed before we go through the expense of storing a new set of inputs.

Add Comment

[Austin Blatt (Jira)]

Austin Blatt updated an issue

PuppetDB / PDB-4895 Use top level hash to check catalog inputs submission

Change By: Austin Blatt Acceptance Criteria: - database migration to add column to certname - hash & check that the content of catalog inputs has changed before storing the new set Release Notes: New Feature

Add Comment

[Austin Blatt (Jira)]

Austin Blatt assigned an issue to Austin Blatt

PuppetDB / PDB-4895 Use top level hash to check catalog inputs submission

Change By: Austin Blatt Assignee: Austin Blatt

Add Comment

[Rob Browning (Jira)]

Rob Browning updated an issue

PuppetDB / PDB-4895

Use top level hash to check catalog inputs submission

Change By: Rob Browning Issue Type: New Feature Improvement

Add Comment

[Rob Browning (Jira)]

Rob Browning updated an issue

PuppetDB / PDB-4895 Use top level hash to check catalog inputs submission

Change By: Rob Browning Release Notes Summary: Most of the time, the hiera inputs of a catalog won't have changed because it requires a user to commit a change to the control repo. We should hash the entire set, store that hash in the certnames table and check that to identify if there's anything that has changed before we go through the expense of storing a new set of inputs.

Add Comment

[Rob Browning (Jira)]

Rob Browning updated an issue

PuppetDB / PDB-4895 Use top level hash to check catalog inputs submission

Change By: Rob Browning Release Notes Summary: Most of PuppetDB can now detect when the time, the hiera inputs of in a catalog won't have not changed because it requires a user with respect to commit a change to the control repo. We should hash the entire set previous catalog , store that hash in the certnames table and check that to identify if there's anything that has changed before we go through the expense of avoid storing a new set of inputs them again . Team: HA

Add Comment

[Rob Browning (Jira)]

Rob Browning updated an issue

PuppetDB / PDB-4895 Use top level hash to check catalog inputs submission

Change By: Rob Browning Story Points: 2

Add Comment