-
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
aws_iam_policy_document Bool condition always shows diff #19245
Comments
Hi @IrmantasM , thank you for raising this issue. To help backtrack where this may have been introduced, do you mind providing which provider version you were using before upgrading to the latest? thanks in advance! |
This is not an issue in provider version v3.27.0. It was introduced in v3.28.0 |
Can confirm with @jooh-lee's comment above that the behavior is present as early as |
Same here. Getting such on all conditions, e.g. ~ Condition = {
~ Bool = {
~ aws:SecureTransport = "true" -> [
+ "true",
]
}
~ StringEquals = {
~ elasticfilesystem:AccessPointArn = "arn:aws:elasticfilesystem:us-east-1:1234567890:access-point/fsap-1234567890" -> [
+ "arn:aws:elasticfilesystem:us-east-1:1234567890:access-point/fsap-1234567890",
]
}
} |
A previous issue (closed with no proper resolution) showing the the StringEquals case: #17623 Possibly shares a root cause? |
Yep this can be mitigated by adding a trailing comma after any item in a list of conditions/resources/actions, including a single item. |
This should be resolved with #22067 (mostly about IAM but included an updated version of |
This functionality has been released in v3.69.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. |
Community Note
Relates #21968
Terraform CLI and Terraform AWS Provider Version
Affected Resource(s)
Terraform Configuration Files
Please include all Terraform configurations required to reproduce the bug. Bug reports without a functional reproduction may be closed without investigation.
Expected Behavior
Plan should show no changes.
Actual Behavior
Steps to Reproduce
terraform apply
terraform plan
Important Factoids
This issue wasn't there before upgrading to latest aws provider version.
The text was updated successfully, but these errors were encountered: