Issue #4987 has been reported by donavan m.
----------------------------------------
Feature #4987: Support for 'strict' mode when evaluating puppet variables
http://projects.puppetlabs.com/issues/4987
Author: donavan m
Status: Unreviewed
Priority: Normal
Assignee:
Category:
Target version:
Affected version:
Keywords:
Branch:
Currently undefined puppet variables seem to be evaluated as empty strings in
manifests. I would appreciate a 'strict' mode that failed catalog compilation
when evaluating undefined puppet variables in manifest.
A contrived example:
file {
"/tmp/foo":
source => "puppet:///module/myfiles/files/tmp/foo_$undefvariable"
}
This will attempt to use a source of "puppet:///module/myfiles/files/tmp/foo_".
Another common use case would be undefined variables in case/selectors, such as
$revision or $hostgroup.
I believe undefined puppet variables in templates is different/harder problem
related to puppet variables being methods, not variables. Fixing both cases
would be great, but I'd settle for manifests with strict.
This came up at puppet camp, I believe through Matt Robinson in the Friday
'config testing' breakout. The idea had quite a few +1s from those in the room.
--
You have received this notification because you have either subscribed to it,
or are involved in it.
To change your notification preferences, please click here:
http://projects.puppetlabs.com/my/account
--
You received this message because you are subscribed to the Google Groups
"Puppet Bugs" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/puppet-bugs?hl=en.
