On Monday, July 14, 2014 5:22:13 AM UTC-5, Jose Luis Ledesma wrote: > > Hi, > > Shall this be a bug? Teorically a exported resource is not applied in > the managed node if you don't collect it, so it should not collide with an > "applied" resource. thoughs? > >
I understand your argument, but it is by no means clear that the scope for the uniqueness constraint should be the catalog into which the resource is placed. In fact, Puppet consistently works differently, as duplicate virtual resources are also not allowed, even if there is no attempt to collect or realize them at all. The constraint can be conceptualized as requiring uniqueness of all the resources known within the scope of a given catalog compilation run. It's a valid design decision. 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/7c204acf-2a69-4549-89fe-444a10f7abe7%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
