User story #25120


Architecture #24963: Persist compliance in base to know last state for a long time

Use node properties to decide how long compliance is valid

Added by François ARMAND 16 days ago. Updated about 9 hours ago.

Web - Compliance & node report
Target version:
UX impact:
Suggestion strength:
User visibility:
Effort required:
Name check:
To do
Fix check:
To do


For now, we use an heuristic based on "2 agent run + some more time" before we expire compliance and set everything to "no answer".

We want to be able to let the use pilot that latency by letting him specify a period of time during which compliance will remain valid, even if it's days.

That setting must be by-node, and if possible by-group-overridable by node, because the typical use case is "nodes in the 'laptop' group should have a 7 days compliance validatity before we expire it, while server in group 'important' should be checked as often as possible".

This clearly point to the use of (global, group, node) properties.

So that ticket goal is to make the "run agent" parameterized by a period of validity, and get the period of validity from properties.

Actions #1

Updated by François ARMAND 16 days ago

  • Status changed from New to In progress
  • Assignee set to François ARMAND
Actions #2

Updated by François ARMAND 15 days ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from François ARMAND to Clark ANDRIANASOLO
  • Pull Request set to
Actions #3

Updated by Anonymous 13 days ago

  • Status changed from Pending technical review to Pending release
Actions #4

Updated by Alexis Mousset about 9 hours ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 8.2.0~alpha1 which was released today.


Also available in: Atom PDF