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

Support a new "configure expiration" command

    XMLWordPrintable

    Details

    • Type: New Feature
    • Status: Closed
    • Priority: Normal
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: PDB 6.3.0
    • Component/s: None
    • Template:
    • Team:
      PuppetDB
    • Release Notes:
      New Feature
    • Release Notes Summary:
      Hide
      An experimental "configure expiration" command has been added. It currently allows specifying that factsets should (the longstanding default) or should not be candidates for expiration. See the documentation for further information and some caveats, and note that as an experimental command, it might be altered or removed in a future release.
      Show
      An experimental "configure expiration" command has been added. It currently allows specifying that factsets should (the longstanding default) or should not be candidates for expiration. See the documentation for further information and some caveats, and note that as an experimental command, it might be altered or removed in a future release.
    • QA Risk Assessment:
      Needs Assessment

      Description

      For now we'll only support setting factset expiration to true or false.

      DB/command names are not set in stone.

      Add an endpoint (and a feature flag?) that accepts and stores a command that looks like.

      {
        “producer_timestamp”: ISO8601
        “certname” : “foo”
        “expire” : {
                         “facts” : false
                       }
      }
      

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              rob.browning Rob Browning
              Reporter:
              austin.blatt Austin Blatt
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Zendesk Support