docs/ansible: Align the "warn/info" notices style
Motivated by the 4d546a58e1243168f58e20ca53cab71b31e44ae9 changes.
This commit is contained in:
parent
8834afbd8e
commit
e2621a42fc
|
@ -14,10 +14,8 @@ description: |-
|
||||||
The Vagrant Ansible provisioner allows you to provision the guest using [Ansible](http://ansible.com) playbooks by executing **`ansible-playbook` from the Vagrant host**.
|
The Vagrant Ansible provisioner allows you to provision the guest using [Ansible](http://ansible.com) playbooks by executing **`ansible-playbook` from the Vagrant host**.
|
||||||
|
|
||||||
<div class="alert alert-warning">
|
<div class="alert alert-warning">
|
||||||
<strong>Warning:</strong> If you are not familiar with Ansible and Vagrant already,
|
<strong>Warning:</strong>
|
||||||
I recommend starting with the <a href="/docs/provisioning/shell.html">shell
|
If you are not familiar with Ansible and Vagrant already, I recommend starting with the <a href="/docs/provisioning/shell.html">shell provisioner</a>. However, if you are comfortable with Vagrant already, Vagrant is a great way to learn Ansible.
|
||||||
provisioner</a>. However, if you are comfortable with Vagrant already, Vagrant
|
|
||||||
is a great way to learn Ansible.
|
|
||||||
</div>
|
</div>
|
||||||
|
|
||||||
## Setup Requirements
|
## Setup Requirements
|
||||||
|
@ -74,7 +72,10 @@ This section lists the _specific_ options for the Ansible (remote) provisioner.
|
||||||
|
|
||||||
The default value is `true`.
|
The default value is `true`.
|
||||||
|
|
||||||
**Note:** This option was introduced in Vagrant 1.8.0. Previous Vagrant versions behave like if this option was set to `false`.
|
<div class="alert alert-info">
|
||||||
|
<strong>Compatibility Note:</strong>
|
||||||
|
This option was introduced in Vagrant 1.8.0. Previous Vagrant versions behave like if this option was set to `false`.
|
||||||
|
</div>
|
||||||
|
|
||||||
- `host_key_checking` (boolean) - require Ansible to [enable SSH host key checking](https://docs.ansible.com/intro_getting_started.html#host-key-checking).
|
- `host_key_checking` (boolean) - require Ansible to [enable SSH host key checking](https://docs.ansible.com/intro_getting_started.html#host-key-checking).
|
||||||
|
|
||||||
|
@ -122,9 +123,10 @@ N = 3
|
||||||
end
|
end
|
||||||
```
|
```
|
||||||
|
|
||||||
**Caveats:**
|
<div class="alert alert-info">
|
||||||
|
<strong>Tip:</strong>
|
||||||
If you apply this parallel provisioning pattern with a static Ansible inventory, you will have to organize the things so that [all the relevant private keys are provided to the `ansible-playbook` command](https://github.com/mitchellh/vagrant/pull/5765#issuecomment-120247738). The same kind of considerations applies if you are using multiple private keys for a same machine (see [`config.ssh.private_key_path` SSH setting](/docs/vagrantfile/ssh_settings.html)).
|
If you apply this parallel provisioning pattern with a static Ansible inventory, you will have to organize the things so that [all the relevant private keys are provided to the `ansible-playbook` command](https://github.com/mitchellh/vagrant/pull/5765#issuecomment-120247738). The same kind of considerations applies if you are using multiple private keys for a same machine (see [`config.ssh.private_key_path` SSH setting](/docs/vagrantfile/ssh_settings.html)).
|
||||||
|
</div>
|
||||||
|
|
||||||
### Force Paramiko Connection Mode
|
### Force Paramiko Connection Mode
|
||||||
|
|
||||||
|
|
|
@ -150,7 +150,10 @@ Some of these options are for advanced usage only and should not be used unless
|
||||||
- `['--check', '-M', '/my/modules']`
|
- `['--check', '-M', '/my/modules']`
|
||||||
- `["--connection=paramiko", "--forks=10"]`
|
- `["--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.
|
<div class="alert alert-warn">
|
||||||
|
<strong>Attention:</strong>
|
||||||
|
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.
|
||||||
|
</div>
|
||||||
|
|
||||||
- `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).
|
- `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).
|
||||||
|
|
||||||
|
|
|
@ -14,10 +14,8 @@ description: |-
|
||||||
The Vagrant Ansible Local provisioner allows you to provision the guest using [Ansible](http://ansible.com) playbooks by executing **`ansible-playbook` directly on the guest machine**.
|
The Vagrant Ansible Local provisioner allows you to provision the guest using [Ansible](http://ansible.com) playbooks by executing **`ansible-playbook` directly on the guest machine**.
|
||||||
|
|
||||||
<div class="alert alert-warning">
|
<div class="alert alert-warning">
|
||||||
<strong>Warning:</strong> If you are not familiar with Ansible and Vagrant already,
|
<strong>Warning:</strong>
|
||||||
I recommend starting with the <a href="/docs/provisioning/shell.html">shell
|
If you are not familiar with Ansible and Vagrant already, I recommend starting with the <a href="/docs/provisioning/shell.html">shell provisioner</a>. However, if you are comfortable with Vagrant already, Vagrant is a great way to learn Ansible.
|
||||||
provisioner</a>. However, if you are comfortable with Vagrant already, Vagrant
|
|
||||||
is a great way to learn Ansible.
|
|
||||||
</div>
|
</div>
|
||||||
|
|
||||||
## Setup Requirements
|
## Setup Requirements
|
||||||
|
@ -67,7 +65,10 @@ This section lists the _specific_ options for the Ansible Local provisioner. In
|
||||||
- The `version` option is set to `"latest"`.
|
- The `version` option is set to `"latest"`.
|
||||||
- The current Ansible version does not correspond to the `version` option.
|
- The current Ansible version does not correspond to the `version` option.
|
||||||
|
|
||||||
**Attention:** There is no guarantee that this automated installation will replace a custom Ansible setup, that might be already present on the Vagrant box.
|
<div class="alert alert-warning">
|
||||||
|
<strong>Attention:</strong>
|
||||||
|
There is no guarantee that this automated installation will replace a custom Ansible setup, that might be already present on the Vagrant box.
|
||||||
|
</div>
|
||||||
|
|
||||||
- `install_mode` (`:default`, `:pip`, or `:pip_args_only`) - Select the way to automatically install Ansible on the guest system.
|
- `install_mode` (`:default`, `:pip`, or `:pip_args_only`) - Select the way to automatically install Ansible on the guest system.
|
||||||
|
|
||||||
|
@ -148,7 +149,10 @@ This section lists the _specific_ options for the Ansible Local provisioner. In
|
||||||
|
|
||||||
When this option is set to `"latest"`, no version check is applied.
|
When this option is set to `"latest"`, no version check is applied.
|
||||||
|
|
||||||
**Warning:** It is currently possible to use this option to specify which version of Ansible must be automatically installed, but only in combination with the `install_mode` set to `:pip`.
|
<div class="alert alert-info">
|
||||||
|
<strong>Tip:</strong>
|
||||||
|
It is currently possible to use this option to specify which version of Ansible must be automatically installed, but <strong>only</strong> in combination with the `install_mode` set to <strong>`:pip`</strong>.
|
||||||
|
</div>
|
||||||
|
|
||||||
## Tips and Tricks
|
## Tips and Tricks
|
||||||
|
|
||||||
|
|
Loading…
Reference in New Issue