User story #5320
closed
User story #5293: Add a 'changes only' compliance mode, only reporting changes on systems
Update technique to understand "error only" mode
Added by François ARMAND almost 10 years ago.
Updated about 9 years ago.
Category:
System techniques
Description
Both system and user technique should be updated to handle the "error only" mode by outputing only error/repaired logs.
This ticket is not intented to manage all techniques (there is some other work did for that with the ncf-ification of techniques), but at least the logic in the system one.
- Status changed from New to In progress
- Assignee set to Nicolas CHARLES
- Target version set to 140
We have a system variable RUDDER_REPORT_MODE that can contains full-compliance or changes-only
- Status changed from In progress to Pending technical review
- Assignee changed from Nicolas CHARLES to Jonathan CLARKE
- Pull Request set to https://github.com/Normation/rudder-techniques/pull/483
- Status changed from Pending technical review to Discussion
- Assignee changed from Jonathan CLARKE to Nicolas CHARLES
- Status changed from Discussion to Pending release
- % Done changed from 0 to 100
Applied in changeset policy-templates:commit:819bdeaf5eef5c4b499d8c7075f9d294a5f603cb.
Applied in changeset policy-templates:commit:338f6c75f71cdb834c734a6b14a673724ff37138.
- Target version changed from 140 to 3.0.0~beta1
- 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 
Updated by Matthieu CERDA 
Updated by 
Updated by