You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Did you have some kind of workaround for air-gapped systems @paveljeloudovski? I am running into the same issues with an air-gapped environment. I am trying to determine the most practical path forward for resolving or working around the hard coded GitHub URL and rubygems URL.
Yes.
I'll have to check exactly what I did when at work.
In general.
What we have is a local ruby gems repo based on artifactory(but it was just a web server before) and there is a cookbook that we run on all servers that configures the ruby to work with repo at compile time.
So all the gems are installed from there. I can share the code for that if you need.
I'll have to check if this is what solved this issue or I had to do something more.
Found this issue while trying to install a private supermarket with supermarket-omnibus-cookbook.
In chef-ingredient/libraries/helpers.rb is the code
I've noticed in my own recipes that if the version you specify with a gem is the latest version it will fail to find it on rubygems.org.
Only reason I haven't done a pull request myself is because I'm unsure of how to lock to version 1.1.0 when it's the latest version of the gem.
The text was updated successfully, but these errors were encountered: