Issue #18490 has been updated by eric sorenson.

Category set to modules
Assignee changed from eric sorenson to Ryan Coleman
Keywords deleted (backlog)

I've had quite a few conversations about this lately and the proposal to permit 
duplicate, non-conflicting resources and it seems prohibitively troublesome. 
Specifically, two things are deal-breakers:

1. You lose the ability to back-track from a resource to its origin, and 
therefore the intent behind its inclusion in the catalog. With the upcoming 
changes to promote modules to first-class citizens inside Puppet, this seems 
confusing and contradictory.
2. The second, thornier problem is that if there are dependencies to or from 
resources which are duplicated it opens the door to a resource being required 
to exist in two different parts of the graph, while not technically being a 
loop. (I confess this one makes my head hurt a little bit to think about)

Ryan (and other watchers, are there other avenues we can explore to accomplish 
the goal? It seems like we have a good conversation going on, so let's continue 
that, but I'm going to drop this out of the platform team backlog until some 
course of action becomes clear.

----------------------------------------
Feature #18490: Duplicate resources can make re-usable Forge modules difficult
https://projects.puppetlabs.com/issues/18490#change-82544

Author: Ryan Coleman
Status: Investigating
Priority: Normal
Assignee: Ryan Coleman
Category: modules
Target version: 3.x
Affected Puppet version: 
Keywords: 
Branch: 


[EDIT] Re-working this description based on feedback in comment #7. 

User installs module A to provide a web application. 

User installs module B to provide a database server.

Both module A and module B declare a package resource for foo. 

User declares classes from both module A and B on the same node.

User receives duplicate resource declaration error, Puppet run fails. 


I wish to prevent customers of Forge and Puppet from experiencing this 
frustration, when both classes really do need that package for their 
functionality but cannot be used together as-is. I'd love direct questions if 
you need to understand this better from my perspective.



-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to