Always delete the Packer builder VM at the end of the build #2993
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In our content library patch, we had explicitly set the nested
destroy
field in the content library configuration section to"true"
, so Packer builder VMs were getting deleted when the build finishes. When we removed the patch in #2988, the build fell back to image-builder's default behavior of leaving around VMs. In this PR, I am patching image-builder so we get the old behavior back.By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.