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
..
compiler	Permit dynamic to appear in more places (like binops)	2017-04-12 10:55:33 -07:00
diag	Add optional formatting to the diag.Message API	2017-03-15 12:16:56 -07:00
encoding	Switch to imports as statements	2017-04-08 18:16:10 -07:00
eval	Permit dynamic to appear in more places (like binops)	2017-04-12 10:55:33 -07:00
graph	Update copyright notices from 2016 to 2017	2017-03-14 19:26:14 -07:00
pack	Update copyright notices from 2016 to 2017	2017-03-14 19:26:14 -07:00
resource	Implement AWS Lambda resource provider	2017-04-18 11:02:04 -07:00
tokens	Update copyright notices from 2016 to 2017	2017-03-14 19:26:14 -07:00
util	Retry lambda creation until IAM role is available	2017-04-18 13:56:19 -07:00
workspace	Make major commands more pleasant	2017-03-21 19:23:32 -07:00