Issue #3675 has been updated by Randall Hansen. Status changed from Needs Decision to Accepted Priority changed from Normal to Low
---------------------------------------- Feature #3675: groups should be able to remove inherited classes https://projects.puppetlabs.com/issues/3675 Author: Dan Bode Status: Accepted Priority: Low Assignee: Category: Target version: 1.2 Keywords: Branch: Affected URL: Affected Dashboard version: It would nice if the following was supported: - add class A to group A - group B inherits from group A, un-includes class A There may be security reasons why this would be less than desirable (but these are probably not valid since its already possible to override resources using inheritance). # use case (if this helps clarify things :) ) The most common use case that I have is where a service is disabled by default, and some overriding group may want to enable it. This can be accomplished by using class inheritance in Puppet, but I dont like the idea that an enabling class should be the child of a disabling class (it seems like a reverse of how it should be modeled) the ideal way to achieve it would be group A include service::disable group B uninclude service::disable include service -- 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.
