Issue #5673 has been updated by eric sorenson. Category set to language Target version set to 3.x Keywords changed from defines,execution order to graph resources ordering
Got a dup of this one; relevant to some discussions about ordering. Flagging for attention during 3.x ---------------------------------------- Bug #5673: defines are always processed after classes https://projects.puppetlabs.com/issues/5673#change-72733 Author: Yuri Arabadji Status: Needs More Information Priority: Normal Assignee: Category: language Target version: 3.x Affected Puppet version: 2.6.4 Keywords: graph resources ordering Branch: It's fine when you want to do processing on agent, but what if you require dependencies on master? The test case follows: <pre> define firstdef { notice("Define: first.") } define seconddef { notice("Define: second.") } class first { notice("Class: first.") firstdef {'firstdef_rsrc': } } class second { notice("Class: second.") seconddef { 'seconddef_rsrc': } } node 'default' { include first include second } </pre> No matter what you do, the output is always: <pre> notice: Scope(Class[First]): Class: first. notice: Scope(Class[Second]): Class: second. notice: Scope(Firstdef[firstdef_rsrc]): Define: first. notice: Scope(Seconddef[seconddef_rsrc]): Define: second. </pre> It would be cool to have the graph engine actually work for you on master, too. The reason is proper templating. Thank you. -- 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://projects.puppetlabs.com/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.
