haskal
/
vagrant
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Merge pull request #7719 from dragon788/patch-1 

Corrected typo, added a couple examples.
This commit is contained in:
Chris Roberts 2016-10-26 10:25:04 -07:00 committed by GitHub
parent fff1c72684 977630c7de
commit 36d0722366
1 changed files with 8 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
website/source/docs/provisioning/basic_usage.html.md
View File

@ -48,7 +48,8 @@ end
The benefit of the block-based syntax is that with more than a couple options
it can greatly improve readability. Additionally, some provisioners, like
the Chef provisioner, have special methods that can be called within that
block to ease configuration that cannot be done with the key/value approach.
block to ease configuration that cannot be done with the key/value approach,
or you can use this syntax to pass arguments to a shell script.
The attributes that can be set in a single-line are the attributes that
are set with the `=` style, such as `inline = "echo hello"` above. If the
@ -107,6 +108,11 @@ Vagrant.configure("2") do |config|
end
```
You can also set `run:` to `"never"` if you have an optional provisioner
that you want to mention to the user in a "post up message" or that
requires some other configuration before it is possible, then call this
with `vagrant provision --provision-with bootstrap`.
If you are using the block format, you must specify it outside
of the block, as shown below:
@ -150,7 +156,7 @@ The ordering of the provisioners will be to echo "foo", "baz", then
ordering is _outside in_.
With multiple provisioners, use the `--provision-with` setting along
with names to get more fine grainted control over what is run and when.
with names to get more fine grained control over what is run and when.
## Overriding Provisioner Settings