make block device example less specific

This commit is contained in:
Adrien Delorme 2019-06-19 12:10:08 +02:00
parent 8cea5d409a
commit 433c40d72d
2 changed files with 14 additions and 20 deletions

View File

@ -11,18 +11,15 @@ import (
"github.com/hashicorp/packer/template/interpolate"
)
// 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. Example:
// 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. Example value:
//
// ``` json
// "builders":[{
// "type":"...",
// "ami_block_device_mappings":[{
// [{
// "device_name":"xvda",
// "delete_on_termination":true,
// "volume_type":"gp2"
// }]
// }
// ```
// Documentation for Block Devices Mappings can be found here:
// https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/block-device-mapping-concepts.html

View File

@ -1,16 +1,13 @@
<!-- Code generated from the comments of the BlockDevice struct in builder/amazon/common/block_device.go; DO NOT EDIT MANUALLY -->
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. Example:
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. Example value:
``` json
"builders":[{
"type":"...",
"ami_block_device_mappings":[{
[{
"device_name":"xvda",
"delete_on_termination":true,
"volume_type":"gp2"
}]
}
}]
```
Documentation for Block Devices Mappings can be found here:
https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/block-device-mapping-concepts.html