Issue #6621 has been updated by Oliver Hookins.
Actually I think my original diagnosis was incorrect. In at least 2.6, undef can make its way from symbol form when passed as YAML to the ENC interface, lives after that as Puppet::Parser::AST::Undef inside Puppet and makes its way out again into ERB as :undef, not 'undef'. Still, it's the same kind of problem. Without knowing what the implementation will be it is hard to make the call of whether this will impact enough to warrant going into 2.8. Personally it would be safe (and desirable) for me if it went into 2.7. ---------------------------------------- Feature #6621: Provide a nil type in the Puppet language https://projects.puppetlabs.com/issues/6621 Author: Oliver Hookins Status: Rejected Priority: Normal Assignee: Category: Target version: Affected Puppet version: 2.6.5 Keywords: Branch: Currently there is no way to semantically convey the concept of nil, as Ruby understands it. nil currently evaluates to true and is internally converted to a string 'nil', and '' evaluates (somewhat confusingly) to false. However, the empty string is a permissible configuration value whereas nil inherently is not. Furthermore non-empty strings evaluate to true unlike the empty string. My use case, to put it very simply, is to work around some limitations of communicating information between the external node classifier interface and Puppet itself, since once you pass a nil value through the interface to Puppet, nil loses its semantic value. -- 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.
