provider/aws: doc EBS block device mix-match caveats

refs #5706
This commit is contained in:
Paul Hinze 2016-03-25 12:12:01 -05:00
parent 3a44fc7b3f
commit 7501f32721
2 changed files with 4 additions and 0 deletions

View File

@ -109,6 +109,8 @@ Each `ebs_block_device` supports the following:
Modifying any `ebs_block_device` currently requires resource replacement. Modifying any `ebs_block_device` currently requires resource replacement.
~> **NOTE on EBS block devices:** If you use `ebs_block_device` on an `aws_instance`, Terraform will assume management over the full set of non-root EBS block devices for the instance, and treats additional block devices as drift. For this reason, `ebs_block_device` cannot be mixed with external `aws_ebs_volume` + `aws_ebs_volume_attachment` resources for a given instance.
Each `ephemeral_block_device` supports the following: Each `ephemeral_block_device` supports the following:
* `device_name` - The name of the block device to mount on the instance. * `device_name` - The name of the block device to mount on the instance.

View File

@ -11,6 +11,8 @@ description: |-
Provides an AWS EBS Volume Attachment as a top level resource, to attach and Provides an AWS EBS Volume Attachment as a top level resource, to attach and
detach volumes from AWS Instances. detach volumes from AWS Instances.
~> **NOTE on EBS block devices:** If you use `ebs_block_device` on an `aws_instance`, Terraform will assume management over the full set of non-root EBS block devices for the instance, and treats additional block devices as drift. For this reason, `ebs_block_device` cannot be mixed with external `aws_ebs_volume` + `aws_ebs_volume_attachment` resources for a given instance.
## Example Usage ## Example Usage
``` ```