Project

General

Profile

Actions

Bug #13615

closed

Bad explanation for generic variable overide priority cause people making the opposite of what is needed

Added by François ARMAND over 4 years ago. Updated 8 months ago.

Status:
Released
Priority:
N/A
Category:
Documentation
Target version:
Severity:
Minor - inconvenience | misleading | easy workaround
UX impact:
User visibility:
Getting started - demo | first install | level 1 Techniques
Effort required:
Very Small
Priority:
0
Regression:

Description

When people try to override generic variable technique with priority, they naturally follow what the "?" tell. But generic variable definition works in the opposite of unique directive (because it is not a unique directive, and so the priority thing is just a hack of cfengine taking the last definition, so the least prioritary one).

We need to special case the "?" for generic variable definition and refer to https://docs.rudder.io/reference/5.0/usage/advanced_configuration_management.html#_special_use_case_overriding_generic_variable_definition for the full explanation.

Actions #1

Updated by François ARMAND over 4 years ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from François ARMAND to Alexis Mousset
  • Pull Request set to https://github.com/Normation/rudder/pull/2042
Actions #2

Updated by François ARMAND over 4 years ago

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

Updated by Vincent MEMBRÉ over 4 years ago

  • Status changed from Pending release to Released
This bug has been fixed in Rudder 4.1.15, 4.3.5 and 5.0.1 which were released today.
Changelog
Changelog
Changelog
Actions #4

Updated by Alexis Mousset 8 months ago

  • Priority changed from 112 to 0
Actions

Also available in: Atom PDF