Issue #4269 has been reported by Peter Meier.
----------------------------------------
Bug #4269: behavior change in 2.6: undef variables are not anymore empty strings
http://projects.puppetlabs.com/issues/4269
Author: Peter Meier
Status: Unreviewed
Priority: Normal
Assigned to:
Category:
Target version:
Affected version: 2.6.0rc3
Keywords:
Branch:
The following manifest:
<pre>
$ cat foo.pp
notice $a
exec{"/bin/echo a=$a > /tmp/foo": }
</pre>
produced in 0.25.x the following:
<pre>
$ puppet foo.pp
notice: Scope(Class[main]):
notice: //Exec[/bin/echo a= > /tmp/foo]/returns: executed successfully
$ cat /tmp/foo
a=
</pre>
However 2.6 produces:
<pre>
$ puppet foo.pp
notice: Scope(Class[main]): undef
notice: /Stage[main]//Exec[/bin/echo a=undef > /tmp/foo]/returns: executed
successfully
$ cat /tmp/foo
a=undef
</pre>
This changes the behavior of various execs and generate functions. In regard to
ruby's behavior of nil.to_s undef variables should also be empty strings.
Otherwise this should be documented, but it will give some headaches in mixed
enviornments.
--
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.
