fix: make sure attachments are ready before creating lambda function

[manifestori]

This PR fixes the lambda creation issue, where permissions are required.

For example, if you add vpc_config, the lambda will fail on the first attempt since no attachment has been made to the IAM role. That's the only edge case.

Fixing by adding depends_on to attachments as they are implicitly required to exist before the lambda resource creation.

[Gowiem]

@natemccurdy did you run into this issue ever? I'm wondering if this is actually something that needs to be addressed or not still...

[Gowiem]

/terratest

[natemccurdy]

@Gowiem I did not hit this specific issue. But I did find and fix a semi-related ordering issue for the aws_iam_role_policy_attachment.custom resource, but the root cause of that was an incorrect for_each block (#46).

I'm not claiming to be an expert on AWS Lambda API requirements, but I'm not totally sure that this statement is correct:

...to attachments as they are implicitly required to exist before the lambda resource creation.

It'd be good to validate that statement to nail down exactly what situations lead to an edge case.

[mergify]

Thanks @manifestori for creating this pull request!

A maintainer will review your changes shortly. Please don't be discouraged if it takes a while.

While you wait, make sure to review our contributor guidelines.

Tip

Need help or want to ask for a PR review to be expedited?

Join us on Slack in the #pr-reviews channel.