Jira (PDB-4342) Support an option to update the timestamp used to expire nodes

[Zachary Kent (JIRA)]

Zachary Kent created an issue

PuppetDB / PDB-4342 Support an option to update the timestamp used to expire nodes Issue Type: Improvement Assignee: Unassigned Created: 2019/04/11 4:07 PM Priority: Normal Reporter: Zachary Kent Support a way for users to explicitly refresh the timestamp used for node TTL. This can be accomplished currently by repeatedly sending configure expiration commands for a node with expire.facts = true (see linked ticket for more detail) We should make this more explicit (maybe adding a new command) and look into the possibility of allowing bulk updates given a list of certnames. Add Comment

This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)

[Robert Roland (JIRA)]

Robert Roland commented on PDB-4342

Re: Support an option to update the timestamp used to expire nodes Going to add a "touch-node" command to do this. We can expand in the future with "touch-factset" etc

Add Comment

[Robert Roland (JIRA)]

Robert Roland updated an issue

PuppetDB / PDB-4342

Support an option to update the timestamp used to expire nodes

Change By: Robert Roland

Support a way for users to explicitly refresh the timestamp used for node TTL.

This can be accomplished currently by repeatedly sending *configure expiration* commands for a node with *expire.facts = true* (see linked ticket for more detail)

We should make this more explicit (maybe adding a new command) and look into the possibility of allowing bulk updates given a list of certnames.

Add Comment

[Robert Roland (JIRA)]

Robert Roland commented on PDB-4342

Re: Support an option to update the timestamp used to expire nodes This can't be accomplished with a simple "touch-node" call, as a factset or report or otherwise can still cause a node to be expired because our use of on delete cascade throughout the database

Add Comment