Note: total experiment and hack, looks nasty, could be awesome:
- Drop the
kitchen.local.yml
into$HOME/.kitchen/config.yml
- Install polipo (with Mac:
brew install polipo
, with Ubuntu:apt-get install polipo
) - Drop
polipo-start
andpolipo-console
somewhere 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
@pmocek Yes, you're right about highly preferring the HTTPS URL over the HTTP one, but I'm majorly cheating here in this testing context to get faster cached packages. Easily something you might want to change in your version. I've updated the YAML with a comment that I hope is slightly clearer.