Closed snarky closed 1 week ago
Voting for Prioritization
Volunteering to Work on This Issue
Looks like the order in the AWS API response is not deterministic - sometimes the order is OK, sometimes it's not. In any case, it makes sense to make the argument unordered using a Set
as a catch-all.
[!WARNING] This issue has been closed, meaning that any additional comments are hard for our team to see. Please assume that the maintainers will not see them.
Ongoing conversations amongst community members are welcome, however, the issue will be locked after 30 days. Moving conversations to another venue, such as the AWS Provider forum, is recommended. If you have additional concerns, please open a new issue, referencing this one where needed.
This functionality has been released in v5.59.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!
Terraform Core Version
1.8.3
AWS Provider Version
5.49.0
Affected Resource(s)
Expected Behavior
Terraform should recognize that there are no actual changes in the
insight_selector
blocks and should not show any updates in the execution plan.Actual Behavior
Terraform shows an in-place update with the
insight_type
values switching:Relevant Error/Panic Output Snippet
Terraform Configuration Files
https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/cloudtrail
Steps to Reproduce
Define an
aws_cloudtrail
resource withinsight_selector
blocks:Run
terraform apply
twice.Debug Output
No response
Panic Output
No response
Important Factoids
No response
References
No response
Would you like to implement a fix?
None