-
Notifications
You must be signed in to change notification settings - Fork 9.6k
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
AWS SNS always planned to be changed #3660
Comments
Hey @maxbeatty – I've found 2 issues here, and have a fix for both. Posting a fix soon |
#3700 should fix this |
@catsby thanks for looking into this and adding a fix. As my project evolved, I ended up moving the permission to the role policy and out of the SNS resource so I can't test this fix for my previous situation. Hope this helps someone else down the line! |
Thanks for the update @maxbeatty , glad you had a workaround in place. Sorry for the trouble! |
I am experiencing this issue with 0.6.11, my SNS resource looks like this:
|
In your case the cause is the following: Instead try
However this doesn't fix the Terraform problem of it recognizing this incorrectly. |
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. |
I have, what I think is, a straightforward AWS SNS resource definition that includes a
Version
,Id
, andSid
, but it always reports as changed interraform plan
(v0.6.4 - latest from brew on OS X).Is it because of the variables inside the
EOF
? I see the s3 bucket policy argument mentions making "sure you use the verbose/specific version of the policy." How can I make this policy more specific?Thanks in advance!
The text was updated successfully, but these errors were encountered: