-
-
Notifications
You must be signed in to change notification settings - Fork 712
aws_iam_policy_attachment used for additional policies #40
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
This should be the case for all attachments as it can override or removing existing policies from other roles. |
As far as I can see, these two are the only ones that allow using existing policies. Other attachments either create new policies or use inline policies. |
I just ran into this issue as well... does anyone know if there are any plans to correct this? |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
aws_iam_policy_attachment
creates exclusive attachments, I think it makes more sense to useaws_iam_role_policy_attachment
in those cases:terraform-aws-lambda/iam.tf
Line 226 in 5ab6ccb
terraform-aws-lambda/iam.tf
Line 238 in 5ab6ccb
The text was updated successfully, but these errors were encountered: