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

Instance Running waiter not aware of global waiter settings #8699

Merged
merged 1 commit into from
Feb 6, 2020

Conversation

fly1028
Copy link
Contributor

@fly1028 fly1028 commented Feb 5, 2020

This is related to #6177.

The work done for #6177 didn't really address the hardcoded timeout issue for the run source instance step.
Specifically, it's not aware of the AWS_POLL_DELAY_SECONDS and AWS_TIMEOUT_SECONDS.

@fly1028 fly1028 requested a review from a team as a code owner February 5, 2020 23:18
@hashicorp-cla
Copy link

hashicorp-cla commented Feb 5, 2020

CLA assistant check
All committers have signed the CLA.

Copy link
Contributor

@azr azr left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey @fly1028, thanks ! LGTM

InstanceIds: []*string{&instanceId},
}

err := conn.WaitUntilInstanceRunningWithContext(
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oh super nice, I wasn't aware of this one !

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice! Seeing as we don’t actually use err here we can just return with the call to conn.WaitUntilInstanceRunningWithContext(...

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@nywilken I'm following the convention of other existing WaitUntil* methods in state.go

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@fly1028 thanks I only looked at the diff. But this is good to go I just have not had a chance to merge.

Copy link
Contributor

@sylviamoss sylviamoss left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM as well!! Nice catch 😄

Copy link
Member

@nywilken nywilken left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM as well. I left a small comment to drop the assignment of err for a return but that shouldn’t prevent the merge.

@nywilken nywilken merged commit a1d9ba0 into hashicorp:master Feb 6, 2020
@nywilken nywilken added this to the 1.5.2 milestone Feb 10, 2020
@ghost
Copy link

ghost commented Apr 1, 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 1, 2020
@fly1028 fly1028 deleted the fix-instance-running-timeout branch July 24, 2020 15:45
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants