Jira (PUP-5971) Define evaluation should be evaluated depth-first, not breadth-first

[Hunter Haugen (JIRA)]

Title: Message Title

Hunter Haugen commented on PUP-5971   Re: Define evaluation should be evaluated depth-first, not breadth-first Ran into this again with the tomcat module. Here is a simple minimal case: define foo { foo::foo { $name: } } define foo::foo { ensure_resource('user', 'tomcat8', { 'ensure' => 'present' }) file { '/test': owner => 'tomcat8', } } define bar { ensure_resource('user', 'tomcat8', { 'ensure' => 'present' }) } foo { 'hi': } -> bar { 'hi': } And the result Error: Failed to apply catalog: Found 1 dependency cycle: (File[/test] => Foo::Foo[hi] => Foo[hi] => Bar[hi] => User[tomcat8] => File[/test]) And I can't just test the bar an extra level deeper, since foo and bar may be declared at who-knows-what-depth by our users. 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.