Merge pull request #13093 from hashicorp/kc.docs-metadata
Devdot Fixes Vagrant Cloud
This commit is contained in:
commit
3a2c79ac77
@ -89,7 +89,9 @@ When using Ansible, it needs to know on which machines a given playbook should r
|
||||
|
||||
The first and simplest option is to not provide one to Vagrant at all. Vagrant will generate an inventory file encompassing all of the virtual machines it manages, and use it for provisioning machines.
|
||||
|
||||
#### Example with the [`ansible`](/vagrant/docs/provisioning/ansible) provisioner
|
||||
#### Ansible provisioner example
|
||||
|
||||
Example with the [`ansible`](/vagrant/docs/provisioning/ansible) provisioner.
|
||||
|
||||
```text
|
||||
# Generated by Vagrant
|
||||
@ -100,7 +102,9 @@ default ansible_host=127.0.0.1 ansible_port=2200 ansible_user='vagrant' ansible_
|
||||
Note that the generated inventory file is stored as part of your local Vagrant environment in
|
||||
`.vagrant/provisioners/ansible/inventory/vagrant_ansible_inventory`.
|
||||
|
||||
#### Example with the [`ansible_local`](/vagrant/docs/provisioning/ansible_local) provisioner
|
||||
#### Ansible local provision
|
||||
|
||||
Example with the [`ansible_local`](/vagrant/docs/provisioning/ansible_local) provisioner
|
||||
|
||||
```text
|
||||
# Generated by Vagrant
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
layout: vagrant-cloud
|
||||
page_page_title: Organizations in Vagrant Cloud
|
||||
page_title: Organizations in Vagrant Cloud
|
||||
---
|
||||
|
||||
## Organizations in Vagrant Cloud
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user