From 0e8eb61699471f0cdeab6e1e1033c6716413f77b Mon Sep 17 00:00:00 2001 From: Sargun Dhillon Date: Mon, 11 Mar 2019 11:40:49 -0700 Subject: [PATCH] Add documentation around new behaviour of ami_block_device_mappings Previously, if ami_block_device_mappings was set, and you were building from an existing image, it would get silently ignored, and changing root_device_name would be ignored. This changes that behaviour, so if ami_block_device_mappings is specified, it's respected. --- website/source/docs/builders/amazon-chroot.html.md | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/website/source/docs/builders/amazon-chroot.html.md b/website/source/docs/builders/amazon-chroot.html.md index 3b97c38eb..f62914808 100644 --- a/website/source/docs/builders/amazon-chroot.html.md +++ b/website/source/docs/builders/amazon-chroot.html.md @@ -173,8 +173,11 @@ each category, the available configuration keys are alphabetized. more [block device mappings](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/block-device-mapping-concepts.html) to the AMI. These will be attached when booting a new instance from your - AMI. Your options here may vary depending on the type of VM you use. The - block device mappings allow for the following configuration: + AMI. If this field is populated, and you are building from an existing source image, + the block device mappings in the source image will be overwritten. This means you + must have a block device mapping entry for your root volume, `root_volume_size `, + and `root_device_name`. `Your options here may vary depending on the type of VM + you use. The block device mappings allow for the following configuration: - `delete_on_termination` (boolean) - Indicates whether the EBS volume is deleted on instance termination. Default `false`. **NOTE**: If this