terraform

Commit Graph

Author	SHA1	Message	Date
Paul Hinze	7501f32721	provider/aws: doc EBS block device mix-match caveats refs #5706	10 years ago
Paul Hinze	14ca7e3156	docs: Clarify aws_instance.public_ip w/ EIP behavior Closes #1425	10 years ago
Veaceslav Mindru	1901533bea	aws instance docs associate_public_ip_address - missing explicit mentioning that this is a bool.	10 years ago
Seth Vargo	8dbc43639d	Use HTTPS + www. for links	10 years ago
clint shryock	c94b7c4584	provider/aws: Update docs with t1 instance for accounts with EC2 Classic	10 years ago
clint shryock	e59f39df5f	other m1/ami-1234 clean ups	10 years ago
stack72	8cdfe152d6	Adding the documentation of aws_instance tenancy	11 years ago
clint shryock	d3f41320e8	provider/aws: Update Instance/Spot docs for IP information	11 years ago
Clint Shryock	fde2a400f7	Merge branch 'master' into f-aws-pr-2779 * master: (84 commits) provider/aws: Update to aws-sdk 0.9.0 rc1 use name instead of id - launch configs use the name and not ID Fix typo on heroku_cert example provider/aws: add value into ELB name validation message tests: fix missed test update from last merge update prevent_destroy error message Update CHANGELOG.md Update CHANGELOG.md providers/aws: Update Launch Config. docs to detail naming and lifecycle recommendation release: cleanup after v0.6.3 v0.6.3 Update CHANGELOG.md core: fix deadlock when dependable node replaced with non-dependable one tests: extract deadlock checking test helper core: log every 5s while waiting for dependencies Fixed indentation in a code sample state/remote/s3: match with upstream changes provider/aws: match with upstream changes google: Add example of two-tier app Updating Launch Config Docs for Name attribute ...	11 years ago
Marc Tamsky	521451db4d	provider/aws/aws_instance: add new argument `instance_initiated_shutdown_behavior`, accepts string values of 'stop' or 'terminate'. Signed-off-by: Marc Tamsky <tamsky@users.noreply.github.com>	11 years ago
Mitchell Hashimoto	25fa84974b	update CHANGELOG	11 years ago
Joshua Garnett	d23f534d26	Adding support for detailed monitoring of instances	11 years ago
Clint Shryock	db8805dfa5	provider/aws: Fix issue with restoring from snapshot ID Fixes #1862	11 years ago
Paul Hinze	e1ea427649	provider/aws: support ec2 termination protection closes #1233	11 years ago
Mitchell Hashimoto	b755459ee3	Merge pull request #1358 from rzh/placement_group provider/aws: support for AWS Placement Group	11 years ago
Clint Shryock	3337503eda	update test and documentation for vpc ids in instances	11 years ago
Clint Shryock	97b98b1da6	Merge branch 'master' into f-aws-instance-vpc-sec-ids * master: (511 commits) Update CHANGELOG.md core: avoid diff mismatch on NewRemoved fields during -/+ Update CHANGELOG.md update CHANGELOG Fix minor error in index/count docs terraform: remove debug terraform: when pruning destroy, only match exact nodes, or exact counts up version for dev update CHANGELOG terraform: prune tainted destroys if no tainted in state [GH-1475] update CHANGELOG config/lang: support math on variables through implicits update CHANGELOG update cHANGELOG update cHANGELOG providers/aws: set id outside if/esle providers/aws: set ID after creation core: remove dead code from pre-deposed refactor website: update LC docs to note name is optional security_groups field expects a list of Security Group Group Names, not IDs ...	11 years ago
Paul Hinze	34c7bbcf4d	providers/aws: reduce scope of block_device set hashcodes Fixes #1409 Resource set hash calculation is a bit of a devil's bargain when it comes to optional, computed attributes. If you omit the optional, computed attribute from the hash function, changing it in an existing config is not properly detected. If you include the optional, computed attribute in the hash and do not specify a value for it in the config, then you'll end up with a perpetual, unresolvable diff. We'll need to think about how to get the best of both worlds, here, but for now I'm switching us to the latter and documenting the fact that changing these attributes requires manual `terraform taint` to apply.	11 years ago
Rui Zhang	94bb3ed513	Support for AWS Placement Group - add placement_group for aws instance - update test and document	11 years ago
Paul Hinze	a4e80b6313	providers/aws: derive instance root_block_device name I was working on building a validation to check the user-provided "device_name" for "root_block_device" on AWS Instances, when I realized that if I can check it, I might as well just derive it automatically! So that's what we do here - when you customize the details of the root block device, device name is just comes from the selected AMI.	11 years ago
Paul Hinze	2b23c402ee	providers/aws: rework instance block devices Instance block devices are now managed by three distinct sub-resources: * `root_block_device` - introduced previously * `ebs_block_device` - all additional ebs-backed volumes * `ephemeral_block_device` - instance store / ephemeral devices The AWS API support around BlockDeviceMapping is pretty confusing. It's a single collection type that supports these three members each of which has different fields and different behavior. My biggest hiccup came from the fact that Instance Store volumes do not show up in any response BlockDeviceMapping for any EC2 `Describe*` API calls. They're only available from the instance meta-data service as queried from inside the node. This removes `block_device` altogether for a clean break from old configs. New configs will need to sort their `block_device` declarations into the three new types. The field has been marked `Removed` to indicate this to users. With the new block device format being introduced, we need to ensure Terraform is able to properly read statefiles written in the old format. So we use the new `helper/schema` facility of "state migrations" to transform statefiles in the old format to something that the current version of the schema can use. Fixes #858	11 years ago
Colin Hebert	268920126e	Update documentation to reflect the new vpc_security_group_ids parameter	11 years ago
Suguru Namura	68efa3fc21	providers/aws: add iops to block devices	11 years ago
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

40 Commits (ba4ec0097a47820db3bd686fdb708eca3b717d74)