Actions
Bug #7127
closed
Order of directive in a rule is only for ncf or standard lib
Status:
Released
Priority:
N/A
Assignee:
Category:
Web - Config management
Target version:
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:
Description
The order of directives in rules (or rules) is not done for all directive, but for the ncf technique on one hand, and for other techniques on the other hand.
So in fact, if we have directives: dir1, dir2, dir3, but dir3 is based on a ncf technique, then the final order is dir3, dir1, dir2. Which is clearly not what we want.
Updated by François ARMAND about 9 years 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/cf-clerk/pull/78
Updated by François ARMAND about 9 years ago
- Related to Bug #7128: When a directive from an unique technique is in several rules, it's order may be lost added
Updated by François ARMAND about 9 years ago
- Status changed from Pending technical review to Pending release
- % Done changed from 0 to 100
Applied in changeset cf-clerk|0c6e8b742d9a3e8c1a64b9dec977e1c0221690e7.
Updated by Nicolas CHARLES about 9 years ago
Applied in changeset cf-clerk|ebd12d225b250591a41597acdfa966d0cd66846a.
Updated by Vincent MEMBRÉ about 9 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 3.1.2 which was released today.
Actions