Uploaded image for project: 'PuppetDB'
  1. PuppetDB
  2. PDB-4895

Use top level hash to check catalog inputs submission

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Resolved
    • Priority: Normal
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: PDB 6.12.1
    • Component/s: None
    • Labels:
      None
    • Template:
    • Acceptance Criteria:
      • database migration to add column to certname
      • hash & check that the content of catalog inputs has changed before storing the new set
    • Team:
      HA
    • Story Points:
      2
    • Release Notes:
      New Feature
    • Release Notes Summary:
      PuppetDB can now detect when the inputs in a catalog have not changed with respect to the previous catalog, and avoid storing them again.
    • QA Risk Assessment:
      Needs Assessment

      Description

      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.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              austin.blatt Austin Blatt
              Reporter:
              austin.blatt Austin Blatt
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Zendesk Support