Hi, On 02/08/2016 06:28, Geoff Nichols wrote:
>> 1. So it concerns gems installed via this command: >> >> /opt/puppetlabs/puppet/bin/gem install $gem_foo >> >> Is it correct? >> > > Yes, that's correct. Ok. >> 2. And what about gems installed via this command? >> >> /opt/puppetlabs/bin/puppetserver gem install $gem_foo >> >> Is a re-installation after the upgrade needed too? >> > > No, gems installed using Puppet Server's `puppetserver gem install` > subcommand use a separate (JRuby) interpreter. Those gems should not be > affected and should not require re-installation after the upgrade. Ok. Thanks for your answer Geoff. But, in this case, I don't really see the impact of this migration Ruby 2.1 => 2.3 in a classical "clients/server" architecture (I mean the impact for the _user_ because I imagine there are eventually impacts for the puppet-agent developer ;)). For instance, I have installed hiera-eyaml but it's for the server (so I have made "/opt/puppetlabs/bin/puppetserver gem install hiera-eyaml"). I have installed hiera-eyaml with the "puppet" command too, to just have the "eyaml" command in my PATH too (ie in /opt/puppetlabs/puppet/bin/) but it's just for convenience. Another example: if I have ruby functions in my puppet modules, these functions are executed in the server side, so no impact too in this case, correct ? In fact, where could be the "user" impacts of this change? The only thing I see is "custom facts" in modules which are Ruby code executed in clients side. Are there another things which I need to check carefully in the clients/server architecture? Regards. François Lafont -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/8eeb0ea2-f03b-e2ec-e98e-9600e848b4ac%40gmail.com. For more options, visit https://groups.google.com/d/optout.
