-
Notifications
You must be signed in to change notification settings - Fork 187
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add support for provision_command #78
Comments
Thanks @cobzilla. This will be included as part of test-kitchen/test-kitchen#329. |
Seems still in progress. |
For anybody looking for hotfix, you can follow this guide http://www.elmund.io/2015/07/05/run-a-script-on-a-test-kitchen-vm-before-converge-starts/ Basically if you specify driver in .kitchen.yml like this: platforms:
- name: fedora-27
driver:
provision: True
vagrantfiles:
- fedora27_provision.rb And then you specify provisioning file Vagrant.configure(2) do |config|
config.vm.provision "shell", inline: <<-SHELL
sudo dnf install -y python2
SHELL
end |
The kitchen-docker driver has a 'provision_command' attribute that allows you to specifically set the command executed when provisioning the Chef client. This is much more flexible than just setting the URL for the script and would really help those of us trapped behind a corporate firewall.
The text was updated successfully, but these errors were encountered: