Project

General

Profile

Actions

Bug #15029

closed

It's not possible to use $(match.o) anymore in directives/techniques

Added by Nicolas CHARLES almost 5 years ago. Updated over 4 years ago.

Status:
Released
Priority:
N/A
Category:
Techniques
Target version:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
To do
Fix check:
Checked
Regression:

Description

Trying to use ${match.x} in check generic file content for line replacement
Agent replaced the line with empty text, because it didn't detect the replacement variable as defined (replace_lines_destination_defined is not defined)
so it replaces with empty text

Actions #1

Updated by Vincent MEMBRÉ almost 5 years ago

  • Target version changed from 5.0.12 to 5.0.13
Actions #2

Updated by Alexis Mousset almost 5 years ago

Note: The file_lines_replace method works as a workaround.

Actions #3

Updated by Alexis Mousset almost 5 years ago

  • Category changed from Agent to Techniques

As the method work, it is problably not an agent problem, but a bug in the technique.

Actions #4

Updated by Félix DALLIDET almost 5 years ago

  • Status changed from New to In progress
  • Assignee set to Félix DALLIDET
Actions #5

Updated by Félix DALLIDET almost 5 years ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from Félix DALLIDET to Nicolas CHARLES
  • Pull Request set to https://github.com/Normation/rudder-techniques/pull/1460
Actions #7

Updated by Félix DALLIDET almost 5 years ago

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

Updated by Nicolas CHARLES over 4 years ago

  • Fix check set to Checked
Actions #9

Updated by Vincent MEMBRÉ over 4 years ago

  • Name check set to To do
Actions #10

Updated by Vincent MEMBRÉ over 4 years ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 5.0.13 which was released today.

Actions

Also available in: Atom PDF