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

Increased lambda event mapping creation timeout #7657

Merged
merged 1 commit into from
Jul 18, 2016

Conversation

kellydavid
Copy link
Contributor

Increased the retry timeout from 1 to 5 minutes due to the time for IAM permission propagation.

@kellydavid kellydavid force-pushed the master branch 2 times, most recently from 6e0654d to 7f9b9b8 Compare July 14, 2016 20:03
@radeksimko
Copy link
Member

Hi @kellydavid
thanks for the PR. This makes sense to me.

Would you mind bumping the timeout to 5mins in Update function too?
Since IAM is eventually consistent the Create operation may succeed and subsequent Update operation may fail (i.e. may need retry too).

@radeksimko radeksimko added bug waiting-response An issue/pull request is waiting for a response from the community provider/aws labels Jul 18, 2016
@kellydavid kellydavid closed this Jul 18, 2016
@kellydavid kellydavid reopened this Jul 18, 2016
@kellydavid
Copy link
Contributor Author

@radeksimko Thanks, made that change.

Increased the retry timeout from 1 to 5 minutes due to the time for IAM permission propagation
@radeksimko radeksimko removed the waiting-response An issue/pull request is waiting for a response from the community label Jul 18, 2016
@radeksimko
Copy link
Member

👍

@radeksimko radeksimko merged commit 08291af into hashicorp:master Jul 18, 2016
@ghost
Copy link

ghost commented Apr 24, 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 24, 2020
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.

2 participants