Thanks, Darin. I must say that it makes me a bit nervous to see items with a "2.0.0" ruby version listed in your load path, though; the JRuby that is embedded in puppet server is intended to be compatible (at the language level) with a 1.9.3 ruby. It seems like maybe the right solution here is to think about doing OS packages for gems like hiera that put the correct version of the gem directly in the jruby-gem path that Puppet Server expects.
Thanks for creating the ticket, I'll chime in on it and ping our release engineering folks. On Fri, Oct 17, 2014 at 9:18 AM, Darin Perusich <[email protected]> wrote: > Hi Chris, > > Adding the path of the hiera lib directory to the ruby-load-path > works, I just hadn't gone that deep when trying different paths. I'll > create a Jira ticket for this, perhaps adding a gems-load-path > parameter for system "gems" which is recursively searched. > > os-settings: { > ruby-load-path: [ /usr/lib64/ruby/vendor_ruby/2.0.0, > /usr/lib64/ruby/site_ruby/2.0.0, > /usr/lib64/ruby/gems/2.0.0/gems/hiera-1.2.1/lib > ] > } > -- > Later, > Darin > > > On Fri, Oct 17, 2014 at 10:28 AM, Chris Price <[email protected]> > wrote: > > On Fri, Oct 17, 2014 at 7:21 AM, Darin Perusich <[email protected]> > wrote: > >> > >> Hi Chris, > >> > >> Much like how installing puppetserver from yum.puppetlabs.com would > >> leverage the hiera package for hiera support, I need the same as I'm > >> packaging it in the open build service for opensuse/sles. > >> > >> I've tried added it to the ruby-load-path in os-settings.conf but that > >> failed, which kinda expected. > > > > > > I see; so the gem is being installed via system packages rather than via > the > > gem tool itself. Hmmm. Well, the ruby-load-path is what we use to make > > that work on RHEL/debian... so I'm a little surprised actually that that > > doesn't sound like it works for you. We could maybe look into adding a > > gem-path setting as an alternative to or replacement for gem-home, but > I'm > > not sure we'll have any way to know whether that fixes the issue you're > > hitting until we actually have it wired up. > > > > Seems like maybe the best thing to do for now is to open up a Jira > ticket. > > In the interim I still think there is probably *some* value that you > could > > add to your ruby-load-path as a temporary workaround if you need one; it > > just may have to drill all the way down into the hiera lib directory. > > > > > > -- > > You received this message because you are subscribed to the Google Groups > > "Puppet Developers" 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-dev/CAMx1QfLdsH3Oj9eF9T%3DE1T37d4s4kMSXSH-Ow4oMstwaLWTDzA%40mail.gmail.com > . > > > > For more options, visit https://groups.google.com/d/optout. > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Developers" 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-dev/CADaviKtsu%2BKa6o1%2BdRgfAp6aOSFBYStUpn9TE4g%3DopZJ5R8%3DWA%40mail.gmail.com > . > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Puppet Developers" 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-dev/CAMx1Qf%2BRdhvJWPbUyojtX0acFsuBv3MHudJHdQTCfaFhe9Pu2g%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
