Terraform shows diff for policy due to different order in JSON
### Community Note * Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help the community and maintainers prioritize this request * Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request * If you are interested in working on this issue or have submitted a pull request, please leave a comment <!--- Thank you for keeping this note for the community ---> ### Terraform CLI and Terraform AWS Provider Version ``` Terraform v1.0.8 on linux_amd64 + provider registry.terraform.io/hashicorp/aws v3.70.0 + provider registry.terraform.io/hashicorp/google v3.90.1 ``` ### Affected Resource(s) * aws_s3_bucket_policy ### Terraform Configuration Files <!--- Information about code formatting: https://help.github.com/articles/basic-writing-and-formatting-syntax/#quoting-code ---> Please include all Terraform configurations required to reproduce the bug. Bug reports without a functional reproduction may be closed without investigation. ```hcl locals { customers = data.terraform_remote_state.global.outputs.all_customers } resource "aws_s3_bucket" "customer_cloud_resources" { for_each = local.customers bucket = "XXX-cloud-resources-${each.value}" acl = "private" cors_rule { allowed_headers = ["*"] allowed_methods = ["GET",
Posted by anthonyAdhese on Dec 22, 2021, 1:07 PM
Tags
Related issues
Raise real-world problems, find people facing the same issue, and discuss solutions.3,000 issues0 comments
github (E-commerce)
proposal: cmd/cgo: cgo without a C toolchain
Replace PowerToys Run with Command Palette
VPS with a vRack leg
Possibility of Portal 1 Code Inclusion
Introducing NewPlayer
Metrics for PRs are never expiring ("memory leak")
ship even more of the compiler in source form
Flatpak Application TRACKING ISSUE
Terraform shows diff for policy due to different order in JSON
### Community Note * Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help the community and maintainers prioritize this request * Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request * If you are interested in working on this issue or have submitted a pull request, please leave a comment <!--- Thank you for keeping this note for the community ---> ### Terraform CLI and Terraform AWS Provider Version ``` Terraform v1.0.8 on linux_amd64 + provider registry.terraform.io/hashicorp/aws v3.70.0 + provider registry.terraform.io/hashicorp/google v3.90.1 ``` ### Affected Resource(s) * aws_s3_bucket_policy ### Terraform Configuration Files <!--- Information about code formatting: https://help.github.com/articles/basic-writing-and-formatting-syntax/#quoting-code ---> Please include all Terraform configurations required to reproduce the bug. Bug reports without a functional reproduction may be closed without investigation. ```hcl locals { customers = data.terraform_remote_state.global.outputs.all_customers } resource "aws_s3_bucket" "customer_cloud_resources" { for_each = local.customers bucket = "XXX-cloud-resources-${each.value}" acl = "private" cors_rule { allowed_headers = ["*"] allowed_methods = ["GET",
Comments (0)
No comments yet. Start the discussion.