Project

General

Profile

Actions
Copy link

Bug #2855

closed

Rudder doesn't properly checks the folder name for techniques when writing them

Added by Nicolas CHARLES about 12 years ago. Updated over 9 years ago.

Status:
Released
Priority:
1 (highest)
Assignee:
François ARMAND
Category:
Web - Config management
Target version:
2.4.0~beta5
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

Description

If we have another folder in the /var/rudder/configuration-repository with the same file hierarchy than the techniques folders, then when writing promises (not at any other moment), the files read might come from the other folder.

Step to reproduce :
  1. Copy the /var/rudder/configuration-repository/techniques to policies
  2. Garble completely the content of the files in /var/rudder/configuration-repository/policies
  3. add the /var/rudder/configuration-repository/policies folder to the git, and commit it
  4. do a modification (simple) in the /var/rudder/configuration-repository/techniques, and commit it (this step is mandatory for rudder to reload the technique lib)
  5. reload the technique library

Some files in the generated promises will be garbled (not all)

Note : I'm not sure if it would happen in 2.3.9, but that's most likely

Actions
Copy link

Also available in: Atom PDF