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

Update wording on manifest behaviour on build rerun

This commit is contained in:
Manoj 2017-10-24 11:27:22 +05:30 committed by GitHub
parent b3ea9da4f7
commit dbeb48a993
1 changed files with 4 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
website/source/docs/post-processors/manifest.html.md
View File

@ -65,10 +65,11 @@ An example manifest file looks like:
}
```
If I run the build again, my new build will be added to the manifest file rather than replacing it, so you can always grab specific builds from the manifest by uuid.
If the build is run again, the new build artifacts will be added to the manifest file rather than replacing it. It is possible to grab specific build artifacts from the manifest by using `packer_run_uuid`.
The mainfest above was generated from this packer.json:
```
The above mainfest was generated with this packer.json:
```json
{
"builders": [
{