Project

General

Profile

Actions

User story #12291

closed

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

Added by Vincent MEMBRÉ almost 5 years ago. Updated almost 5 years ago.

Status:
Released
Priority:
N/A
Category:
Web - Config management
Target version:
UX impact:
Suggestion strength:
User visibility:
Effort required:
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

Actions #1

Updated by Vincent MEMBRÉ almost 5 years ago

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

Updated by Vincent MEMBRÉ almost 5 years 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
Actions #3

Updated by Vincent MEMBRÉ almost 5 years ago

  • Status changed from Pending technical review to Pending release
Actions #4

Updated by Vincent MEMBRÉ almost 5 years ago

  • Status changed from Pending release to Released

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

Actions

Also available in: Atom PDF