-
Notifications
You must be signed in to change notification settings - Fork 9.2k
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
Make aws_iam_policy_attachment warning less opaque #1234
Merged
grubernaut
merged 1 commit into
hashicorp:master
from
mcwqy9:aws_iam_policy_attachment_warning
Jul 25, 2017
Merged
Make aws_iam_policy_attachment warning less opaque #1234
grubernaut
merged 1 commit into
hashicorp:master
from
mcwqy9:aws_iam_policy_attachment_warning
Jul 25, 2017
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
grubernaut
added
the
documentation
Introduces or discusses updates to documentation.
label
Jul 25, 2017
grubernaut
approved these changes
Jul 25, 2017
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, thanks!
This was referenced Jul 19, 2017
This was referenced Jan 23, 2018
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 feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks! |
ghost
locked and limited conversation to collaborators
Apr 11, 2020
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
The current note on aws_iam_policy_attachment is well intentioned but too subtle. I managed to revoke an execution role from 7 lambdas over this. I'm not alone. Consider #94, and #133, which feature gems like:
"aws_iam_policy_attachment as it is implemented today is insanely dangerous" and
"this is hugely disruptive and downright dangerous to use in a live environment. Folks should probably stick with using aws_iam_role_policy_attachment instead of aws_iam_policy_attachment"
I actually think aws_iam_policy_attachment ought to be removed from Terraform because no one expects the Terraform inquisition, but at the very least we can make the docs clearer.
This update is worth deploying to the site immediately.