Project

General

Profile

Actions

Bug #18564

open

Class parameters using module data defaults should not have override enabled on import

Added by Dominic Cleal about 7 years ago. Updated about 7 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
Puppet integration
Target version:
-
Difficulty:
Triaged:
Fixed in Releases:
Found in Releases:

Description

Class parameters in a module (e.g. puppetlabs/ntp 6.0.0) should not have the override flag set on class import when the module uses data lookups.

In these cases, no inline default is given in the manifest (class foo($a, $b, $c) {), but the default is derived from the data within the module. Traditionally, prior to data binding this would have meant that the parameter is required, but this isn't a correct assumption any more.

(Workaround, use the Override all parameters/Set parameters to defaults pair of options on the dropdown menu on the Puppet classes page to set them to defaults.)


Related issues 2 (1 open1 closed)

Related to Foreman - Feature #18553: Set Puppet 4/5 data types during class importNewActions
Related to Foreman - Bug #24355: All parameters for class overridden by defaultClosedOri RabinActions
Actions #1

Updated by Dominic Cleal about 7 years ago

  • Related to Feature #18553: Set Puppet 4/5 data types during class import added
Actions #2

Updated by Ori Rabin almost 6 years ago

  • Related to Bug #24355: All parameters for class overridden by default added
Actions

Also available in: Atom PDF