Seems like a problem that people run into all the time, but I haven't found any info on this topic that is in the least satisfying.
I have a monolithic puppet repo that is several years old, and which has one main "module" with several dozen manifests along with files and templates. Currently, this code uses 3rd party/forge modules that are pretty old, and I'd like to update the 3rd party modules (stuff like apt, nginx, node, stdlib, etc...), but I need to do it selectively, since many of our manifests may break in a major-version upgrade. As I create proper modules from the manifests that we have now, the existing "module" should continue to use the versions they're currently using and the new ones should be able to use the latest versions of these modules. Simply installing modules, for example by using 'puppet module install' updates the current version of the module, which resides in our git repo in the modules subdir. Ultimately, it seems that we should move to librarian puppet, but I'm not sure that that solves the basic problem, which is that I need to have multiple versions of the same modules. How do I accomplish this? Thanks. Eric -- 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/835e1fdd-83fc-436e-b1ad-3bee874ff0b1%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
