You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

Paul Hinze 73d20b4c58 providers/aws: add root_block_device to aws_instance ... AWS provides a single `BlockDeviceMapping` to manage three different kinds of block devices: (a) The root volume (b) Ephemeral storage (c) Additional EBS volumes Each of these types has slightly different semantics [1]. (a) The root volume is defined by the AMI; it can only be customized with `volume_size`, `volume_type`, and `delete_on_termination`. (b) Ephemeral storage is made available based on instance type [2]. It's attached automatically if _no_ block device mappings are specified, and must otherwise be defined with block device mapping entries that contain only DeviceName set to a device like "/dev/sdX" and VirtualName set to "ephemeralN". (c) Additional EBS volumes are controlled by mappings that omit `virtual_name` and can specify `volume_size`, `volume_type`, `delete_on_termination`, `snapshot_id`, and `encryption`. After deciding to ignore root block devices to fix #859, we had users with configurations that were attempting to manage the root block device chime in on #913. Terraform does not have the primitives to be able to properly handle a single collection of resources that is partially managed and partially computed, so our strategy here is to break out logical sub-resources for Terraform and hide the BlockDeviceMapping inside the provider implementation. Now (a) is supported by the `root_block_device` sub-resource, and (b) and (c) are still both merged together under `block_device`, though I have yet to see ephemeral block devices working properly. Looking into possibly separating out `ephemeral_block_device` and `ebs_block_device` sub-resources as well, which seem like the logical next step. We'll wait until the next big release for this, though, since it will break backcompat. [1] http://bit.ly/ec2bdmap [2] http://bit.ly/instancestorebytype Fixes #913 Refs #858		11 years ago
..
autoscale.html.markdown	Revert "docs: consistent use of array configuration syntax"	11 years ago
db_instance.html.markdown	Support storage_type parameter for aws_db_instance	11 years ago
db_parameter_group.html.markdown	Implement apply_method for RDS parameters	11 years ago
db_security_group.html.markdown	Revert "docs: consistent use of array configuration syntax"	11 years ago
db_subnet_group.html.markdown	Revert "docs: consistent use of array configuration syntax"	11 years ago
eip.html.markdown	…
elb.html.markdown	Clarify usage of `aws_elb`	11 years ago
instance.html.markdown	providers/aws: add root_block_device to aws_instance	11 years ago
internet_gateway.html.markdown	Add docs for AWS IG tags	11 years ago
key_pair.html.markdown	Add docs for key_pair AWS resource	11 years ago
launch_config.html.markdown	Added missing line for aws_launch_configuration resource on AWS provider docs	11 years ago
main_route_table_assoc.html.markdown	providers/aws: docs for aws_main_route_table_association	11 years ago
network_acl.html.markdown	…
route53_record.html.markdown	Revert "docs: consistent use of array configuration syntax"	11 years ago
route53_zone.html.markdown	…
route_table.html.markdown	allow vpc_peering_connection_id in aws_route_table	11 years ago
route_table_assoc.html.markdown	…
s3_bucket.html.markdown	…
security_group.html.markdown	adding documentation	11 years ago
subnet.html.markdown	…
vpc.html.markdown	providers/aws: docs for aws_main_route_table_association	11 years ago
vpc_peering.html.markdown	allow update	11 years ago