Issue #3118 has been updated by Alex Harvey.

This bug has been open for a long time and the result is that our documentation 
contradicts the actual behavior.  I am aware of sites using this behavior (i.e. 
relying on default node always being applied) as a feature as Jeff suggested 
above.  I would vote to update docs to match the actual behavior and close this 
bug.  Either way it would be good to resolve it one way or another.

----------------------------------------
Bug #3118: Default node definition should not be required when ENC returns a 
node definition.
https://projects.puppetlabs.com/issues/3118#change-101185

* Author: Markus Roberts
* Status: Accepted
* 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 puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to