fix: Lambda should depend on policy attachments #327
Merged
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.
Description
Added all policy-attachments to the deponds_on of the 'aws_lambda_function'
Motivation and Context
When the lambda is created the execution-role with all its
policies should be in place.
Some policies like VPC are a hard requirement for lambda creation
which fill fail if they are not already in place.
Fixes #326
Breaking Changes
May introduce circular dependencies, where policies some how depend on the lambda.
Those policies could created / attached outside of this module.
How Has This Been Tested?
examples/with-vpcpre-commit run -aon my pull request