Jira (PDB-170) exported resources with single element arrays aren't arrays on the collected side

[Richard Clark (JIRA)]

Title: Message Title

Richard Clark commented on an issue   Re: exported resources with single element arrays aren't arrays on the collected side As with the cloned bug report, adding a second empty item can sometimes cause problems with modules that don't check for empty value. (jfryman/puppet-nginx) Example: proxy_set_header => ['Host $http_host',''], Will work for some cases, but it will export an array that will have two items to iterate over. Instead, double nesting the array does work proper without side effects (for me): proxy_set_header => [['Host $http_host',],], instead will cause the exported record (at least with PupppetDB / PostgreSQL) to export properly as ["Host $http_host"] Add Comment   PuppetDB / PDB-170 exported resources with single element arrays aren't arrays on the collected side If I export a defined type with an array for one of the parameters, but only containing one element, it doesn't appear to be an array on the collecting side (using puppetlabs-stdlib/is_array). Adding a second blank element resolved this. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.