The requirement to "deploy code in complex ways" sounds like an "enterprise" thing. On the one hand, these companies may have few spare cycles for synchronizing configurations across disparate customer-facing products. On the other hand, there can be certain strategically important environments whose change managment is subject to agreements with major customers and operate on a different set of timelines. On the third hand, there can be a myriad of currently-unknown reasons why you would need the flexibility to do something complicated.
Not to say that r10k versus other things (monolithic repositories for one) haven't been a subject of intense debate here too, they have. My current thinking is that we can more maintainably use a subset of r10k functionality than bolt stuff on to a simpler system on an ad-hoc basis. I think of things like ldap/r10k/radius as items which it really helps to already have when you start getting large and complicated problems. On Thu, Jan 28, 2016 at 06:40:15AM -0800, Alex Harvey wrote: > Hi all, > I am interested in the future of the Librarian-puppet project - to find > out how many people are still using it, and if there are people out there > who actually prefer it over R10K. > I recently looked into R10K for a few projects I was working on, and I > found it to be surprisingly complicated. It had many features I didn't > seem to need, features that overlap with features provided by > Jenkins/Bamboo, and appeared designed with a view to helping people deploy > code in complex ways, help them to test short lived branches on Puppet > masters, etc. This might have made sense once, but if you're doing all > your development in a test-driven fashion in Vagrant/Rspec-puppet/Beaker, > I can't see a need for R10K's features, and concluded it was mainly just a > lot harder to understand than Librarian-puppet. I do see that it performs > better, but again, Librarian-puppet has never been a bottleneck. > Other views most appreciated. > With best regards, > Alex > > -- > 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 [1]puppet-users+unsubscr...@googlegroups.com. > To view this discussion on the web visit > > [2]https://groups.google.com/d/msgid/puppet-users/639366f5-0fc8-47f8-a1ed-541c79dbc07c%40googlegroups.com. > For more options, visit [3]https://groups.google.com/d/optout. > > References > > Visible links > 1. mailto:puppet-users+unsubscr...@googlegroups.com > 2. > https://groups.google.com/d/msgid/puppet-users/639366f5-0fc8-47f8-a1ed-541c79dbc07c%40googlegroups.com?utm_medium=email&utm_source=footer > 3. https://groups.google.com/d/optout -- 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/20160128162936.GA15474%40iniquitous.heresiarch.ca. For more options, visit https://groups.google.com/d/optout.
