joeduffy
da75f62865
Retry lambda creation until IAM role is available
...
Per Amazon's own documentation,
http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/iam-roles-for-amazon-ec2.html#launch-instance-with-role ,
IAM roles may take "several seconds" to propagate. In the meantime, we
are apt to get the dreaded "role defined for this function cannot be assumed"
error message. In response, we'll do what the AWS documentation suggests:
wait a bit and retry.
2017-04-18 13:56:19 -07:00
joeduffy
95f59273c8
Update copyright notices from 2016 to 2017
2017-03-14 19:26:14 -07:00
joeduffy
c633d0ceb0
Add "still waiting" messages to retries
2017-03-02 13:12:40 -08:00
joeduffy
1c43abffec
Fix some go vet
issues
2017-02-28 11:02:33 -08:00
joeduffy
fbb56ab5df
Coconut!
2017-02-25 07:25:33 -08:00
joeduffy
43432babc5
Wait for SecurityGroups to become active
2017-02-23 10:18:37 -08:00
joeduffy
d9e6d8a207
Add a simple retry.Until package/function
...
This change introduces a simple retry package which will be used in
resource providers in order to perform waits, backoffs, etc. It's
pretty basic right now but leverages the fancy new Golang context
support for deadlines and timeouts. Soon we will layer AWS-specific
acceptors, etc. atop this more general purpose thing.
2017-02-22 19:16:46 -08:00