Jira (PUP-7443) puppet-lookup should not fail on no returned items
Title: Message Title Nicholas Fagerlund updated an issue Puppet / PUP-7443 puppet-lookup should not fail on no returned items Change By: Nicholas Fagerlund Labels: triaged Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7443) puppet-lookup should not fail on no returned items
Title: Message Title
Terri Haber created an issue
Puppet / PUP-7443
puppet-lookup should not fail on no returned items
Issue Type:
Bug
Affects Versions:
PUP 4.7.1
Assignee:
Unassigned
Created:
2017/04/11 2:52 PM
Priority:
Normal
Reporter:
Terri Haber
The idea behind Hiera is that data can be applied, as needed, for a node. In many cases, in the old world of hiera* functions, sometimes data is not returned, and that's ok. It should be optional, given the flexibility the user base is accustomed to in the ecosystem.
Now, however, the hiera* functions are being deprecated for the lookup function, and optional data return is not allowed. The catalog compilation fails if no data is returned. This restricts the ways in which hiera can be leveraged.
Given this example:
$jobs = lookup('cronjob', {merge => hash})
create_resources('cronjob',$jobs)
