17 Commits (4d205ebcf66bb487591e6326d032badfa3c8021b)

Author	SHA1	Message	Date
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
Mitchell Hashimoto	577e2420b0	Revert "docs: consistent use of array configuration syntax" ... This reverts commit 4893eb8b55.	11 years ago
Emil Hessman	4893eb8b55	docs: consistent use of array configuration syntax ... The Terraform configuration syntax defines what arrays are. Use the word array consistently throughout the documentation instead of list. The corresponding JSON datatype is called array as well, and since the Terraform configuration syntax is interoperable with JSON it makes sense to use the term array to describe them.	11 years ago
Sören Blom	efca6b0e8a	only non-default VPC security groups are referenced by ID.	11 years ago
Daniel Malon	1e3065ae11	allow setting the block device virtual_name	12 years ago
Armon Dadgar	38aec9f20b	provide/aws: Document the block device	12 years ago
Seth Vargo	073a0f76c5	Add meta descriptions to all pages	12 years ago
Paul Lewis	3f5a9b70d8	Removing duplicate example and unclosed code block	12 years ago
Sean Herron	3e16190e69	Expands AWS tagging to cover EC2 instances	12 years ago
Ian Delahorne	9f91c4e8c3	Add IAM Instance profile support to AWS instance provider	12 years ago
James Martelletti	78e072e0b6	source_dest_check defaults to true in the code	12 years ago
Mitchell Hashimoto	b3c5b848f9	website: update docs for GH-260]	12 years ago
James Martelletti	821a0a6dc6	Fix typo, proviate_ip -> private_ip	12 years ago
Mitchell Hashimoto	a292625846	website: private IP docs	12 years ago
Luke Chadwick	8d2e232602	Update documentation to reflect the addition of associate_public_ip_address to the aws_instance resource	12 years ago
Jack Pearkes	1d06ecb7a9	website: add note about security group names/ids on instances	12 years ago
Armon Dadgar	6f8732d01f	website: more docs	12 years ago