Define custom playbook in Vagrantfile

This change allows the playbook used in Vagrant to be
defined by the end user.

This is useful in the case where a developer may want to use
their own playbook that imports Kubespray, but also leverage
the Kubespray Vagrantfile.
This commit is contained in:
edemsea 2018-08-10 13:42:48 -04:00
parent d0d7777d68
commit 80c87db148

4
Vagrantfile vendored
View file

@ -44,6 +44,8 @@ $kube_node_instances_with_disks = false
$kube_node_instances_with_disks_size = "20G" $kube_node_instances_with_disks_size = "20G"
$kube_node_instances_with_disks_number = 2 $kube_node_instances_with_disks_number = 2
$playbook = "cluster.yml"
$local_release_dir = "/vagrant/temp" $local_release_dir = "/vagrant/temp"
host_vars = {} host_vars = {}
@ -157,7 +159,7 @@ Vagrant.configure("2") do |config|
# when all the machines are up and ready. # when all the machines are up and ready.
if i == $num_instances if i == $num_instances
config.vm.provision "ansible" do |ansible| config.vm.provision "ansible" do |ansible|
ansible.playbook = "cluster.yml" ansible.playbook = $playbook
if File.exist?(File.join(File.dirname($inventory), "hosts")) if File.exist?(File.join(File.dirname($inventory), "hosts"))
ansible.inventory_path = $inventory ansible.inventory_path = $inventory
end end