-
Notifications
You must be signed in to change notification settings - Fork 9.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
provider/aws: Troubles destroying large ASGs #46
Comments
This comment was originally opened by @maratoid as hashicorp/terraform#3495 (comment). It was migrated here as part of the provider split. The original comment is below. Hey guys. Just wondering if this is in any kind of a roadmap. We're still having to work around this in all sorts of clunky ways. Thanks. |
This comment was originally opened by @phinze as hashicorp/terraform#3495 (comment). It was migrated here as part of the provider split. The original comment is below. Acknowledging that this is still an issue. Been kicking around a core-supported solution for this, let me braindump some notes on that: Terraform needs support for per-resource user-configurable timeouts. These timeouts should apply to Create, Update, Destroy operations. Sketch of one possible config (not super sold on it - there might be a nicer spot to drop this): resource "aws_autoscaling_group" "foo" {
# ...
timeouts {
create = "30m"
destroy = "30m"
update = "10m"
}
} Resource implementations would need to opt-in for support of these config values so that if a user specifies them on an unsupported resource, a validation error is returned. |
This comment was originally opened by @maratoid as hashicorp/terraform#3495 (comment). It was migrated here as part of the provider split. The original comment is below. Any news :) ? |
This comment was originally opened by @maratoid as hashicorp/terraform#3495 (comment). It was migrated here as part of the provider split. The original comment is below. ping |
Hi everyone, The ASG deletion timeout is now configurable as per #949. I am going to close this one if you folks don't mind, let me know if this is still an issue! |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks! |
This issue was originally opened by @phinze as hashicorp/terraform#3495. It was migrated here as part of the provider split. The original body of the issue is below.
hashicorp/terraform#3485 attempted to fix
force_delete
, but @maratoid provided a test config that still yields errors.Current status with his config is:
In order to fix, I think we need to:
This is all a bit jargon-y, happy to clarify anything if someone else digs into this before I do.
The text was updated successfully, but these errors were encountered: