Issue #3382 has been updated by Alan Harder.
Tried it out, but still seeing these resources in arbitrary order with the #3186 patch applied to 0.25.4. With or without the patch the --debug output shows both "//baz/require: requires Class[foo::bar]" and "//foo::bar/require: requires Class[foo]", but the requirement is not enforced for empty foo::bar class. ---------------------------------------- Bug #3382: Class require chain thru class with no resources http://projects.reductivelabs.com/issues/3382 Author: Alan Harder Status: Unreviewed Priority: Normal Assigned to: Category: functions Target version: Affected version: 0.25.4 Keywords: require Branch: This may be working as designed, but wanted to file an issue to make sure. Consider this test case: <pre> class foo { notify { 'foo': } class bar { require foo # notify { 'bar': } } } class baz { require foo::bar notify { 'baz': } } node default { include baz } </pre> When notify 'bar' is uncommented, this works as expected.. the notify messages always appear in order: foo, bar, baz. However, with notify 'bar' commented the order is sometimes foo,baz and sometimes baz,foo. It seems that some resource must be in the foo::bar class to enforce that foo is evaluated before baz. Is this expected that a class level "require" chain only works when each link in the chain has at least one resource? I use a setup like this sometimes where a subclass sets some variables and then requires the outer class, so it has no resources of its own. If you have another recommended way to do this, let me know :-) I guess I could do "require foo::bar, foo" but that's less intuitive usage. Thanks. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://reductivelabs.com/redmine/my/account -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
