Issue #6934 has been updated by Chuck Schweizer.
The main use case i had is now solved with puppet 2.6.7 because of Bug fix #5073. I would still like puppet to not fail if the class does not exist. Mainly because if coded correctly a missing class should not invalidate the puppet manifest the client runs and I would like puppet to be resilient in that way. I do agree that an error should be raised though. So at this point it is just a preference I have for this solution. If it makes more sense for the manifest build to fail and have the client do nothing puppet 2.6.7 allows my environment to continue to work. ---------------------------------------- Bug #6934: non-fatal method for including classes https://projects.puppetlabs.com/issues/6934 Author: Chuck Schweizer Status: Needs More Information Priority: Normal Assignee: Nigel Kersten Category: Target version: Affected Puppet version: Keywords: Branch: There are use cases where people wish to attempt to include a given class, but not to fail if it cannot be found. This functionality was accidentally provided by external node classifiers in 2.6.x and earlier, but has been removed to achieve consistency in class declarations between ENCs and the DSL. It should be simple to copy the include function and replace errors with a log message instead. This probably isn't possible with parameterized classes. -- 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.
