14 Commits (65ac8649efa733231d89c4e6d746dbe21e75cf0d)

Author	SHA1	Message	Date
Paul Hinze	c70eab6500	aws: undeprecate min_elb_capacity; restore min capacity waiting ... It was a mistake to switched fully to `==` when activating waiting for capacity on updates in #3947. Users that didn't set `min_elb_capacity == desired_capacity` and instead treated it as an actual "minimum" would see timeouts for every create, since their target numbers would never be reached exactly. Here, we fix that regression by restoring the minimum waiting behavior during creates. In order to preserve all the stated behavior, I had to split out different criteria for create and update, criteria which are now exhaustively unit tested. The set of fields that affect capacity waiting behavior has become a bit of a mess. Next major release I'd like to rework all of these into a more consistently named block of config. For now, just getting the behavior correct and documented. (Also removes all the fixed names from the ASG tests as I was hitting collision issues running them over here.) Fixes #4792	10 years ago
Paul Hinze	319f7d77a0	Merge pull request #3947 from hashicorp/phinze/asg-wait-on-update ... provider/aws: wait for ASG capacity on update	10 years ago
Paul Hinze	709d1f3599	Merge pull request #3704 from dayer4b/add-placement-group ... added placement group as an option for autoscaling groups	11 years ago
Paul Hinze	7f9360797c	provider/aws: wait for ASG capacity on update ... It's a bit confusing to have Terraform poll until instances come up on ASG creation but not on update. This changes update to also poll if min_size or desired_capacity are changed. This changes the waiting behavior to wait for precisely the desired number of instances instead of that number as a "minimum". I believe this shouldn't have any undue side effects, and the behavior can still be opted out of by setting `wait_for_capacity_timeout` to 0.	11 years ago
Sunil K Chopra	16b0e0d619	documentation, thanks again to stack72	11 years ago
stack72	69b905fb92	Making the AutoScalingGroup name optiona	11 years ago
Paul Hinze	07a9c34e02	Merge pull request #3339 from stack72/aws-asg-docs-3327 ... docs: Updating the ASG docs to suggest health_check_grace_period is a required field under certain circumstances	11 years ago
Paul Hinze	5f6c03f515	Merge pull request #3191 from hashicorp/f-asg-wait-config ... provider/aws: configurable capacity waiting duration	11 years ago
Paul Hinze	a811a72f11	provider/aws: fix force_delete on ASGs ... The `ForceDelete` parameter was getting sent to the upstream API call, but only after we had already finished draining instances from Terraform, so it was a moot point by then. This fixes that by skipping the drain when force_delete is true, and it also simplifies the field config a bit: * set a default of false to simplify the logic * remove `ForceNew` since there's no need to replace the resource to flip this value * pull a detail comment from code into the docs	11 years ago
stack72	dc27e3d10b	Adding a node to AWS AutoScale docs to make it clear that health_check_grace_period is a required field when setting ELB as the health_check_type	11 years ago
Paul Hinze	506aae2f28	provider/aws: configurable capacity waiting duration ... move wait for capacity timeout from a constant to a configurable	11 years ago
Dave York	6c6793a260	use name instead of id ... - launch configs use the name and not ID	11 years ago
Clint Shryock	55a1a31c2b	provider/aws: document that availability zones are now optional in ASGs	11 years ago
Radek Simko	ef92a03a9b	Docs: Fix name according to reality (autoscaling->autoscaling_group)	11 years ago