Issue #3118 has been updated by Oliver Hookins.
I may be completely wrong here, but my first foray into using an ENC was initially prevented by not having ANY static node definition present (not even a default node). So technically it is not cumulative, because a definition returned by the ENC by itself is not enough. You need at least a default node definition in the files (even if it is completely empty). For this reason, I see it as a bug. ---------------------------------------- Bug #3118: External node tool definitions appear to be cumulative https://projects.puppetlabs.com/issues/3118 Author: Markus Roberts Status: Needs design decision 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 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.
