Skip to content
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

feature request: warning for iam_policy_attachment #252

Closed
maartenvanderhoef opened this issue Sep 6, 2018 · 2 comments
Closed

feature request: warning for iam_policy_attachment #252

maartenvanderhoef opened this issue Sep 6, 2018 · 2 comments

Comments

@maartenvanderhoef
Copy link

Hi! In an environment where any developer can create tf code. Would it be an idea to create warnings which stand out for [https://www.terraform.io/docs/providers/aws/r/iam_policy_attachment.html] iam_policy_attachment ? When applied wrongfully it can be quite disruptive, and it's easy to overlook when reviewing.

@lkysow
Copy link
Member

lkysow commented Sep 7, 2018

Hi @maartenvanderhoef thanks for the ticket. I agree that it would be nice to have some sort of automated code review process built in to Atlantis but I'm not sure the best way to approach it. While I do see Atlantis being able to help with this at some point, it seems far off because I'm focused on getting the main workflow piece working smoothly for everyone.

I think for now, I'd recommend using the atlantis.yaml file to run your own hooks that do the review you want or using a secondary build process. What do you think?

@lkysow lkysow added the waiting-on-response Waiting for a response from the user label Sep 7, 2018
@maartenvanderhoef
Copy link
Author

maartenvanderhoef commented Sep 8, 2018

That's fine.. enough on your list. For now I've fixed with it an extra run step after the plan. It will probably get annoying after a while..

  • run: find . -name \"*.tf\" -exec grep -Hn aws_iam_policy_attachment {} \\; -print

@lkysow lkysow removed the waiting-on-response Waiting for a response from the user label Dec 3, 2018
jamengual pushed a commit that referenced this issue Nov 24, 2022
* draft

* pass context/fields thru

* fix tests
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants