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

Move "should be deactivated" logic from process-command! down to deactivate-node!

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Normal
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: PDB 3.1.0
    • Component/s: None
    • Labels:
      None
    • Template:
    • Epic Link:
    • Story Points:
      1
    • Sprint:
      PuppetDB 2015-08-12

      Description

      Perhaps storage's deactivate-node! command (or some new wrapper) should centralize the deactivation logic instead of having commands/process-command! perform part of the evaluation (looking for any newer records for the certname) and deactivate-node! handle the rest (checking the producer_timestamp).

        Attachments

          Activity

            People

            Assignee:
            Unassigned
            Reporter:
            rob.browning Rob Browning
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:

                Zendesk Support