Architecture #24963
openPersist compliance in base to know last state for a long time
Description
We need to persist compliance in base to be able to:
- restore the last known state when rudder start up
- more finely control persistance expiration by node.
More saillantly, we want to be able to address the case:
- a node compliance should be kept for several days when a node is not answering (typically: laptop when people go on hollidays),
- we want to avoid keeping run reports for more than a day for storage reason
That case is not possible without persistence in base.
Today, we compute compliance from expected reports and last run reports, always. If we don't have run reports, we don't have compliance.
Updated by François ARMAND 10 months ago
Work in progess here: https://github.com/fanf/rudder/commit/4b948032dcd05758176d9fbeb7df91a29e3cebf4
Updated by François ARMAND 8 months ago
- Status changed from In progress to Pending release
This was completed in Rudder 8.2.0.beta2
Updated by Vincent MEMBRÉ 8 months ago
This bug has been fixed in Rudder 8.2.0~rc1 which was released today.