Jira (PDB-3879) node-purge-ttl setting not working in 2017.3

[Daniel Mcilhagga (JIRA)]

Title: Message Title

Daniel Mcilhagga created an issue   PuppetDB / PDB-3879 node-purge-ttl setting not working in 2017.3 Issue Type: Bug Assignee: Unassigned Created: 2018/03/21 6:38 AM Priority: Normal Reporter: Daniel Mcilhagga In 2017.2 when a node was marked as expired or deactivated it but node-purge-ttl wasn't invoked, it will still searchable by using: curl -X GET http://localhost:8080/pdb/query/v4 --data-urlencode 'query=nodes { expired is not null or deactivated is not null }' | python -m json.tool Since 2017.3.*, if the node-purge-ttl setting is set to 0s (or any value) it will not be respected and the data is purged from the DB instantly.  Running the above query does not display any results and any queries searching for all nodes so not show the nodes in question.  Add Comment   This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.