Jira (HI-220) Deprecate interpolation via function in hiera.yaml

[Sean Griffin (JIRA)]

Title: Message Title

Sean Griffin commented on HI-220   Re: Deprecate interpolation via function in hiera.yaml I don't see any deprication warning message when causing a call to hiera() during interpolation of the hiera config file. The discussion and title of the ticket would suggest that I should see such a warning. I set up a manifest and a hiera configuration, in which hiera.yaml calls hiera('role') and a module manifest that makes the function call hiera('somename'). (See attached init-manifest) Comparing the old hiera (commit sha 51d74ff8f693188d07297c80d9b3f2f8cc9ec310) to the new sha (8e34c4fec5d1afc3dd89d01520debf7daab2f741 == head), I see following differences: 1. function call from the module manifest returns different error messages: old msg: Error: Could not run: stack level too deep new msg: Error: Evaluation Error: Error while evaluating a Function Call, Lookup recursion detected in [hiera('role')] at /etc/puppetlabs/code/environments/production/modules/hieratest/manifests/init.pp:11:10 on node rg9zuk876be3znp.delivery.puppetlabs.net 2. These error messages are displayed in response to the command: 'puppet lookup somename'. 3. The same is also true for 'hiera somename', except in the fixed version I also see a stack trace. So... Deprication? It seems it got merged before and then reverted. Was this omitted or do we no longer want that warning? Add Comment   This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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.