Actions
Bug #7474
closedChanging rule/directive name does not start a promise generation
Status:
Released
Priority:
2
Assignee:
Category:
Web - Config management
Target version:
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:
Description
Since Rule and Directive name are used to choose the techniques order in the final bundle, a change on them must start a generation.
Updated by François ARMAND about 9 years ago
- Status changed from New to In progress
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 Vincent MEMBRÉ
- Pull Request set to https://github.com/Normation/rudder/pull/977
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 rudder|d7aa54ee9009162fdcf13ccc39de0cdbbf783cd3.
Updated by Vincent MEMBRÉ about 9 years ago
Applied in changeset rudder|09cd56cb280be09ffa1440c972c0e5dfab288c91.
Updated by Vincent MEMBRÉ about 9 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 3.1.5 which was released today.
Actions