c7b35dd6bc
added `post-processors` block to run chained post-processors after a build. Before this, defining multiple `post-processor` blocks after provisioning steps would run them sequentially, now doing this makes them start from the build's artifact. To queue post-processors you now have to define them in a `post-processors` block. This is a breaking change. |
||
---|---|---|
.. | ||
aws-builds.pkr.hcl | ||
fruit_string.pkr.hcl | ||
virtualbox-builds.pkr.hcl |