User story #5320: Update technique to understand "error only" mode - Rudder - Issue Tracker

Actions

Copy link

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 over 10 years ago. Updated over 9 years ago.

Status:

Released

Priority:

N/A

Assignee:

Nicolas CHARLES

Category:

System techniques

Target version:

3.0.0~beta1

Pull Request:

https://github.com/Normation/rudder-t...

UX impact:

Suggestion strength:

User visibility:

Effort required:

Name check:

Fix check:

Regression:

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.

Actions

Copy link

Updated by Nicolas CHARLES about 10 years ago

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

Actions

Copy link

Updated by Nicolas CHARLES about 10 years ago

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

https://github.com/Normation/rudder-techniques/pull/483

Actions

Copy link