From 35f7c2c4c984321f5d65a1ad62bd6970d31d162a Mon Sep 17 00:00:00 2001 From: Gilles Cornu Date: Sat, 22 Oct 2016 00:58:53 +0200 Subject: [PATCH] provisioners/ansible: Fix raw_arguments documentation Precise valid and invalid syntax for `raw_arguments` array values, especially for the `ansible` remote provisioner. Close GH-7890 [ci skip] --- website/source/docs/provisioning/ansible_common.html.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/website/source/docs/provisioning/ansible_common.html.md b/website/source/docs/provisioning/ansible_common.html.md index 0bef8ac50..d76d6cfa0 100644 --- a/website/source/docs/provisioning/ansible_common.html.md +++ b/website/source/docs/provisioning/ansible_common.html.md @@ -114,7 +114,11 @@ Some of these options are for advanced usage only and should not be used unless It is an *unsafe wildcard* that can be used to apply Ansible options that are not (yet) supported by this Vagrant provisioner. As of Vagrant 1.7, `raw_arguments` has the highest priority and its values can potentially override or break other Vagrant settings. - Example: `['--check', '-M /my/modules']`). + Examples: + - `['--check', '-M', '/my/modules']` + - `["--connection=paramiko", "--forks=10"]` + + **Caveat:** The `ansible` provisioner does not support whitespace characters in `raw_arguments` elements. Therefore **don't write** something like `["-c paramiko"]`, which will result with an invalid `" parmiko"` parameter value. - `skip_tags` (string or array of strings) - Only plays, roles and tasks that [*do not match* these values will be executed](https://docs.ansible.com/playbooks_tags.html).