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

Add command for deleting node data

    XMLWordPrintable

Details

    • Major
    • 2 - 5-25% of Customers
    • 4 - Major
    • 4 - $$$$$
    • The workarounds for this(dropping node-ttl) impact all node data not just the one you are targeting. Customers have cases where they want to delete exported resources for example but not delete all old node records.
    • New Feature
    • Added a delete node command to the admin endpoint which allows for deactivation and immediate GC of data related to a specific certname.
    • Needs Assessment

    Description

      PuppetDB supports many commands, one of which is node deactivate, which causes the query API to stop returning results for a node. However, no data is actually removed until a GC sweep occurs. There are occasions when an immediate deletion of node data is desired and the only current option is to hit the DB directly with SQL statements, which is not great. Some examples are:

      • Removing problematic exported resources.
      • Removing old PE infrastructure nodes after migrating data from an old PE installation.
      • Quickly clearing node data during testing.

      PuppetDB should provide a command that allows for deactivation and immediate GC of data related to a specific certname, or certname pattern.

      Attachments

        Issue Links

          Activity

            People

              zachary.kent Zachary Kent
              chuck Charlie Sharpsteen
              Votes:
              3 Vote for this issue
              Watchers:
              17 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Zendesk Support