User story #5399
closed
User story #5293: Add a 'changes only' compliance mode, only reporting changes on systems
Create a system variable RUDDER_NODE_CONFIG_ID to store the node current configuration identifier
Added by Nicolas CHARLES over 9 years ago.
Updated about 9 years ago.
Description
It would contain a "hash" of the promises for the node, and injected in the startRun / endrun report, to ensure that promises are up to date
The variable name is: RUDDER_NODE_CONFIG_ID
- Project changed from Rudder to 17
- Category deleted (
Web - Compliance & node report)
- Status changed from New to In progress
- Assignee changed from Nicolas CHARLES to François ARMAND
- Parent task deleted (
#5293)
- Status changed from In progress to 10
- Priority changed from N/A to 2
- Pull Request set to https://github.com/Normation/cf-clerk/pull/52
- Description updated (diff)
- Subject changed from Create a system variable to store the "node configuration version" to Create a system variable RUDDER_NODE_CONFIG_ID to store the node current configuration identifier
- Status changed from 10 to Pending technical review
- Assignee changed from François ARMAND to Nicolas CHARLES
PR updated to match the expected variable name.
- Status changed from Pending technical review to Pending release
- % Done changed from 0 to 100
Applied in changeset commit:fe9e6e3f51bdb2152383dd964cffedb5a20a8490.
- Target version changed from 140 to 3.0.0~beta1
- Project changed from 17 to Rudder
- Parent task set to #5293
- Status changed from Pending release to Released
This bug has been fixed in Rudder 3.0.0~beta1 which was release on 01/12/2014.
- Tracker changed from Enhancement to User story
Also available in: Atom
PDF
Updated by 
Updated by Matthieu CERDA 
Updated by 
Updated by