When creating lambda function, retry waiting for IAM role to be propagated #30610
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.
When an AWS IAM role is created, it may take some time before it's propagated to all regions. In the meantime, creating a lambda function referencing that role may fail. In salt states that create a role and then immediately create a lambda function, this can lead to errors. Add an exponential backoff retry to cover this case, rather than forcing users to work around in their state files.
See hashicorp/terraform#1885 for more info on the situation that occurs.