Actions
Bug #22126
closed
Windows generic method parameters are always written "mandatory=true" even when "mayBeEmpty"
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
To do
Fix check:
Checked
Regression:
No
Description
If we have a technic parameter than can be "MayBeEmpty" in the editor, it is actually mandatory not empty when used.
If we look at the generated code for the technique with such a parameter, we see that the parameter is written mandatory=$true when we would expect a false there.
Files
Updated by François ARMAND about 2 years ago
- Target version changed from 7.2.2 to 7.1.8
We have the same thing in 7.1
Updated by François ARMAND about 2 years ago
- Status changed from New to In progress
- Assignee set to François ARMAND
Updated by François ARMAND about 2 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/4584
Updated by Anonymous about 2 years ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder|8259c68de4181176ac0d91fe790c46ac0743b51f.
Updated by François ARMAND about 2 years ago
- Fix check changed from To do to Checked
Updated by Vincent MEMBRÉ about 2 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 7.1.8 and 7.2.2 which were released today.
Actions