On Wednesday, 10 July 2019 18:39:44 UTC+1, Martin Alfke wrote: > > Hi, > > we never use the puppet module tool. > Instead we mirror upstream modules on an internal git server (including > tags) and reference module, git url and tag in a control-repository > Puppetfile. > When we want to upgrade modules we create a branch and veriffy that > everything still works as expected. > We sometimes even use the octocatalog-diff tool to verify catalogs build > with old and new module versions. > > hth, > Martin >
We do the same as well - we mirror into an internal Git Lab, and use r10k to Git clone the upstream modules onto Puppet Masters like they were our own internal ones. This also helps with our speed; usually when one of our engineers finds a problem in an upstream module that's not fixed in the latest commits, and they want the fix *now*. So we patch it internally immediately then submit that patch upstream, where more often than not it sits for 1-2 weeks waiting for someone to review and merge :-) You still have to pay attention to dependencies and the release notes - sometimes we've done big version jumps and missed some sort of functional change that's bitten us (but that would happen with Forge modules anyway). There's only a handful of modules we pull directly from the Forge, and those are modules that don't have a one-to-one mapping of Git repo to Forge module (such as R.I.'s Choria agent modules). -Luke -- 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/cb00e7de-916d-473c-af00-1dfa46874042%40googlegroups.com.
