haskal
/
vagrant
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Update ansible_common.html.md 

Added an explanation about locating ansible roles in a non vagrant writeable directory
This commit is contained in:
Rémy G 2018-05-24 14:54:15 +02:00 committed by GitHub
parent 4b896d9945
commit 57f12d115c
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 3 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
website/source/docs/provisioning/ansible_common.html.md
View File

@ -89,7 +89,7 @@ Some of these options are for advanced usage only and should not be used unless
ansible.playbook = "/vagrant/playbook.yml"
ansible.galaxy_role_file = "/vagrant/requirements.yml"
ansible.galaxy_role_path = "/etc/ansible/roles"
ansible.galaxy_command = "ansible-galaxy install --force --ignore-certs --role-file=%{role_file} --roles-path=%{roles_path}"
ansible.galaxy_command = "sudo ansible-galaxy install --force --ignore-certs --role-file=%{role_file} --roles-path=%{roles_path}"
end
end
```
@ -104,6 +104,8 @@ Some of these options are for advanced usage only and should not be used unless
By default, this option is set to `nil`, which means that the Galaxy roles will be installed in a `roles` subdirectory located in the parent directory of the `playbook` file.
Be careful that `ansible-galaxy` command is by default run as vagrant user. Setting `galaxy_roles_path` to a folder like `/etc/ansible/roles` will fail silently : unable to write there, `ansible-galaxy` will extract the role a second time in a `/home/vagrant/.ansible/roles/`. Then if your playbook uses become: true user: root, it will fail with a "role was not found". To work around that, use `ansible.galaxy_command` to include a `sudo ansible-galaxy ...`.
- `groups` (hash) - Set of inventory groups to be included in the [auto-generated inventory file](/docs/provisioning/ansible_intro.html).
Example: