138 Commits (347690a73e449e1d5fdbbce2de8d4081837ecf2f)

Author	SHA1	Message	Date
Mitchell Hashimoto	c9eb7dc8bf	Merge pull request #1465 from tlovett-rmn/fix-security-groups-docs ... website: security_groups field expects a list of Group Names, not Group IDs	11 years ago
Mitchell Hashimoto	0bd7856942	website: update LC docs to note name is optional	11 years ago
Thomas Lovett	baf1625485	security_groups field expects a list of Security Group Group Names, not IDs	11 years ago
Paul Hinze	de3735bd6f	docs: move aws SG tags from rules to resource ... fixes #1479	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
Daisuke Fujita	236d3af646	Remove owner_id argument from document	11 years ago
Nick HS	39598cf1fa	Rename False to false in aws_db_instance ... False isn't allowed in hcl, just fixing a typo	11 years ago
Nick HS	95270bf68d	Change example name in aws_db_paramater_group res ... AWS DB Paramater Groups cannot contain underscores, see http://docs.aws.amazon.com/AmazonRDS/latest/CommandLineReference/CLIReference-cmd-CreateDBParameterGroup.html	11 years ago
Jason Waldrip	f77250f17d	block device support for launch configurations ... - mimics block device support from AWS instance - splits the acceptance tests out so they all pass, handling a FIXME from #1079	11 years ago
Clint Shryock	e485767694	provider/aws: Add non-destructive updates to AWS RDS ... This introduces non-destructive, in-place upgrades to MultiAZ and Engine Version attributes of AWS RDS instances.	11 years ago
Radek Simko	7950ace399	Documentation for ASG Tags added	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
Clint	bb4dd8ae77	Merge pull request #1137 from deverton/aws-go-vpn ... provider/aws: Add Support For AWS VPN Gateways using aws-sdk-go	11 years ago
Paul Hinze	46b63074e0	Merge pull request #1045 from hashicorp/f-block-devices ... providers/aws: rework instance block devices	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
Dan Everton	f7289599cc	Merge branch 'master' into aws-go-vpn	11 years ago
Michael H. Oshita	1979d9b792	fix indent ... align indentation with the rest of the code.	11 years ago
Clint	dc4abb48fa	Merge pull request #1195 from hashicorp/f-retire-goamz ... provider/aws: Retire goamz	11 years ago
Clint Shryock	cd15c9aaf9	clean up docs	11 years ago
Clint Shryock	2d62e55b0e	Add note to Intergent Gateway resource on using depends_on	11 years ago
Clint Shryock	580b696e7f	Strike 'goamz' from the repo'	11 years ago
Dan Everton	9f50b048e1	Merge branch 'master' into aws-go-vpn	11 years ago
Clint Shryock	64f7e6a19c	Update website docs on AWS RDS encryption field	11 years ago
Dan Everton	0900452113	Remove type parameter from vpn_gateway docs	11 years ago
Dan Everton	b741e0c9a3	Add documentation	11 years ago
Paul Hinze	72d4ac73d3	Merge pull request #1103 from suguru/aws-block-device-iops ... providers/aws: add iops to block devices	11 years ago
Mitchell Hashimoto	16cafe9d46	website; clarify where the args go for AWS [GH-853]	11 years ago
Mitchell Hashimoto	9efd20cd7c	website: document MFA token for AWS [GH-390]	11 years ago
Suguru Namura	68efa3fc21	providers/aws: add iops to block devices	11 years ago
Kevin Yi	0e3f1a865e	protocol value for all traffic should be -1 ... If it is all traffic instead of all tcp traffic , protocol should be equal -1 , otherwise indicate all tcp not all traffic	11 years ago
Jack Pearkes	c21c766c3e	website: route53 subdomain hosted zones example	11 years ago
Clint Shryock	d79b0d7fd1	provider/aws: Convert AWS DB Instance over to awslabs/aws-sdk-go ... - Remove check on password for AWS RDS Instance - Update documentation on AWS RDS Instance regarding DB Security Groups - Change error handling to check error code from AWS API [ci skip]	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	44c45994c8	Merge pull request #963 from julienba/master ... providers/aws: vpc_peering_connection	11 years ago
jba	372035368f	allow update	11 years ago
Mitchell Hashimoto	0feb29944c	Merge pull request #856 from CashStar/aws_egress ... provider/aws: adding support for egress rules in AWS Security Groups	11 years ago
nevins-b	b7238ca6f2	adding documentation	11 years ago
Mitchell Hashimoto	c5e035361f	Merge pull request #896 from bitglue/storage_type ... provider/aws: Support storage_type parameter for aws_db_instance	11 years ago
Mitchell Hashimoto	f63aa41d67	Merge pull request #897 from bitglue/apply_method ... provider/aws: Implement apply_method for RDS parameters	11 years ago
Mitchell Hashimoto	1fa6141a39	Merge pull request #933 from egarbi/master ... docs: Added missing line for aws_launch_configuration resource on AWS provider...	11 years ago
jba	101f801846	add aws_vpc_peering_connection	11 years ago
Radek Simko	3366f1924f	Add docs for AWS IG tags	11 years ago
jba	3b0b41c9a1	allow vpc_peering_connection_id in aws_route_table	11 years ago
Phil Frost	81b5c238ef	Clarify usage of `aws_elb` ... Address confusion regarding ELB in VPC or EC2-classic. See #958.	11 years ago
Enrique Garbi	2b3015f66a	Added missing line for aws_launch_configuration resource on AWS provider docs	11 years ago
Paul Hinze	f852a01c22	providers/aws: docs for aws_main_route_table_association	11 years ago
Phil Frost	8eb5418c4a	Implement apply_method for RDS parameters ... This is necessary to support creating parameter groups with parameters that require a reboot, since the RDS API will return an error when attempting to set those parameters with ApplyMethod "immediate".	11 years ago
Phil Frost	bfaf8ccee6	Support storage_type parameter for aws_db_instance ... This allows provisioning "gp2" (general purpose SSD) storage for DB instances.	11 years ago
Phil Frost	254b25a64f	Fix aws_db_instance to not recreate each time ... Several of the arguments were optional, and if omitted, they are calculated. Mark them as such in the schema to avoid triggering an update. Go back to storing the password in the state file. Without doing so, there's no way for Terraform to know the password has changed. It should be hashed, but then interpolating the password yields a hash instead of the password. Make the `name` parameter optional. It's not required in any engine, and in some (MS SQL Server) it's not allowed at all. Drop the `skip_final_snapshot` argument. If `final_snapshot_identifier` isn't specified, then don't make a final snapshot. As things were, it was possible to create a resource with neither of these arguments specified which would later fail when it was to be deleted since the RDS API requires exactly one of the two. Resolves issue #689.	11 years ago
Seth Vargo	5713b7abcc	Remove extra newline	11 years ago