[PDB-4270] Support a new "configure expiration" command Created: 2019/02/25  Updated: 2019/03/26  Resolved: 2019/03/20

Status: Closed
Project: PuppetDB
Component/s: None
Affects Version/s: None
Fix Version/s: PDB 6.3.0

Type: New Feature Priority: Normal
Reporter: Austin Blatt Assignee: Rob Browning
Resolution: Fixed Votes: 0
Labels: resolved-issue-added
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
blocks PDB-4267 Allow nodes to opt out of some garbag... Closed
relates to PDB-4271 Create a new query endpoint/AST entit... Closed
Team: PuppetDB
Release Notes: New Feature
Release Notes Summary: An experimental "configure expiration" command has been added. It currently allows specifying that factsets should (the longstanding default) or should not be candidates for expiration. See the documentation for further information and some caveats, and note that as an experimental command, it might be altered or removed in a future release.
QA Risk Assessment: Needs Assessment


For now we'll only support setting factset expiration to true or false.

DB/command names are not set in stone.

Add an endpoint (and a feature flag?) that accepts and stores a command that looks like.

  “producer_timestamp”: ISO8601
  “certname” : “foo”
  “expire” : {
                   “facts” : false

Comment by Rob Browning [ 2019/03/21 ]

Heston Hoffman Yeah, should have mentioned that – if you look at the "git log -p" and search (typically via '/') for PDB-4270, you should jump to the commit including the doc changes. I suspect the likely entry point would be the summary in documentation/api/command/v1/commands.markdown, i.e. the ### "configure expiration", version 1 (experimental) section.

Comment by Heston Hoffman [ 2019/03/21 ]

Thanks Rob Browning, I've linked to the doc from the release note

Generated at Sun Jul 12 23:00:10 PDT 2020 using Jira 8.5.2#805002-sha1:a66f9354b9e12ac788984e5d84669c903a370049.