User story #12291: Identify in technique metadata if techniques should enable or disable ncf reporting - Rudder - Issue Tracker

Actions

Copy link

User story #12291

closed

Identify in technique metadata if techniques should enable or disable ncf reporting

Added by Vincent MEMBRÉ about 6 years ago. Updated about 6 years ago.

Status:

Released

Priority:

N/A

Assignee:

François ARMAND

Category:

Web - Config management

Target version:

4.3.0~rc2

Pull Request:

https://github.com/Normation/rudder/p...

UX impact:

Suggestion strength:

User visibility:

Effort required:

Name check:

Fix check:

Regression:

Description

We want to disable ncf reporting for classic techniques, and enable it for techniques made with the technique editor (which rely on the method reporting contrary to the first one), we may also want handmade technique to rely on method reporting too.

To do this, we will all a new tag in metadata

<METHODREPORTING>disabled/enabled</METHODREPORTING>

We will add this metadata to ncf techniques when they will be migrated to 4.3 version,

If that value is not defined (migration path), we will also look if the techniques defines an expected_reports.csv, if there is a csv file, we will enable reporting