Jira (PUP-2403) Should include parser function to generate a "stack trace"

[Henrik Lindberg (JIRA)]

Title: Message Title

Henrik Lindberg commented on an issue   Re: Should include parser function to generate a "stack trace" For resources that are included in the catalog, it is possible to see where they were included by running: puppet master --compile <envname> As this outputs the resulting catalog for the given environment name. All resources show the file and line where they were included/created. Unfortunately, this is not recorded for include, require and contain of classes, only if the class is included via a resource _expression_. i.e. this does not record the wanted information: include(test) But this does: class { test: } The implementation of a "puppet trace" is somewhat tricky and requires keeping track of extra information that will carry a performance penalty. We envision writing a debugger (where it is ok to run slower) that allows stopping at a breakpoint in puppet logic and then checking the call stack. An alternative is to modify the function API to provide information about the source location of the call (neither the 3x nor the 4x API has this atm). This would enable the include/require/contain functions to record the location the same way as the resource instantiation (but it cannot currently do this). Meanwhile, the Geppetto IDE for Puppet can perform static navigation between a class and all places where it is mentioned (e.g. included) and vice versa. (Since it is based on static analysis it may not find dynamic references though, but may be a convenient way for inexperienced users to browse/navigate puppet code for the purpose of understanding it). Add Comment   Puppet / PUP-2403 Should include parser function to generate a "stack trace" Customers often struggle over identifying how classes are included in their catalog. It would be incredibly helpful if we had a `trace()` function that would generate a hierarchical list (maybe just an array?) of the class that included the current class, all the way to top scope. I understand that this should be possible with the future parser. 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.