Actions
Bug #18995
closed
Missing mandatory directive parameter doesn't fail policy generation
Bug #18995:
Missing mandatory directive parameter doesn't fail policy generation
Status:
Released
Priority:
N/A
Assignee:
Category:
Web - Config management
Target version:
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
To do
Fix check:
Checked
Regression:
Description
It seems that at some point, we lost the check for mandatory parameters during policy generation (or perhaps we never had one - we at least have a `SaveDirectivesOnTechniqueCallback` but AFAIR it was only to update information saved in LDAP).
So, it means that if a new mandatory parameter is added, then the policy generation doesn't fail.
Updated by François ARMAND almost 5 years ago
- Status changed from New to In progress
Updated by François ARMAND almost 5 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/rudder/pull/3532
Updated by François ARMAND almost 5 years ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder|4abbf6890181dda7da8267de5b89ad18f7a33833.
Updated by François ARMAND almost 5 years ago
- Fix check changed from To do to Checked
Updated by Vincent MEMBRÉ almost 5 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 6.1.10 and 6.2.3 which were released today.
Updated by Vincent MEMBRÉ almost 5 years ago
- Related to Bug #19115: Allow to put empty value in technique parameters added
Actions