Issue #3118 has been updated by Andrew Parker. Status changed from Accepted to Rejected
As Alex says, this ticket has been open for a long time. This is behavior that is wanted by some and unwanted by others; however, I don't see us changing this any time soon. ---------------------------------------- Bug #3118: Default node definition should not be required when ENC returns a node definition. https://projects.puppetlabs.com/issues/3118#change-101195 * Author: Markus Roberts * Status: Rejected * Priority: Normal * Assignee: * Category: * Target version: * Affected Puppet version: 0.24.8 * Keywords: * Branch: ---------------------------------------- This behavior is surprising, but not new. Given the external node tool: <pre> #!/usr/bin/env ruby print %q{ --- classes: - foo } exit 0 </pre> And site.pp: <pre> class foo { notice "foo" } class bar { notice "bar" } node default { include bar } </pre> The following results are seen: <pre> info: Caching node for host-246-104.pubnet.pdx.edu notice: Scope(Class[bar]): bar notice: Scope(Class[foo]): foo notice: Compiled catalog for host-246-104.pubnet.pdx.edu in 0.01 seconds </pre> The same results are seen with 0.24.8 and 0.25.4rc3. This appears to break the assumption that default is only applied for nodes that aren't otherwise defined. The same is seen with an explicit node instead of just default in site.pp -- 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 unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
