Project

General

Profile

Actions
Copy link

Bug #21291

closed

systemUpdate technique parameters should accept properties as input

Bug #21291: systemUpdate technique parameters should accept properties as input

Added by Félix DALLIDET over 3 years ago. Updated over 3 years ago.

Status:
Released
Priority:
N/A
Assignee:
Alexis Mousset
Category:
Techniques
Target version:
7.1.2
Pull Request:
https://github.com/Normation/rudder-t...
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
To do
Fix check:
Checked
Regression:

Description

The technique has 2 "SELECT1" parameters which are making it impossible to pilot from group properties to "enable/disable" a campaign for a given group for instance.
We should instead have "INPUT" with a control at exec time that it is the string "true" if it must be enable.

Updated by Félix DALLIDET over 3 years ago Actions
Copy link
 #1

  • Status changed from New to In progress
  • Assignee set to Félix DALLIDET

Updated by Félix DALLIDET over 3 years ago Actions
Copy link
 #2

  • Status changed from In progress to Pending technical review
  • Assignee changed from Félix DALLIDET to Alexis Mousset
  • Pull Request set to https://github.com/Normation/rudder-techniques/pull/1767

Updated by Félix DALLIDET over 3 years ago Actions
Copy link
 #3

  • Status changed from Pending technical review to Pending release

Updated by Vincent MEMBRÉ over 3 years ago Actions
Copy link
 #4

  • Target version changed from 7.1.3 to 7.1.2

Updated by Vincent MEMBRÉ over 3 years ago Actions
Copy link
 #5

  • Fix check changed from To do to Checked

Updated by Vincent MEMBRÉ over 3 years ago Actions
Copy link
 #6

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 7.1.2 which was released today.

Actions
Copy link

Also available in: PDF Atom