On 29/02/16 01:18, Robert Davidson wrote:
I think I figured it out.
For whatever reason, delete_undef_values wasn't doing what it said on the tin -
I'm not sure why,
> or if I should even report this as a bug to the puppet-keystone devs.
That looks like a valid bit
of puppetry to me, and I have no idea why it wasn't working on our setup.
The function delete_undef_values from stdlib does not do a good job. It
can only recognize some forms of historical undefined values.
If you are using future parser in 3.x, or puppet 4.x you can do the same
with the filter function in puppet.
# Keep those that are not undef
$filtered = $array.filter |$x| { $x !~ Undef }
Please report the problem against puppet stdlib.
Regards
- henrik
--
Visit my Blog "Puppet on the Edge"
http://puppet-on-the-edge.blogspot.se/
--
You received this message because you are subscribed to the Google Groups "Puppet
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/56D3A8DE.8070905%40puppetlabs.com.
For more options, visit https://groups.google.com/d/optout.
