Jira (PUP-9112) :undef still shows up in types and providers
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-9112 :undef still shows up in types and providers Change By: Kenn Hussey Team: Platform Core Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9112) :undef still shows up in types and providers
Title: Message Title Michael Smith commented on PUP-9112 Re: :undef still shows up in types and providers Failing PEZ. I have a fix for PE up to make it handle nil. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9112) :undef still shows up in types and providers
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-9112 :undef still shows up in types and providers Change By: Henrik Lindberg Fix Version/s: PUP 6.0.0 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9112) :undef still shows up in types and providers
Title: Message Title
Henrik Lindberg updated an issue
Puppet / PUP-9112
:undef still shows up in types and providers
Change By:
Henrik Lindberg
Release Notes Summary:
In versions before Puppet 6.0.0 values from manifests assigned to resource attributes that contained undef values nested in arrays and hashes would use the Ruby symbol :undef to represent those values. When using puppet apply types and providers would see those as :undef or as the string "undef" depending on the implementation of the type. When using a puppet master, the same values were correctly handled. In Puppet 6.0.0 Ruby {{nil}} is used consistently for this. (Top level undef values are still encoded as empty string for backwards compatibility).
Release Notes:
Deprecation
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
Jira (PUP-9112) :undef still shows up in types and providers
Title: Message Title Henrik Lindberg commented on PUP-9112 Re: :undef still shows up in types and providers This is because we are still using a 3x API for resources in puppet and it is specified that undef must be encoded as Ruby symbol :undef inside of nested structures, and as '' for top level values. When using a master, the catalog is serialized correctly and you will see a JSON null for an undef value. In the apply case, the catalog is never serialized - it simply contains whatever is in the catalog, and thus, it is possible that :undef appears in nested structures. We have almost gotten rid of :undef everywhere - hoping we may be able to get rid of it also for this case in Puppet 6.0.0 (but time is short as code freeze is imminent). Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9112) :undef still shows up in types and providers
Title: Message Title
Adam Gardner updated an issue
Puppet / PUP-9112
:undef still shows up in types and providers
Change By:
Adam Gardner
*Puppet Version:* 5.5.6 *Puppet Server Version:* N/A *OS Name/Version:* Centos 7, same on Windows 10Per the discussion in PUP-1467, all Ruby code in Types and Providers is supposed to receive {{undef}} values as {{nil}}. However, in at least some circumstances, I am receiving the Symbol {{:undef}} instead.For example, given the following resource declaration: {code:java}foo { 'bar': baz => {quux => undef, },}{code} *Desired Behavior:*Inside the provider, {{resource[:baz]}} evaluates to {{ \ {'quux' => nil \ }}}*Actual Behavior:*Inside the provider, {{resource[:baz]}} evaluates to {{ \ {'quux' => :undef \ }}}*Additional Context*Besides behaving contrary to the discussions in PUP-1467 (which is the closest I could find to documentation on {{:undef}} vs {{nil}}, this is also problematic when the provider is constructing JSON, perhaps to communicate with an API; the desired JSON string would be {{ \ {"quux": null \ }}}, but instead you end up with {{ \ {"quux": "undef" \ }}}.
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-9112) :undef still shows up in types and providers
Title: Message Title
Adam Gardner created an issue
Puppet / PUP-9112
:undef still shows up in types and providers
Issue Type:
Bug
Affects Versions:
PUP 5.5.6
Assignee:
Unassigned
Components:
Types and Providers
Created:
2018/09/06 4:16 PM
Priority:
Minor
Reporter:
Adam Gardner
Puppet Version: 5.5.6 Puppet Server Version: N/A OS Name/Version: Centos 7, same on Windows 10 Per the discussion in PUP-1467, all Ruby code in Types and Providers is supposed to receive undef values as nil. However, in at least some circumstances, I am receiving the Symbol :undef instead. For example, given the following resource declaration:
foo { 'bar':
baz => {
quux => undef,
},
