dde94a3ce7
The benefits of the following "breaking change" are the following: - default behaviour naturally fits with most common usage (i.e. always connect with Vagrant SSH settings) - the autogenerated inventory is more consistent by providing both the SSH username and private key. - no longer needed to explain how to override Ansible `remote_user` parameters Important: With the `force_remote_user` option, people still can fall back to the former behavior (prior to Vagrant 1.8.0), which means that Vagrant integration capabilities are still quite open and flexible. |
||
|---|---|---|
| .. | ||
| commands | ||
| communicators/winrm | ||
| guests | ||
| kernel_v2/config | ||
| providers | ||
| provisioners | ||
| pushes | ||
| synced_folders | ||