From 670cadae9faf1d782d398e500375fa77af79f718 Mon Sep 17 00:00:00 2001 From: Michael C Date: Thu, 10 Oct 2019 20:44:14 +0200 Subject: [PATCH] docs: Add clarification about ansible.limit in static inventory usecase --- website/source/docs/provisioning/ansible_intro.html.md | 1 + 1 file changed, 1 insertion(+) diff --git a/website/source/docs/provisioning/ansible_intro.html.md b/website/source/docs/provisioning/ansible_intro.html.md index 6e0fb0716..620cbf785 100644 --- a/website/source/docs/provisioning/ansible_intro.html.md +++ b/website/source/docs/provisioning/ansible_intro.html.md @@ -239,6 +239,7 @@ config.vm.network :private_network, ip: "192.168.111.222" **Notes:** - The machine names in `Vagrantfile` and `ansible.inventory_path` files should correspond, unless you use `ansible.limit` option to reference the correct machines. + - The `ansible.inventory_path` option by default is only scoped to apply to a single guest in the inventory file, and does not apply to all defined guests. To allow access to all available machines in the inventory, it is necessary to set `ansible.limit = "all"`. - The SSH host addresses (and ports) must obviously be specified twice, in `Vagrantfile` and `ansible.inventory_path` files. - Sharing hostnames across Vagrant host and guests might be a good idea (e.g. with some Ansible configuration task, or with a plugin like [`vagrant-hostmanager`](https://github.com/smdahlen/vagrant-hostmanager)).