### Terraform Version ``` Terraform v1.2.4 on windows_amd64 + provider registry.terraform.io/hashicorp/azurerm v3.12.0 ``` ### Terraform Configuration Files ```terraform terraform { required_providers { azurerm = { source = "hashicorp/azurerm" version = ">=3.12.0" } } backend "azurerm" {} } provider "azurerm" { features {} } data "azurerm_subscription" "primary" {} output "foo" { value = "Hello world" } ``` ### Debug Output https://gist.github.com/orgads/4a9e79e173ab4deeed93b34248cf36ee ### Expected Behavior When terraform is forcefully aborted (Ctrl-C twice), the lock should not be acquired if not acquired yet, and should be released if already acquired. I'm not sure if this is a core or azurerm provider issue, feels like core to me. ### Actual Behavior The lock is acquired and not released, so force-unlock must be executed afterwards. ### Steps to Reproduce 1. `terraform init -backend-vars backend.tfvars` (you need variables for Azure backend) 2. `terraform apply` 3. Ctrl-C twice ### References - #16652 (unsure if it's the same)