Details
-
Bug
-
Status: Closed
-
Normal
-
Resolution: Fixed
-
None
-
None
-
2
-
Language 2016-08-24
-
Bug Fix
-
Description
The following code works when evaluated from a manifest:
puppet apply -e 'define foo($foo) {} foo { "FOO": foo => undef }' |
But not when done using create_resources.
The rule puppet should use is: if undef is given then use the default value if one exists, otherwise set an explicit undef. Now the create_resources function simply filters out all undef values. (If simply kept, there are other problems since relationships cannot handle undef entries.
Attachments
Issue Links
- relates to
-
MODULES-3715 ensure_resource fails with undef parameter
-
- Needs Information
-
-
MODULES-3442 postgresql::server::extension tests fail with "No title provided and "undef" is not a valid resource reference"
-
- Closed
-
-
PUP-6385 No title provided and "" is not a valid resource reference - caused by create_resources() not filtering out undefs
-
- Closed
-