TF not warning same resource being declared twice

[ghost]

This issue was originally opened by @sandyleo26 as hashicorp/terraform#23175. It was migrated here as a result of the provider split. The original body of the issue is below.

---

Not sure if this is reported because but it seems very problematic to me if this is expected behaviour.

plan and then apply the following will give me one queue named test with 60s visibility_timeout_seconds. I expect TF would raise warning at least or bubble up errors from AWS but it's all green.

Terraform Version

Terraform v0.12.10
+ provider.aws v2.33.0

Terraform Configuration Files

resource "aws_sqs_queue" "sha-test" {
  visibility_timeout_seconds = 120
  name = "test"
}

resource "aws_sqs_queue" "sha-test2" {
  name = "test"
  visibility_timeout_seconds = 60
}

Expected Behavior

TF warn me the two resources actually the same.

Actual Behavior

TF proceed and overwrite the configuration. And the state file contains duplicate queues.

Steps to Reproduce

1. terraform init
2. terraform plan
3. terraform apply

[radeksimko]

Related: hashicorp/terraform-plugin-sdk#224

[ryndaniels]

Hi @sandyleo26 - thanks for taking the time to open this issue. Unfortunately, I am not able to reproduce this behavior with the latest versions of both Terraform and the AWS Provider with the configuration you provided. With the latest version, this config gives me the following error:

Error: Error creating SQS queue: QueueAlreadyExists: A queue already exists with the same name and a different value for attribute VisibilityTimeout

We're going to go ahead and close this issue for now, but if you are still seeing this behavior when you are using the latest versions, please feel free to open another issue.

[ghost]

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.

If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks!