Project

General

Profile

User story #12291

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

Added by Vincent MEMBRÉ 9 months ago. Updated 8 months ago.

Status:
Released
Priority:
N/A
Category:
Web - Config management
Target version:
Suggestion strength:
User visibility:
Effort required:

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

Associated revisions

Revision ef0c3bca (diff)
Added by Vincent MEMBRÉ 9 months ago

Fixes #12291: Identify in technique metadata if techniques should enable or disable ncf reporting

Revision 056eec82 (diff)
Added by Vincent MEMBRÉ 9 months ago

Fixes #12291: Identify in technique metadata if techniques should enable or disable ncf reporting

History

#1 Updated by Vincent MEMBRÉ 9 months ago

  • Status changed from New to In progress
  • Assignee set to Vincent MEMBRÉ

#2 Updated by Vincent MEMBRÉ 9 months ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from Vincent MEMBRÉ to François ARMAND
  • Pull Request set to https://github.com/Normation/rudder/pull/1877

#3 Updated by Vincent MEMBRÉ 9 months ago

  • Status changed from Pending technical review to Pending release

#4 Updated by Vincent MEMBRÉ 8 months ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 4.3.0~rc2 which was released today.

Also available in: Atom PDF