On Monday, June 13, 2016 at 5:21:42 AM UTC-5, Justin Rowles wrote: > > At risk of bumping a now truly ancient thread (which I found because I > have a 3rd party module and one of my own which both want to control a > specific package), I don't see why puppet should complain when two > identical (or at least non-contradictory) invocations of the same resource > are found. >
You have necro'd a thread that was already necro'd once before. I guess if history is any indicator, we can expect it to be necro'd again some time around July, 2018. But let's see whether we can defy history, shall we? In any case, there is no answer to the question of *why* Puppet works as it does in this regard that will be of any help to you. That is, no answer to that question will help you resolve your present issue. There has been a great deal of discussion of the general topic over the years; in fact, I think it may be Puppet's single most controversial characteristic. Yet it endures. If you really want to discuss why, then that discussion would be better conducted over on puppet-developers. If you just want to vent, then ok, get it out of your system. If you have specific questions about how to apply some of the plethora of information and advice that is already available, or if you have some pattern that you think has not been adequately covered, then by all means, please do start a new thread to discuss it. John -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/67379af9-8f81-419a-a86f-c92a1af558bd%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
