It looks like we need a way of telling r10k to not look for a global r10k.yaml file.
bundle exec onceover run spec
r10k: Runtime error: #<R10K::Error: Git provider 'rugged' is not functional.>
Error while running: #<RuntimeError: r10k could not install all required modules>
I am attempting to run onceover on a PE 2019.1 master. I think what's happening here is r10k is seeing 'rugged' specified as the git provider specified in /etc/puppetlabs/r10k/r10k.yaml. I have GEM_HOME set to ~/gems and have installed bundler there, and bundler has then installed onceover and it's dependencies there. I do not have rugged in the Gemfile and so r10k gets upset. I do not want to add rugged to the Gemfile because that requires installing cmake and other things for it to compile. I am using the puppet agent's ruby, which does have the rugged gem, so if we think onceover would run ok with r10k using rugged, then I could probably figure out a way to have it see the puppet agent's rugged gem.
It looks like we need a way of telling r10k to not look for a global r10k.yaml file.
I am attempting to run onceover on a PE 2019.1 master. I think what's happening here is r10k is seeing 'rugged' specified as the git provider specified in
/etc/puppetlabs/r10k/r10k.yaml. I have GEM_HOME set to~/gemsand have installed bundler there, and bundler has then installed onceover and it's dependencies there. I do not have rugged in the Gemfile and so r10k gets upset. I do not want to add rugged to the Gemfile because that requires installing cmake and other things for it to compile. I am using the puppet agent's ruby, which does have the rugged gem, so if we think onceover would run ok with r10k using rugged, then I could probably figure out a way to have it see the puppet agent's rugged gem.