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
TF does not fail on inability to tag IAM Policy Resources with default tags #24930
Comments
Hey @mikecouk 👋 Thank you for taking the time to raise this! So that we have all of the necessary information in order to look into this, can you update the issue description to include all of the information requested in the bug report template? |
@justinretzolk Hi Justin, unfortunately due to commercial reasons we cannot provide any more information or dedicate any more time to reporting this error. We do still believe though that you should be able to replicate this error with only the limited information we have provided, as it's quite a simple problem. Sorry we can't be of any more help. |
FYI I'm observing he same behaviour. |
this is missing some info as |
Related #22532 |
This functionality has been released in v4.20.0 of the Terraform AWS Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you! |
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. |
Sooooo ......
If you use default_tags in your AWS provider, and you also use an "aws_iam_user_policy" resource, then naturally your AWS IAM policy somewhere will have "iam:TagPolicy + iam:UntagPolicy" in it right ? Else the policy can't be tagged ....
However, if you DON'T have the those permissions in your policy, you'd expect terraform to bomb out. However it doesn't, it just carries on as normal, says "Modifications complete" and thinks it's all done. Further manual inspection of the AWS policy reveals the tags have not been applied, and if you re-run terraform it correctly notices the tags still haven't been applied yet, and will try again ... and again .... and again !
Summary : Terraform doesn't bomb out and report an error when it can't tag an IAM policy with default tags.
Terraform version = 1.2.0
hashicorp/aws version = 4.15
Other modules worked with = Datadog/datadog v 3.11.0
Thanks in advance people !
The text was updated successfully, but these errors were encountered: