Skip to content
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

Make the ASG delete timeout configurable #14396

Conversation

jringuette
Copy link
Contributor

Fix issue #14394

I've added a configurable delete timeout for the ASG.

I've modified helper/schema/resource.go to read the meta from the state when it is not present in the diff. I'm not sure why this is happening, but on every tries I made, the diff never had the meta info into. It might not be the proper way to fix that problem tough, if someone more familiar with the code base could have a look. But it does not seem to cause any regression nor problem.

Documentation is also updated to reflect the new supported timeout.

@iceycake iceycake force-pushed the fix-issue-14394-asg-configurable-timeout branch from 3ccbada to 689095f Compare May 11, 2017 23:07
@iceycake
Copy link
Contributor

@catsby can you take a look to see if this PR is good? Thanks.

@catsby catsby self-assigned this May 12, 2017
@catsby
Copy link
Member

catsby commented May 12, 2017

Hey @jringuette can you describe when this was happening?

I've modified helper/schema/resource.go to read the meta from the state when it is not present in the diff.

Was that all the time? Or just certain situation(s)?

@catsby catsby added the waiting-response An issue/pull request is waiting for a response from the community label May 12, 2017
@jringuette
Copy link
Contributor Author

@catsby, It was all the time. It was always returning the default timeout (20 minutes) from here

return 20 * time.Minute

When opening the state file, I was able to see the timeouts correctly saved under the meta e2bfb730-ecaa-11e6-8f88-34363bc7c4c0, but when reading, it always read from the diff which did not contained that meta.

@ledor473
Copy link

Any update on this ticket? We faced the same issue recently.

@catsby
Copy link
Member

catsby commented Jun 22, 2017

This has been migrated to #15374 and hashicorp/terraform-provider-aws#949

@catsby catsby closed this Jun 22, 2017
catsby pushed a commit to hashicorp/terraform-provider-aws that referenced this pull request Jun 23, 2017
@ghost
Copy link

ghost commented Apr 8, 2020

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 have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@ghost ghost locked and limited conversation to collaborators Apr 8, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement provider/aws waiting-response An issue/pull request is waiting for a response from the community
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants