Jira (PDB-4342) Add a node timestamp and connect to configure expiration

[Rob Browning (JIRA)]

Rob Browning updated an issue

PuppetDB / PDB-4342 Add a node timestamp and connect to configure expiration Change By: Rob Browning Summary: Support an option to update the Add a node timestamp used and connect to expire nodes configure expiration Add Comment

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

[Rob Browning (JIRA)]

Rob Browning updated an issue

PuppetDB / PDB-4342 Add a node timestamp and connect to configure expiration Change By: Rob Browning

Extend the configure expiration command to allow "node" as a value in the "expire" field, i.e. {"node": <boolean> ...} 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

[Rob Browning (JIRA)]

Rob Browning updated an issue

PuppetDB / PDB-4342 Add a node timestamp and connect to configure expiration Change By: Rob Browning

Extend the configure expiration command to allow "node" as a value in the "expire" field, i.e. {"node": <boolean> ...} and have the command behave as it does for facts, but

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