azurerm_app_configuration soft deleted with no option to purge

[jason-swissre]

Is there an existing issue for this?

• I have searched the existing issues

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

Terraform Version

1.0.7

AzureRM Provider Version

3.6.0

Affected Resource(s)/Data Source(s)

azurerm_app_configuration

Terraform Configuration Files

resource "azurerm_app_configuration" "main" {
  name                = var.configname
  resource_group_name = var.rgname
  location            = var.location
  sku                 = var.sku
  identity {
    type = "SystemAssigned"
  }
}

Debug Output/Panic Output

not applicable

Expected Behaviour

When doing a terraform destroy and then later a terraform apply the azurerm_app_configuration should be created.

Actual Behaviour

The azurerm_app_configuration is not created because there is already an azurerm_app_configuration with the same name.

This happens because terraform destroy is doing a soft delete on the azurerm_app_configuration. There is no option in azurerm_app_configuration or azurerm features that allows turning on purge for this resource.

Steps to Reproduce

1. terraform apply
2. terraform destroy
3. terraform apply

Important Factoids

No response

References

No response

[github-actions]

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.