Issue #18490 has been reported by Ryan Coleman. ---------------------------------------- Feature #18490: Resources with the same properties and values should not conflict https://projects.puppetlabs.com/issues/18490
Author: Ryan Coleman Status: Unreviewed Priority: Normal Assignee: Category: Target version: Affected Puppet version: Keywords: Branch: It is not uncommon with the Forge to install and use two modules that express the same resource in two classes that you want to use together, resulting in a catalog compilation failure. For example, imagine two modules, for different reasons express a package resource for gcc, ensuring it is present. A user would need to modify one or both of the modules they've installed in order to move on. It would be lovely if two resources that express the same properties with the same values result in a compiled catalog with one instance of that resource managed. If a comprehensive solution is unrealistic, accomplishing this with the package & service resources alone would be absolutely killer. Please let me know if I can provide more background information on the problem and I apologize if this is a duplicate. I did attempt to find a similar ticket, but did not find one. -- 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.
