Note: total experiment and hack, looks nasty, could be awesome:
- Drop the
kitchen.local.ymlinto$HOME/.kitchen/config.yml - Install polipo (with Mac:
brew install polipo, with Ubuntu:apt-get install polipo) - Drop
polipo-startandpolipo-consolesomewhere useful (perhaps$HOME/bin?)
Simply start up polipo in the foreground in a terminal/tmux/screen session with: ~/bin/polipo-start. In your Test Kitchen project verify that caching is enabled by running kitchen diagnose and look for the http_proxy and chef_omnibus_url config options, like in this abbreviated example output:
---
timestamp: 2015-03-06 19:27:56 UTC
kitchen_version: 1.3.1
instances:
default-ubuntu-1204:
state_file: {}
driver:
http_proxy: http://10.0.10.20:8123
https_proxy: http://10.0.10.20:8123
provision_command: env http_proxy=http://10.0.10.20:8123 bash -c 'curl -L
http://www.chef.io/chef/install.sh | bash'
provisioner:
chef_omnibus_url: http://www.chef.io/chef/install.sh
The only chef_omnibus_url that still works with a HTTP proxy cache is http://www.opscode.com/chef/install.sh I'm afraid. The rest (http://www.getchef.com/chef/install.sh, http://www.chef.io/chef/install.sh) send the request to omnitruck-direct.chef.io over HTTPS and the S3 URL is over HTTPS as well.
Tested with Ubuntu 15.04: