resource/aws_lambda_function: Handle slower code uploads on creation with configurable timeout #6409
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #4516
Tested by adding a deliberate 2 minute sleep inside the first
resource.Retry()
function before the CreateFunction call. Prior to this update, slow ZIP file uploads would have no chance of being successful. Now they can have a configurable timeout. This is not a problem on update since we callUpdateFunctionCode
outside anyresource.Retry()
/StateChangeConf
context.Previously:
Now: