Logbook retention policies
Registered by
Joshua Harlow
It would be nice to support a few basic logbook retention policies to avoid the continual cleanup required to discard irrelevant logbooks (and there associated flow details and task details contained in those logbooks).
A few that come to mind:
- delete individual flow detail/full logbook after success (aka, clear on/after certain states)
- expire logbook (or part of it) automatically after a given period of time (aka, TTL based)
- keep it forever, but place in a 'longer-term' storage, such as a remote directory (aka, move it)
- never keep anything (no persistence)
- keep just the last X entries
Blueprint information
- Status:
- Not started
- Approver:
- Joshua Harlow
- Priority:
- Medium
- Drafter:
- Joshua Harlow
- Direction:
- Approved
- Assignee:
- None
- Definition:
- Approved
- Series goal:
- None
- Implementation:
- Unknown
- Milestone target:
- None
- Started by
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
Etherpad for further discussion: https:/
(?)