iSharkFly-Docs
/
packer-cn
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

clarify docs 

closes #4208
This commit is contained in:
Matthew Hooker 2017-02-21 15:27:55 -08:00
parent d188db2ab0
commit 0d16df1427
No known key found for this signature in database
GPG Key ID: 7B5F933D9CE8C6A1
1 changed files with 5 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
website/source/intro/getting-started/vagrant.html.md
View File

@ -67,10 +67,11 @@ As you watch the output, you'll notice at the end in the artifact listing that a
Vagrant box was made (by default at `packer_aws.box` in the current directory).
Success!
But where did the AMI go? When using post-processors, Vagrant removes
intermediary artifacts since they're usually not wanted. Only the final artifact
is preserved. This behavior can be changed, of course. Changing this behavior is
covered [in the documentation](/docs/templates/post-processors.html).
But where did the Amazon EBS builder artifact go? When using post-processors,
Vagrant removes intermediary artifacts since they're usually not wanted. Only
the final artifact is preserved. This behavior can be changed, of course.
Changing this behavior is covered [in the
documentation](/docs/templates/post-processors.html).
Typically when removing intermediary artifacts, the actual underlying files or
resources of the artifact are also removed. For example, when building a VMware