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

Adjust storage to accommodate catalog inputs

    XMLWordPrintable

    Details

    • Type: New Feature
    • Status: Resolved
    • Priority: Normal
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: PDB 6.5.0
    • Component/s: None
    • Labels:
      None
    • Release Notes:
      Not Needed
    • QA Risk Assessment:
      Needs Assessment

      Description

      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).

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              zachary.kent Zachary Kent
              Reporter:
              rob.browning Rob Browning
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Zendesk Support