Project

General

Profile

Actions
Copy link

User story #5400

closed

User story #5895: Enhance detection of ncf based techniques in Rudder

Use the existence of expected_reports.csv to detect if a technique is from ncf

Added by Benoît PECCATTE over 10 years ago. Updated over 9 years ago.

Status:
Released
Priority:
1 (highest)
Assignee:
Nicolas CHARLES
Category:
Web - Technique editor
Target version:
3.0.0~beta1
Pull Request:
https://github.com/Normation/cf-clerk...
UX impact:
Suggestion strength:
User visibility:
Effort required:
Name check:
Fix check:
Regression:

Description

The webapp uses REPORTKEYS to know if a technique is from ncf.

With this we can't create ncf techniques with parameters.

Instead we should rely on the existence of expected_reports.csv which will be there event with parametered techniques.

Subtasks 2 (0 open — 2 closed)

Bug #5734: errors when reloading techniquesReleasedNicolas CHARLES2014-11-05Actions
Bug #5731: Promise generation is slowed down because expected_reports.csv file is written multiple times per nodeReleasedFrançois ARMAND2014-11-04Actions

Related issues 1 (0 open — 1 closed)

Blocks Rudder - User story #5665: Generate technique with parameter from ncfReleasedVincent MEMBRÉ2014-10-21Actions
Actions
Copy link
 #1

Updated by Matthieu CERDA over 10 years ago

  • Subject changed from Use the exisnce of expected_reports.csv to detect if a technique is from ncf to Use the existence of expected_reports.csv to detect if a technique is from ncf
Actions
Copy link
 #2

Updated by Benoît PECCATTE over 10 years ago

  • Description updated (diff)
Actions
Copy link
 #3

Updated by François ARMAND about 10 years ago

Note that the correction of that bug won't allow to have mixed ncf/non ncf variable. This need a dedicated code upgrade in RudderCf3PromisesFileWriterServiceImpl#prepareRulesForAgents

Actions
Copy link
 #4

Updated by François ARMAND about 10 years ago

  • Project changed from 41 to 17
  • Status changed from New to 8
  • Priority changed from N/A to 3
Actions
Copy link
 #5

Updated by François ARMAND about 10 years ago

  • Tracker changed from Bug to Enhancement
  • Status changed from 8 to Pending technical review
  • Assignee changed from François ARMAND to Nicolas CHARLES
  • Pull Request set to https://github.com/Normation/cf-clerk/pull/59
Actions
Copy link
 #6

Updated by François ARMAND about 10 years ago

  • Status changed from Pending technical review to Pending release
  • % Done changed from 0 to 100

Applied in changeset commit:6f903c602f47dd1b1ac96f091ba95be1a9cb88b6.

Actions
Copy link
 #7

Updated by Nicolas CHARLES about 10 years ago

Applied in changeset commit:6892cd7d2eb2b1b6fcc4cdf2749d4ef5f7e460cd.

Actions
Copy link
 #8

Updated by Matthieu CERDA about 10 years ago

  • Target version changed from 140 to 3.0.0~beta1
Actions
Copy link
 #9

Updated by Vincent MEMBRÉ about 10 years ago

  • Project changed from 17 to Rudder
  • Category set to Web - Technique editor
  • Parent task set to #5895
Actions
Copy link
 #10

Updated by Vincent MEMBRÉ about 10 years ago

  • 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.

Actions
Copy link
 #11

Updated by Benoît PECCATTE over 9 years ago

  • Tracker changed from Enhancement to User story
Actions
Copy link

Also available in: Atom PDF