Skip to content
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

TF not warning same resource being declared twice #23175

Closed
sandyleo26 opened this issue Oct 24, 2019 · 2 comments
Closed

TF not warning same resource being declared twice #23175

sandyleo26 opened this issue Oct 24, 2019 · 2 comments

Comments

@sandyleo26
Copy link

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
@ghost
Copy link

ghost commented Oct 24, 2019

This issue has been automatically migrated to hashicorp/terraform-provider-aws#10621 because it looks like an issue with that provider. If you believe this is not an issue with the provider, please reply to hashicorp/terraform-provider-aws#10621.

@ghost
Copy link

ghost commented Nov 24, 2019

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 have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@ghost ghost locked and limited conversation to collaborators Nov 24, 2019
This issue was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants