Commit Graph

15 Commits (8b586ad055932fce06ff93ac405dc2103cb8662d)

Author SHA1 Message Date
Gilles Cornu dc60e08aa0 Documentation: Update the Vagrant Guide
This is an attempt to solve #7665.

Revert the change applied by f56a6e0951
(#12310), as the inventory generated by Vagrant still rely on the legacy
`_ssh` setting names for backwards compatibility reasons.
See also https://github.com/mitchellh/vagrant/issues/6570
9 years ago
Sandra Wills 32cb2fa215 removed repetition of note and replaced with an include directive
ansible_ssh_* changes from 1.9 to 2.0, original note made into a separate file
for easier editing, and an include for this new file added to each of the 6 file affected
by this change
9 years ago
Sandra Wills 748ff72b6b fixed typo, depricated --> deprecated, in all 6 notes 9 years ago
Sandra Wills f24fbb04c9 note modified a bit, then reviewed/approved by jmartin
Ansible 2.0 has depricated the “ssh” from ansible_ssh_user,
ansible_ssh_host, and ansible_ssh_port to become ansible_user,
ansible_host, and ansible_port. If you are using a version of
Ansible prior to 2.0, you should continue using the older style
variables (ansible_ssh_*). These shorter variables are ignored,
without warning, in older versions of Ansible.
9 years ago
Sandra Wills 6af2b2a4cb added note about ansible_ssh_* change
added a note like the following to each file hit with unlabled 2.0 changes...
Ansible 2.0 moved away from using ansible_ssh_* variables to accepting
ansible_* variables. If you are using a version of Ansible prior to 2.0,
you should continue using the older style variables (ansible_ssh_*), such
as ansible_ssh_user instead of ansible_user and ansible_ssh_port instead of
ansible_port, which appear in the following content. These shorter variables
are ignored, without warning, in older versions of Ansible.
9 years ago
Abhijit Menon-Sen f56a6e0951 Rename ansible_ssh_{host,port,user} in docs to ansible_*
The _ssh variants will continue to work, but the shorter, more generic
names are preferred now.
9 years ago
Erika Heidi c20c6d4eb4 [Vagrant guide] Updating private key location
Since Vagrant 1.7.0, released in December 2014, the private key file is autogenerated and has a new location - check the changelog for more info: [version 1.7.0 changelog](https://github.com/mitchellh/vagrant/blob/master/CHANGELOG.md#170-december-9-2014)
10 years ago
Nándor István Krácser 18b41ebda5 Ansible inventory file location fixed
according to the official Vagrant guide at http://docs.vagrantup.com/v2/provisioning/ansible.html
11 years ago
Christian Berendt 58ff9cd7c8 fixed typos found by RETF rules in RST files
rules are avaialble at https://en.wikipedia.org/wiki/Wikipedia:AutoWikiBrowser/Typos
11 years ago
Eric Dahl 9309b6b0e4 Documentation: fix various small typos 11 years ago
Michael DeHaan 041cea134f New Sphinx theme has sidebar navigation so don't need TOC on each page. 11 years ago
Michael F. Booth 8a19b595c7 Fix "manual" ansible-playbook example in guide_vagrant.rst
The given example is trying to load an inventory file with the -i option, so it should probably be given the actual Vagrant-written inventory file name. I contemplated using 'vagrant_ansible_inventory_default' instead (which is what my Vagrant demo actually creates) but 'vagrant_ansible_inventory_machinename' is more consistent with the existing example in the docs.
11 years ago
Tim Gerla fb3d5d6589 elaborate on a couple of sections 11 years ago
Tim Gerla 1cd71b7899 fix up word wrapping 11 years ago
Tim Gerla 7adf33ed41 add a topical guide for Vagrant integration 11 years ago