Project

General

Profile

Actions

Bug #22126

closed

Windows generic method parameters are always written "mandatory=true" even when "mayBeEmpty"

Added by François ARMAND 17 days ago. Updated 10 days ago.

Status:
Released
Priority:
N/A
Category:
-
Target version:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
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

Actions #1

Updated by François ARMAND 17 days ago

  • Target version changed from 7.2.2 to 7.1.8

We have the same thing in 7.1

Actions #2

Updated by François ARMAND 17 days ago

  • Status changed from New to In progress
  • Assignee set to François ARMAND
Actions #3

Updated by François ARMAND 16 days 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
Actions #4

Updated by Anonymous 16 days ago

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

Updated by Vincent MEMBRÉ 10 days 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

Also available in: Atom PDF