Project

General

Profile

Bug #11071

Generated technique name for dsc technique in rudder-directives.ps1 contains forbiden chars

Added by Nicolas CHARLES 6 months ago. Updated 5 months ago.

Status:
Released
Priority:
N/A
Category:
-
Target version:
Target version (plugin):
Severity:
Major - prevents use of part of Rudder | no simple workaround
User visibility:
Effort required:
Priority:
0

Description

We generate technique name with / in it, which is invalid: it prevents the reports from being insered in database
So we should either:
  1. update the rsyslog rule to autorize / in technique name
  2. update the name to not use / in it

editing rudder-directives.ps1 to remove the / in it fixes the reporting

Associated revisions

Revision 9239d547
Added by François ARMAND 6 months ago

Fixes #11071: Generated technique name for dsc technique in rudder-directives.ps1 contains forbiden chars

History

#1 Updated by François ARMAND 6 months ago

  • Status changed from New to In progress
  • Assignee set to François ARMAND

#2 Updated by Nicolas CHARLES 6 months ago

rsyslog rule is [ a-zA-Z0-9_\-]+?

#3 Updated by François ARMAND 6 months ago

  • Subject changed from Generated technique name for dsc technique in rudder-directives.ps1 is invalid to Generated technique name for dsc technique in rudder-directives.ps1 contains forbiden chars

#4 Updated by François ARMAND 6 months ago

OK, so I really don't want to code a generic "utf-8 to ascci" algo for now, I propose to use the technique ID (the one "normalized" by technique editor, used in the Technique directory name, and add the full name as a comment at the end of the line.

#5 Updated by François ARMAND 6 months ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from François ARMAND to Nicolas CHARLES
  • Pull Request set to https://github.com/Normation/rudder/pull/1690

#6 Updated by François ARMAND 6 months ago

  • Status changed from Pending technical review to Pending release

#7 Updated by Vincent MEMBRÉ 5 months ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 4.2.0~beta2 which was released today.

Also available in: Atom PDF