Details
-
New Feature
-
Status: Resolved
-
Normal
-
Resolution: Fixed
-
None
-
PuppetDB
-
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
- blocks
-
ENTERPRISE-1215 Feature to remove bulk nodes from PE console
-
- Open
-
- is duplicated by
-
PDB-3508 Create an actual "node purge" command
-
- Closed
-