@markuslatvala @djlink this kind of stuff drives me nuts

Sometimes Chef runs will fail because if a cookbook depends on a ruby gem it always checks rubygems.org even if it's already installed. So if the site goes down or is overloaded ... it's so dumb.

So then you gotta setup a rubygems proxy and try to use that.

They did finally add a setting to not do this but last I checked it wasn't in a release yet.

How has this been default behavior for over a decade? How can you even quantify the amount of wasted bandwidth and electricity?