You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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
locked and limited conversation to collaborators
Nov 24, 2019
This issue was closed.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Not sure if this is reported because but it seems very problematic to me if this is expected behaviour.
plan
and thenapply
the following will give me one queue namedtest
with 60svisibility_timeout_seconds
. I expect TF would raise warning at least or bubble up errors from AWS but it's all green.Terraform Version
Terraform Configuration Files
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
terraform init
terraform plan
terraform apply
The text was updated successfully, but these errors were encountered: