On 12/31/2012 03:18 PM, Matthew Barr wrote:
Sorry to reply to myself.. but option #1 doesn't work. (It works for resources, but not classes. Silly me.) So: should forge modules use repo's explicitly? or is there already a standard design pattern that implements a parameter for repos? else… I guess I'll end up writing one :)
What I've done is to let the baseurl for the repo optional be passed into the class as a parameter - that fixes it from my perspective.
Jason -- You received this message because you are subscribed to the Google Groups "Puppet Users" 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-users?hl=en.
