Ensure chef runs are successful when gitlab.com is unavailable.
During our dry run in production, chef converges failed because they tried to pull recaptcha from gitlab.com which was down. If we needed to make a cookbook change with gitlab.com down, we would be blocked.
We need to provide a way to make sure we are not blocked and can update cookbooks with gitlab.com down.
Edited by John Jarvis