### Terraform Version ```shell Terraform v1.10.5 on darwin_arm64 + provider registry.terraform.io/drfaust92/confluence v0.0.5 + provider registry.terraform.io/hashicorp/aws v5.84.0 + provider registry.terraform.io/hashicorp/external v2.3.4 + provider registry.terraform.io/hashicorp/template v2.2.0 ``` ### Terraform Configuration Files ``` resource aws_cloudwatch_event_rule "orders" { name = "orders" event_pattern = <<PATTERN { "detail": { "metadata": { "Order-Status": ["orders/updated"] }, "payload": { "tags": ["VALUE_ONE"], "tags": ["VALUE_TWO"] } } } PATTERN event_bus_name = "my_event_bus" } ``` ### Debug Output ``` ...debug output, or link to a gist... ``` ### Expected Behavior The event pattern should include BOTH `tags` values ``` "tags": ["VALUE_ONE"], "tags": ["VALUE_TWO"] ``` ### Actual Behavior Only the FIRST value is used, because of the duplicate `"tags"` key. Duplication of keys is required if, for instance, the event rule pattern needs to only match events that have BOTH values in the `tags` array. Using `"tags": ["VALUE_ONE", "VALUE_TWO"]` matches for the presence of EITHER value, which is not what is required in some cases. Note that duplicate tags like the above are accepted and work as expected when directly updating the event rule in the AWS web console. ### Steps to Reproduce 1. terraform init 2. terraform plan You will see that the plan only shows the first of the `tags` items. ### Additional Context _No response_ ### References _No response_ ### Generative AI / LLM assisted development? _No response_